You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@geode.apache.org by GitBox <gi...@apache.org> on 2020/12/14 15:52:50 UTC

[GitHub] [geode] agingade commented on a change in pull request #5844: GEODE-7802: Add disclaimer for OQL queries in UG

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:
users@infra.apache.org