[
https://issues.apache.org/jira/browse/SOLR-13759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17004426#comment-17004426
]
mosh commented on SOLR-13759:
-----------------------------
Gus, you're absolutely right about the *FilterQuery* parsing part and I liked
the concept of treating each *FilterQuery* clause as an individual query and
parse it accordingly.
Once parsed the queries I understand the necessity of collecting the query
clauses and for appling our collection filtering logic but I am not quite sure
that I got how *QueryVisitor* will be our savior here.
I was not familiar with *QueyVisitor* but after reading about it (mostly going
through the code and digging down the LUCENE-3041 issue) it seems like it is
*Term* oriented and, on the other hand, the queries that are interesting us and
on which we are basing our optimization on are not consist of *Term*... or
maybe I am missing something...
I would be glad if you could explain deeply what's the idea of using
*QueryVisitor*.
Maybe overriding #Query.visit method and collecting the relevant part of the
query clauses is the way to go ?!
Thanks for the review!
> Optimize Queries when query filtering by TRA router.field
> ---------------------------------------------------------
>
> Key: SOLR-13759
> URL: https://issues.apache.org/jira/browse/SOLR-13759
> Project: Solr
> Issue Type: Sub-task
> Reporter: mosh
> Assignee: Gus Heck
> Priority: Minor
> Attachments: SOLR-13759.patch, SOLR-13759.patch,
> image-2019-12-09-22-45-51-721.png
>
>
> We are currently testing TRA using Solr 7.7, having >300 shards in the alias,
> with much growth in the coming months.
> The "hot" data(in our case, more recent) will be stored on stronger
> nodes(SSD, more RAM, etc).
> A proposal of optimizing queries will be by filtering query by date range, by
> that we will be able to querying the specific TRA collections taking
> advantage of the TRA mechanism of partitioning data based on date.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
