Have the option of NOT having the type predicate (i.e. _class = '<class-name>' in queries.

[mikereiche]

Have the option of NOT having the type predicate (i.e. _class = '' in queries.

The most logical solution would be to simply use 1=1 in place of _class=. This could be achieved by specifying the typeKey=1 and typeAlias=1 - except that back-ticks are automatically used to escape the typeKey.

[mikereiche]

@@ -229,7 +229,8 @@ public class StringBasedN1qlQueryParser {
-               String typeSelection = "`" + typeField + "` = \"" + typeValue + "\"";
+               String typeSelection =
+                       typeField == null ? null : ( typeField.equals("1") ? "1=1" : ("`" + typeField + "` = \"" + typeValue + "\""));

@@ -77,12 +77,12 @@ public class N1qlJoinResolver {
-               String onLks = "lks." + n1qlL.filter;
+               String onLks = n1qlL.filter != null  && !n1qlL.filter.equals("1=1") ? "lks." + n1qlL.filter : null;
...
-               String onRks = "rks." + n1qlR.filter;
+               String onRks = n1qlR.filter != null && !n1qlR.filter.equals("1=1") ?  "rks." + n1qlR.filter :null;

@@ -107,7 +107,9 @@ public class N1qlJoinResolver {
-               String on = "ON " + parameters.getJoinDefinition().on().concat(" AND " + onLks).concat(" AND " + onRks);
+               String on = "ON " + parameters.getJoinDefinition().on();
+               on = onLks != null ? " AND " + onLks : on;
+               on = onRks != null ? " AND " + onRks : on;

[mikereiche]

See #493

[mikereiche]

Folks - please read the end of the sentence : "This could be achieved by specifying the typeKey=1 and typeAlias=1 - except that back-ticks are automatically used to escape the typeKey".

[mikereiche]

Fixed by #1777.
"If the configuration getType() or the https://github.com/typealias is an empty string, then do not add the typeKey:typeAlias property when storing documents, and do not add the typeKey=typeAlias property on queries - including removeByQuery."