[infinispan-issues] [JBoss JIRA] (ISPN-3807) Caching of parsed HQL queries
Adrian Nistor (JIRA)
issues at jboss.org
Tue Dec 17 04:16:42 EST 2013
[ https://issues.jboss.org/browse/ISPN-3807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932001#comment-12932001 ]
Adrian Nistor commented on ISPN-3807:
-------------------------------------
I agree, this is a sensible step towards better performance. But there are some things we need to fix before this can work.
1. We need reliable support for parameters in the Hibernate Search HQL parser and not sure of its status now. Last time I tried using it (September) I was advised to avoid it as it was a bit too experimental.
2. Would be great if we had support for translating the 'order by'; right now it is recognized and ignored (there should be a HSEARCH jira but can't find it).
Having 1,2 sorted will mean our query is going to be a fixed string + a variable map of parameter values instead of (currently) being a variable string + a list of sort criteria.
Another related idea, would it be possible to cache the Lucene query object instead of caching the hql AST? Does lucene have params?
> Caching of parsed HQL queries
> -----------------------------
>
> Key: ISPN-3807
> URL: https://issues.jboss.org/browse/ISPN-3807
> Project: Infinispan
> Issue Type: Enhancement
> Components: Querying
> Affects Versions: 6.0.0.Final
> Reporter: Sanne Grinovero
> Assignee: Adrian Nistor
>
> We'll probably need to use a cache (lowercase) to avoid invoking ANTLR on each request.
> Ideally we could think of caching parameterized templates, or recognize constants: in case of constants the output could degenerate in caching a Lucene Filter.
> Priority do be defined after performance tests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list