[
https://issues.jboss.org/browse/ARTIF-722?page=com.atlassian.jira.plugin....
]
Brett Meyer commented on ARTIF-722:
-----------------------------------
WIP:
https://github.com/ArtificerRepo/artificer/compare/master...brmeyer:ARTIF...
If we go this route, it will have to wait until we no longer support EAP 6 (or can upgrade
to Hibernate 4.3.x). The DelayedPredicate concept relies on SPI that changed between
4.2/4.3. There may be a better way to do it, but...
Realistically, I'm not sure how useful this is. With proper indexing at the DB level,
the queries tend to be fast anyway. Users will also almost always be using paging,
further reducing the necessity for this level of improvement.
Re-visit sometime in the future.
Solely use Hibernate Search if query is limited to full-text search
and indexed columns
---------------------------------------------------------------------------------------
Key: ARTIF-722
URL:
https://issues.jboss.org/browse/ARTIF-722
Project: Artificer
Issue Type: Feature Request
Reporter: Brett Meyer
Assignee: Brett Meyer
Now that queries return a summary DTO, if a query only contains full-text search and
columns indexed by Lucene, Hibernate Search can be solely used. There is no need to also
execute the SQL query. For example:
/s-ramp/xsd/XsdDocument[xp2:matches(., 'FizzBuzz')]
Since 'model' and 'type' are both indexed, this could be accomplished
entirely with the Lucene query, skipping SQL.
This idea implies that all properties included in ArtifactSummary would need to be
indexed as well. SQL would be needed only when custom properties, ontologies, or
relationships are required.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)