Github user ashish-m-yh commented on the pull request:
https://github.com/apache/metamodel/pull/19#issuecomment-98772705
Thank you for the detailed comments. I concur in part - some corner cases
may need handling. Some kinds of queries, such as joins are rarely used in Solr
and the support is inefficient.
if executeQuery() is not implemented, then is there any other method which
makes sense to implement? If not, do you recommend deferring the release of
this till all corner cases are handled?
The module is almost useless if the actual search does not take place in
the engine itself, as users would generally use search engines for large data
sets, which practically cannot be read into the MetaModel application space and
searched in the MM layer. Hence, I was wondering if it has to be a all or
nothing approach and if we could throw exceptions for unsupported query
patterns and incrementally handle the rare query patterns too.
Do let me know your thoughts.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
