[
https://issues.apache.org/jira/browse/GEODE-7802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17249065#comment-17249065
]
ASF GitHub Bot commented on GEODE-7802:
---------------------------------------
agingade commented on a change in pull request #5844:
URL: https://github.com/apache/geode/pull/5844#discussion_r542493639
##########
File path:
geode-docs/developing/querying_basics/restrictions_and_unsupported_features.html.md.erb
##########
@@ -30,6 +30,6 @@ At a high level, <%=vars.product_name%> does not support the
following querying
- You cannot create an index on fields using Set/List types (Collection
types) that are not comparable. The OQL index implementation expects fields to
be Comparable. To workaround this, you can create a custom Collection type that
implements Comparable.
- ORDER BY is only supported with DISTINCT queries.
-
+- OQL queries aren't pre-validated for references to nonexistent methods and
attributes.
Review comment:
I have commented on the ticket with my thoughts.
What could be added here is, saying OQL query engine determines the field or
methods on the given object (region keys and values) during query execution
time.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> User Guide - add disclaimer that OQL queries are not pre-validated for
> nonexistent attributes
> ---------------------------------------------------------------------------------------------
>
> Key: GEODE-7802
> URL: https://issues.apache.org/jira/browse/GEODE-7802
> Project: Geode
> Issue Type: Improvement
> Components: docs
> Reporter: Dave Barnes
> Priority: Minor
> Labels: pull-request-available
>
> Community member @deepak khopade requests that we add a disclaimer to the
> user guide stating that OQL queries are not pre-screened for references to
> nonexistent attributes. The assertion is that users who have experience with
> other query models may expect Geode to apply such validation. In the Geode
> model, attributes and methods are resolved at runtime during query execution
> - the server does not know what's actually stored in a region until the query
> is executed.
> The disclaimer could be added in one of two places:
> Query Language Restrictions and Unsupported Features
> ([https://geode.apache.org/docs/guide/111/developing/querying_basics/restrictions_and_unsupported_features.html])
> or
> Querying FAQ and Examples
> ([https://geode.apache.org/docs/guide/111/getting_started/querying_quick_reference.html])
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
