[
https://issues.apache.org/jira/browse/LUCENE-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16385824#comment-16385824
]
Bruno Roustant commented on LUCENE-8159:
----------------------------------------
Ok. I'll let you guys decide whether to discard this patch.
[~jpountz] I'm curious about searching a lot of fields.
{quote}searching over lots of fields is a bad practice
{quote}
Could you tell me the reason for the bad practice? Is it due to bad performance
impact? Are there other reasons by design?
Generally customer organizations love to have lots of fields. While I agree
that sometimes they should revisit their data partitioning, there are cases
where searching many fields help (e.g. CRM, field level security, ML ranking
model based on field matches)
> Add a copy constructor in AutomatonQuery to copy directly the compiled
> automaton
> --------------------------------------------------------------------------------
>
> Key: LUCENE-8159
> URL: https://issues.apache.org/jira/browse/LUCENE-8159
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Affects Versions: trunk
> Reporter: Bruno Roustant
> Assignee: David Smiley
> Priority: Major
> Attachments:
> 0001-Add-a-copy-constructor-in-AutomatonQuery-to-copy-dir.patch,
> LUCENE-8159.patch
>
>
> When the query is composed of multiple AutomatonQuery with the same automaton
> and which target different fields, it is much more efficient to reuse the
> already compiled automaton by copying it directly and just changing the
> target field.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
