GitHub user bruno-roustant opened a pull request:
https://github.com/apache/lucene-solr/pull/390
Refactor QueryElevationComponent to prepare query subset matching
[SOLR-11865]
See comments in https://issues.apache.org/jira/browse/SOLR-11865
You can merge this pull request
Github user bruno-roustant commented on the issue:
https://github.com/apache/lucene-solr/pull/390
@dsmiley here is the PR for QueryElevationComponent.
---
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
;> On Sat, 23 Nov, 2019, 10:35 PM David Smiley,
>>>>> wrote:
>>>>>
>>>>>> Congratulations and welcome Bruno! We always need more eyes on the
>>>>>> low level Lucene bits.
>>>>>>
>>>>>> ~ David Smiley
&
I like this new version. This clarifies the review, commit and CHANGES. As
a beginner in this process, it helps.
I appreciate the idea to have a "risk" section where we could list and say
a few words about some risky areas so that the contributor can announce
they might be impacted in reviews.
are better categorized as
>>> "Optimizations"
>>> * LUCENE-9211: Add compression for Binary doc value fields. (Mark
>>> Harwood)
>>> * LUCENE-4702: Better compression of terms dictionaries. (Adrien Grand)
>>> * LUCENE-9228: Sort dvUpdates in the
Welcome Alessandro!
Le ven. 27 mars 2020 à 17:02, Christine Poerschke (BLOOMBERG/ LONDON) <
cpoersc...@bloomberg.net> a écrit :
> Welcome Alessandro!
>
> Christine
>
> From: dev@lucene.apache.org At: 03/18/20 19:25:48
> Cc: dev@lucene.apache.org
> Subject: Re: Welcome Alessandro Benedetti as a
+1 for analysis within the PR workflow.
Le ven. 4 sept. 2020 à 06:38, David Smiley a écrit :
> Sounds great to me! I'm really glad to hear it works with the PR
> workflow, and only on the files touched in the PR.
>
> ~ David Smiley
> Apache Lucene/Solr Search Developer
>
Hi Ankur,
Indeed payloads are the standard way to solve this problem. For light
queries with a few top N results that should be efficient. For multi-term
queries that could become penalizing if you need to access the payloads of
too many terms.
Also, there is an experimental PostingsFormat called
Roustant <
broust...@apache.org>
gpg: key 377C3BA26AD29C0A: "Bruno Roustant " not
changed
gpg: Total number processed: 1
gpg: unchanged: 1
I still cannot connect to pgp.mit.edu
Le lun. 29 juin 2020 à 16:52, David Smiley a écrit :
> I've been trying to get B
NOTICE:
Branch branch_8_6 has been cut and versions updated to 8.7 on stable branch.
Please observe the normal rules:
* No new features may be committed to the branch.
* Documentation patches, build patches and serious bug fixes may be
committed to the branch. However, you should submit all
>
> Uwe
>
>
>
> -
>
> Uwe Schindler
>
> Achterdiek 19, D-28357 Bremen
>
> https://www.thetaphi.de
>
> eMail: u...@thetaphi.de
>
>
>
> *From:* Bruno Roustant
> *Sent:* Tuesday, June 30, 2020 3:02 PM
> *To:* dev@lucene.apache.org
> *Subj
[new branch] 0a1f68fafd6711304bbd7372567a359bcf36aab4 -> branch_8_6
Le mar. 30 juin 2020 à 14:59, Bruno Roustant a
écrit :
> I'm creating the branch_8_6 with the release wizard.
>
> Le mar. 30 juin 2020 à 12:37, Ishan Chattopadhyaya <
> ichattopadhy...@
nt cannot be initialized using 'zkHosts'
>>>>> builder Blocker
>>>>> SOLR-14516 NPE during Realtime GET
>>>>> Major
>>>>> SOLR-14502 increase bin/solr's post kill sleep
>>>>> Minor
>>>
t?
>
> I may be close to upgrading Zookeeper to 3.6.1, and very much do NOT want
> it in the 8.6 release as it should bake longer than 2 weeks even…
>
> Thanks for managing this release!
>
> Erick
>
> > On Jun 30, 2020, at 11:34 AM, Bruno Roustant
> wrote:
&
Please vote for release candidate 1 for Lucene/Solr 8.6.0
The artifacts can be downloaded from:
https://dist.apache.org/repos/dist/dev/lucene/lucene-solr-8.6.0-RC1-reva9c5fb0da2dfc8c7375622c80dbf1a0cc26f44dc
You can run the smoke tester directly with this command:
python3 -u
14590.
>
> On Mon, Jul 6, 2020 at 4:22 AM Ishan Chattopadhyaya <
> ichattopadhy...@gmail.com> wrote:
>
>> I'll take a look today, Bruno. Thanks.
>>
>> On Mon, 6 Jul, 2020, 4:32 pm Bruno Roustant,
>> wrote:
>>
>>> Hi all,
>>>
>>
omás Fernández Löbbe <
>>> tomasflo...@gmail.com>, wrote:
>>>
>>> +1. Thanks Bruno
>>>
>>> On Wed, Jun 17, 2020 at 6:22 AM Mike Drob wrote:
>>>
>>>> +1
>>>>
>>>> The release wizard python script should be sufficie
The Lucene PMC is pleased to announce the release of Apache Solr 8.6.0.
Solr is the popular, blazing fast, open source NoSQL search platform from
the Apache Lucene project. Its major features include powerful full-text
search, hit highlighting, faceted search, dynamic clustering, database
The Lucene PMC is pleased to announce the release of Apache Lucene 8.6.0.
Apache Lucene is a high-performance, full-featured text search engine
library written entirely in Java. It is a technology suitable for nearly
any application that requires full-text search, especially cross-platform.
:
Ukrainian analyzer, checksums verification, resource leaks fixes
Le mar. 30 juin 2020 à 19:38, Bruno Roustant a
écrit :
> Erick:
> AFAIK yes from now on a commit in branch_8x will not go to 8.6 branch.
>
> Le mar. 30 juin 2020 à 17:59, Erick Erickson a
> écrit :
>
>> Bru
;
>>> The release wizard python script should be sufficient for everything. If
>>> you run into any issues with it, let me know, I used it for 8.5.2 and think
>>> I understand it pretty well.
>>>
>>> On Tue, Jun 16, 2020 at 8:31 AM Bruno Roustant
>>
Hi
I've been reading the PGP/GPG key part of the ReleaseTodo doc.
https://cwiki.apache.org/confluence/display/LUCENE/ReleaseTodo
I created a 4K-bit key (with my apache.org email) and I uploaded it to MIT
key server pgp.mit.edu last Thursday.
But there is a line in the doc that says my key should
Atri, yes sure. More eyes to verify the steps.
Le mar. 16 juin 2020 à 16:38, Atri Sharma a écrit :
> Bruno,
>
> If you would want, I am willing to help you out in doing the 8.6 release.
> Will help learn the process as well.
>
> On Tue, 16 Jun 2020 at 19:01, Bruno Roustant
&g
+1
Le mar. 16 juin 2020 à 08:23, David Smiley a
écrit :
> +1 thanks
> ~ David
>
>
> On Fri, Jun 12, 2020 at 10:11 AM Erick Erickson
> wrote:
>
>> Short form:
>>
>> In a week or so, I propose to start failing compilations on master for
>> compiler warnings (exclusive of deprecations). If you
Hi all,
It’s been a while since we released Lucene/Solr 8.5.
I’d like to volunteer to be a release manager for an 8.6 release. If
there's agreement, then I plan to cut the release branch two weeks today,
on June 30th, and then to build the first RC two days later.
This will be my first time as
C - current logo
not PMC
Le mar. 16 juin 2020 à 21:38, Erik Hatcher a
écrit :
> C - current logo
>
> On Jun 15, 2020, at 6:08 PM, Ryan Ernst wrote:
>
> Dear Lucene and Solr developers!
>
> In February a contest was started to design a new logo for Lucene [1].
> That contest concluded, and I am
Congrats Ilan!
Le dim. 21 juin 2020 à 17:10, Yonik Seeley a écrit :
> Congrats Ilan!
> -Yonik
>
>
> On Sun, Jun 21, 2020 at 5:44 AM Noble Paul wrote:
>
>> Hi all,
>>
>> Please join me in welcoming Ilan Ginzburg as the latest Lucene/Solr
>> committer.
>> Ilan, it's tradition for you to
Welcome Mayya, congratulations!
Le mar. 9 juin 2020 à 09:10, Tomoko Uchida a
écrit :
> Hello Mayya,
> congratulations and welcome!
>
> Tomoko
>
>
> 2020年6月9日(火) 15:59 Adrien Grand :
>
>> Welcome, Mayya!
>>
>> On Mon, Jun 8, 2020 at 6:58 PM jim ferenczi wrote:
>>
>>> Hi all,
>>>
>>> Please join
Thanks!
The Release Wizard is a great help clearly. I'm going to open a Jira issue
to fix some glitches (links to update, some git command to improve, maybe
more explanation on some specific steps, etc)
Le mer. 15 juil. 2020 à 18:42, Erick Erickson a
écrit :
> +1
>
> > On Jul 15, 2020, at 11:06
+1 Thanks for volunteering
Le ven. 18 déc. 2020 à 01:41, Ishan Chattopadhyaya <
ichattopadhy...@gmail.com> a écrit :
> Sure, Houston. I'll wait another week. Have a good new year and merry
> Christmas!
>
> On Fri, 18 Dec, 2020, 5:58 am Timothy Potter,
> wrote:
>
>> Great point Houston! +1 on
Congrats Julie!
Le jeu. 19 nov. 2020 à 11:38, Alessandro Benedetti a
écrit :
> Welcome onboard Julie!
> --
> Alessandro Benedetti
> Search Consultant, R Software Engineer, Director
> www.sease.io
>
>
> On Thu, 19 Nov 2020 at 03:23, Tomás Fernández Löbbe
> wrote:
>
>>
Welcome Peter!
Le mer. 7 avr. 2021 à 09:11, Peter Gromov
a écrit :
> Thanks for the honor!
>
> (BTW I'm still not recognized by Github as having write access, and can't
> merge my pull requests :))
>
> > Peter, the tradition is that new committers introduce themselves with a
> brief bio.
>
>
Thank you Dawid!
Le jeu. 11 mars 2021 à 02:28, Michael Sokolov a écrit :
> Big thank you, Dawid, and Jan and others for taking the bull by the horns!
>
> On Wed, Mar 10, 2021, 3:14 PM Dawid Weiss wrote:
>
>> > Just tested out the main branch of the new repo, packaged, started,
>> loaded data,
+1
Le dim. 28 févr. 2021 à 22:23, Andi Vajda a écrit :
>
> On Sun, 28 Feb 2021, Jan Høydahl wrote:
>
> > Hi
> >
> > The general@ list is not being used for practically anything. I see
> some
> > user questions there and we announce releases. It may have had more
> > purpose when there were 5
Welcome Zach!
Le mar. 20 avr. 2021 à 10:59, Ishan Chattopadhyaya <
ichattopadhy...@gmail.com> a écrit :
> Congrats, Zach! Thanks for your contributions, looking forward to more!
>
> On Tue, 20 Apr, 2021, 2:26 pm Alan Woodward, wrote:
>
>> Congratulations and welcome!
>>
>> > On 19 Apr 2021, at
+1 (binding)
Ran the smoke tester successfully.
Bruno
Le jeu. 8 avr. 2021 à 04:38, Anshum Gupta a écrit :
> +1 (binding)
>
> Ran a sample indexing/search app and browsed through the admin UI.
>
> Smoketester is happy!
>
> SUCCESS! [1:05:05.761354]
>
>
> On Tue, Apr 6, 2021 at 3:45 PM Mike
+1
SUCCESS! [1:17:35.209577]
Le jeu. 11 nov. 2021 à 18:30, Julie Tibshirani a
écrit :
> +1 (nonbinding)
> SUCCESS! [1:04:58.967300]
>
> On Thu, Nov 11, 2021 at 7:12 AM David Smiley wrote:
>
>> +1
>> SUCCESS! [0:57:23.948714]
>>
>
+1 Thanks Julie
Le ven. 25 févr. 2022 à 13:58, Michael Sokolov a
écrit :
> +1 thanks for volunteering
>
> On Thu, Feb 24, 2022, 5:41 AM Mayya Sharipova
> wrote:
>
>> + 1
>>
>> On Thu, Feb 24, 2022 at 11:28 AM Ignacio Vera wrote:
>>
>>> +1
>>>
>>> On Thu, Feb 24, 2022 at 9:05 AM Adrien Grand
>>>
>>> > -Original Message-
>>> > From: Michael Sokolov
>>> > Sent: Wednesday, March 23, 2022 2:03 PM
>>> > To: Lucene Dev
>>> > Subject: Lucene PMC Chair Br
Welcome!
Le mar. 25 janv. 2022 à 22:38, Vigya Sharma a
écrit :
> Congratulations Feng!
>
> On Tue, Jan 25, 2022 at 1:12 PM Julie Tibshirani
> wrote:
>
>> Welcome!!
>>
>> On Tue, Jan 25, 2022 at 11:00 AM Marcus Eagan
>> wrote:
>>
>>> Congratulations Feng!
>>>
>>> On Tue, Jan 25, 2022 at 10:51
Welcome, congratulations!
Le ven. 20 oct. 2023 à 10:02, Dawid Weiss a écrit :
>
> Congratulations, Luca!
>
> On Fri, Oct 20, 2023 at 7:51 AM Adrien Grand wrote:
>
>> I'm pleased to announce that Luca Cavanna has accepted an invitation to
>> join the Lucene PMC!
>>
>> Congratulations Luca, and
Welcome Greg!
Le mar. 7 juin 2022 à 08:37, Adrien Grand a écrit :
> I'm pleased to announce that Greg Miller has accepted an invitation to
> join the Lucene PMC!
>
> Congratulations Greg, and welcome aboard!
>
> --
> Adrien
>
+0 (PMC)
While I like the simplification, I'm a little concerned by the risk of
disruption in history.
Le mar. 7 juin 2022 à 05:07, Tomoko Uchida a
écrit :
> I'm sorry there was a mistake in the important date. This is the
> corrected version.
>
> ==
> this vote received 13 ballots in
MergePolicy "find merges" methods take a MergeTrigger as parameter, except
findForcedMerges() and findForcedDeletesMerges().
In my use-case, I could leverage a MergeTrigger in findForcedMerges(),
which can be EXPLICIT or MERGE_FINISHED, to differentiate the merge
selection between the initial
orcedMerges` to never run cascaded merges:
> https://issues.apache.org/jira/browse/LUCENE-7020.
>
> On Mon, Jun 20, 2022 at 10:31 AM Bruno Roustant
> wrote:
>
>> MergePolicy "find merges" methods take a MergeTrigger as parameter,
>> except findForcedMerges() and
with the
other find merges methods.
Le lun. 20 juin 2022 à 14:26, Adrien Grand a écrit :
> Wouldn't this be a bug in the AlwaysForceMergePolicy, which should return
> no merges if there is already a single segment with no deletes?
>
> On Mon, Jun 20, 2022 at 1:30 PM Bruno Roustant
> w
ocusedCommentId=13476920=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13476920
> .
>
> On Mon, Jun 20, 2022 at 3:26 PM Bruno Roustant
> wrote:
>
>> I agree this AlwaysForceMergePolicy is not working correctly. It's just a
>> test I did to easily understand how MergeTrigger.M
Welcome!
Le jeu. 6 oct. 2022 à 11:20, Michael Sokolov a écrit :
> Welcome Luca!
>
> On Thu, Oct 6, 2022, 1:05 AM 陆徐刚 wrote:
>
>> Welcome!
>>
>> Xugang
>>
>> https://github.com/LuXugang
>>
>> On Oct 6, 2022, at 13:59, Mikhail Khludnev wrote:
>>
>>
>> Welcome, Luca.
>>
>> On Wed, Oct 5, 2022
+1
Thanks Luca!
Le lun. 16 janv. 2023 à 16:04, Ignacio Vera a écrit :
> +1
>
> On Mon, Jan 16, 2023 at 12:58 PM Alan Woodward
> wrote:
>
>> +1, thanks Luca!
>>
>> On 13 Jan 2023, at 09:54, Luca Cavanna wrote:
>>
>> Hi all,
>> I'd like to propose that we release Lucene 9.5.0. There is a decent
Hello Lucene developers,
Lucene Program Management Committee has elected a new chair, Greg Miller,
and the Board has approved.
Greg, thank you for stepping up, and congratulations!
- Bruno
I vote for option 3.
Then with a follow up work to have a simple extension codec in the "codecs"
package which is
1- not backward compatible, and 2- has a higher or configurable limit. That
way users can directly use this codec without any additional code.
>
> Wow, this looks very relevant to Lucene! Could this index be used for
> faster implementation of our skip lists? Even though they are static
> (computed once at segment-write time) vs dynamic/online that these learned
> indices are also able to handle, it looks like learned indices are still
Interesting coincidence, I'm currently working on a learned index on sorted
keys that can advantageously replace binary search.
It is very compact (additional space of 2% of the sorted key array, e.g.
40KB for 200MB of keys), and it is between 2x to 3x faster than binary
search for the
Welcome Chris!
Le mer. 21 juin 2023 à 13:43, Chris Hegarty
a écrit :
> Thank you all for the warm welcome. Happy to be included in this very
> talented group of individuals :-)
>
> -Chris.
>
> On 21 Jun 2023, at 09:31, Uwe Schindler wrote:
>
> Welcome Chris.
>
> Uwe
>
>
> Am 19. Juni 2023
*Proposed option:* Move the max dimension limit lower level to a HNSW
specific implementation. Once there, this limit would not bind any other
potential vector engine alternative/evolution.
*Motivation:* There seem to be contradictory performance interpretations
about the current HNSW
I agree with Robert Muir that an increase of the 1024 limit as it is
currently in FloatVectorValues or ByteVectorValues would bind the API, we
could not decrease it after, even if we needed to change the vector engine.
Would it be possible to move the limit definition to a HNSW specific
Thank you Chris, congrats!
And of course thank you Greg for the past year!
Le sam. 20 janv. 2024 à 01:15, Greg Miller a écrit :
> Hello Lucene developers-
>
> I wanted to let you know that the Lucene PMC has elected a new Chair—Chris
> Hegarty—and the board has approved the appointment. It's
Congrats Stefan!
Le sam. 20 janv. 2024 à 08:26, Michael Wechner
a écrit :
> Hi Stefan, thank you very much for your contributions and helping to
> improve Lucene!
>
> All the best
>
> Michael
>
> Am 19.01.24 um 20:03 schrieb Stefan Vodita:
>
> Thank you all! It's an honor to join the project as
propagate it to other
> modules? I'm not really sure how much impact it'll have downstream.
>
> D.
>
> On Sat, May 18, 2024 at 5:26 PM Bruno Roustant
> wrote:
>
>> The facet module has a dependency on com.carrotsearch:hppc.
>>
>> Is it possible to add the same depend
Hi,
While looking at the various usages of Map with Integer keys, I found
ja.dict.UserDictionary with its lookup() method where there is a *TODO: can
we avoid this treemap/toIndexArray?*
I could propose something, but I would like to know how much it is used,
and if it is worth improving it.
The facet module has a dependency on com.carrotsearch:hppc.
Is it possible to add the same dependency to the join module ? What is the
rule ?
Thanks
Bruno
Bruno Roustant created SOLR-6613:
Summary: TextField.analyzeMultiTerm should not throw exception
when analyzer returns no term
Key: SOLR-6613
URL: https://issues.apache.org/jira/browse/SOLR-6613
[
https://issues.apache.org/jira/browse/SOLR-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Roustant updated SOLR-6613:
-
Attachment: TestTextField.java
TextField.analyzeMultiTerm should not throw exception when
[
https://issues.apache.org/jira/browse/SOLR-6613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Roustant updated SOLR-6613:
-
Description:
In TextField.analyzeMultiTerm()
at line
try {
if (!source.incrementToken
[
https://issues.apache.org/jira/browse/LUCENE-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465767#comment-16465767
]
Bruno Roustant commented on LUCENE-8292:
I just realized that the current no-default-override
[
https://issues.apache.org/jira/browse/LUCENE-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16465887#comment-16465887
]
Bruno Roustant commented on LUCENE-8292:
[~dsmiley], if I create a subclass of FilterTermsEnum
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456470#comment-16456470
]
Bruno Roustant commented on SOLR-11865:
---
Actually the TrieSubsetMatcher introduced by the next patch
[
https://issues.apache.org/jira/browse/LUCENE-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475579#comment-16475579
]
Bruno Roustant commented on LUCENE-8292:
Actually there is also another related issue
[
https://issues.apache.org/jira/browse/LUCENE-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475579#comment-16475579
]
Bruno Roustant edited comment on LUCENE-8292 at 5/15/18 9:57 AM
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476032#comment-16476032
]
Bruno Roustant commented on SOLR-11865:
---
Great! I agree with all your points [~dsmiley].
Indeed
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Roustant closed SOLR-11865.
-
Work done
> Refactor QueryElevationComponent to prepare query subset match
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517247#comment-16517247
]
Bruno Roustant commented on SOLR-11865:
---
Thanks for your incredible help [~dsmiley]!
Closing
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16496788#comment-16496788
]
Bruno Roustant commented on SOLR-11865:
---
You're right MapElevationProvider.buildElevationMap should
[
https://issues.apache.org/jira/browse/LUCENE-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462394#comment-16462394
]
Bruno Roustant edited comment on LUCENE-8292 at 5/3/18 1:03 PM:
When
[
https://issues.apache.org/jira/browse/LUCENE-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462368#comment-16462368
]
Bruno Roustant commented on LUCENE-8292:
1- "Not possible to override": I was
[
https://issues.apache.org/jira/browse/LUCENE-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462394#comment-16462394
]
Bruno Roustant commented on LUCENE-8292:
When looking at TermsEnum API, what I understand
Bruno Roustant created LUCENE-8292:
--
Summary: Fix FilterLeafReader.FilterTermsEnum to delegate all
seekExact methods
Key: LUCENE-8292
URL: https://issues.apache.org/jira/browse/LUCENE-8292
Project
[
https://issues.apache.org/jira/browse/LUCENE-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Roustant updated LUCENE-8292:
---
Attachment: LUCENE-8292.patch
0001-Fix-FilterLeafReader.FilterTermsEnum
[
https://issues.apache.org/jira/browse/LUCENE-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462409#comment-16462409
]
Bruno Roustant edited comment on LUCENE-8292 at 5/3/18 1:08 PM:
Another
[
https://issues.apache.org/jira/browse/LUCENE-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462409#comment-16462409
]
Bruno Roustant commented on LUCENE-8292:
Another option would be to modify
Bruno Roustant created SOLR-11866:
-
Summary: Support efficient subset matching in query elevation rules
Key: SOLR-11866
URL: https://issues.apache.org/jira/browse/SOLR-11866
Project: Solr
Bruno Roustant created SOLR-11865:
-
Summary: Refactor QueryElevationComponent to prepare query subset
matching
Key: SOLR-11865
URL: https://issues.apache.org/jira/browse/SOLR-11865
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-11866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Roustant updated SOLR-11866:
--
Attachment: SOLR-11866.patch
0001-New-SubsetMatchElevationProvider
Bruno Roustant created LUCENE-8159:
--
Summary: Add a copy constructor in AutomatonQuery to copy directly
the compiled automaton
Key: LUCENE-8159
URL: https://issues.apache.org/jira/browse/LUCENE-8159
[
https://issues.apache.org/jira/browse/LUCENE-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Roustant updated LUCENE-8159:
---
Attachment: LUCENE-8159.patch
0001-Add-a-copy-constructor-in-AutomatonQuery
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Roustant updated SOLR-11865:
--
Attachment: SOLR-11865.patch
0001-Refactor-QueryElevationComponent-to-introduce
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Roustant updated SOLR-11865:
--
Attachment: (was: SOLR-11865.patch)
> Refactor QueryElevationComponent to prepare qu
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Roustant updated SOLR-11865:
--
Attachment: SOLR-11865.patch
0003-Remove-exception-handlers-and-refactor
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426589#comment-16426589
]
Bruno Roustant commented on SOLR-11865:
---
New delta patch with the modification mentioned
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426589#comment-16426589
]
Bruno Roustant edited comment on SOLR-11865 at 4/5/18 7:44 AM:
---
New delta
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450065#comment-16450065
]
Bruno Roustant commented on SOLR-11865:
---
Sorry for the delay.
Yes, if you can take it from here
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16450065#comment-16450065
]
Bruno Roustant edited comment on SOLR-11865 at 4/24/18 3:37 PM:
Sorry
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420302#comment-16420302
]
Bruno Roustant commented on SOLR-11865:
---
4- No "Can be overridden by extending this class&qu
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420301#comment-16420301
]
Bruno Roustant commented on SOLR-11865:
---
3- The indentation around line ~671 (contents
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Roustant updated SOLR-11865:
--
Attachment: SOLR-11865.patch
> Refactor QueryElevationComponent to prepare query sub
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Roustant updated SOLR-11865:
--
Attachment: (was: SOLR-11865.patch)
> Refactor QueryElevationComponent to prepare qu
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420300#comment-16420300
]
Bruno Roustant commented on SOLR-11865:
---
2- ElevationProvider should be immutable and simplified
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420322#comment-16420322
]
Bruno Roustant commented on SOLR-11865:
---
10- seen.contains(id) == false.
I didn't know this Lucene
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420317#comment-16420317
]
Bruno Roustant commented on SOLR-11865:
---
8- Use a UnaryOperator instead of IndexedValueProvider
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16420329#comment-16420329
]
Bruno Roustant commented on SOLR-11865:
---
11- subsetMatch flag in ElevatingQuery.
Yes, the idea
1 - 100 of 150 matches
Mail list logo