Should we keep the HOLDER.DEFAULT pattern to not create the default stop
set if not needed (when there is a custom building)?
Le mar. 2 juil. 2024 à 01:45, Chris Hostetter a
écrit :
>
> : There's also one other problem with those sets: Unfortunately they are
> : modifiable, because they are not
+1
SUCCESS! [0:41:14.593265]
Bruno
>
Ah, I started to work on this. So I just sent an incomplete PR[1] to share
with you Dawid, so you don't do the work twice. Feel free to modify the PR
if needed.
[1] https://github.com/apache/lucene/pull/13422
Le lun. 27 mai 2024 à 08:40, Dawid Weiss a écrit :
>
> Hi Mike,
>
> These changes are
If we increase the hppc fork to 23 classes and 14 test classes, then we can
remove the hppc dependency from all modules.
Do we agree that we should
- Increase the fork size
- Move it to oal.internal
- Remove the hppc dependency from everywhere
I can send a PR for this soon.
Dawid, for the size of
apache/lucene/pull/13392
>>> [2] https://github.com/elastic/elasticsearch/pull/109006
>>> [3] https://github.com/elastic/elasticsearch/pull/84168
>>>
>>> [*] HPPC-186: A different strategy has been implemented for collision
>>> aval
lasticsearch/pull/84168
>>>
>>> [*] HPPC-186: A different strategy has been implemented for collision
>>> avalanche avoidance. This results in removal of Scatter* maps and sets and
>>> their unification with their Hash* counterparts. This change should not
>>>
t's ok to 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 possib
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
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.
Tha
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 bee
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
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 w
>
> 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 rank/indexOf
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 11:
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.
*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 implementati
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
implementa
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
+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
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 a
dCommentId=13476920&page=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
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 Rousta
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 fi
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 expli
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 total
etaphi.de
>>>
>>> > -Original Message-
>>> > From: Michael Sokolov
>>> > Sent: Wednesday, March 23, 2022 2:03 PM
>>> > To: Lucene Dev
>>> > Subject: Lucene PM
+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 w
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 A
+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]
>>
>
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
+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 Drob
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.
>
> Oka
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, s
+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 sub
+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 wai
Congrats Julie!
Le jeu. 19 nov. 2020 à 11:38, Alessandro Benedetti a
écrit :
> Welcome onboard Julie!
> --
> Alessandro Benedetti
> Search Consultant, R&D Software Engineer, Director
> www.sease.io
>
>
> On Thu, 19 Nov 2020 at 03:23, Tomás Fernández Löbbe
> wrote:
>
>> W
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
S
+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
> http://www.linkedin.com
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
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
integra
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.
Thi
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 dev-tools/scripts/
SOLR-14422.
>
> On Jul 6, 2020, at 1:36 PM, Tomás Fernández Löbbe
> wrote:
>
> Just resolved SOLR-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 Jun 17, 2020, 12:27 PM -0500, Tomá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
thers:
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 :
>
>>
>
> 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:
>
>
> 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
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
[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...@gmail.com&
CloudSolrClient cannot be initialized using 'zkHosts'
>>>>> builder Blocker
>>>>> SOLR-14516 NPE during Realtime GET
>>>>> Major
>>>>> SOLR-14502 increase bin/solr's post kill sleep
>>>>>
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
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
;> +1
>>>
>>> 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 Bru
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 introduce
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
+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 hav
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
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 re
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
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 Lu
gt;
>>> I recommend the following changes to Lucene 8.5:
>>>
>>> These are "Improvements" that I think are better categorized as
>>> "Optimizations"
>>> * LUCENE-9211: Add compression for Binary doc value fields. (Mark
>>> Harw
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.
Le
;> 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
>
[
https://issues.apache.org/jira/browse/LUCENE-8920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924178#comment-16924178
]
Bruno Roustant edited comment on LUCENE-8920 at 9/6/19 11:5
[
https://issues.apache.org/jira/browse/LUCENE-8920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924178#comment-16924178
]
Bruno Roustant commented on LUCENE-8920:
I'd love to work on that
[
https://issues.apache.org/jira/browse/LUCENE-8920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923428#comment-16923428
]
Bruno Roustant edited comment on LUCENE-8920 at 9/5/19 8:4
[
https://issues.apache.org/jira/browse/LUCENE-8920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923463#comment-16923463
]
Bruno Roustant commented on LUCENE-8920:
Based on some heuristics, Di
[
https://issues.apache.org/jira/browse/LUCENE-8920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16923428#comment-16923428
]
Bruno Roustant commented on LUCENE-8920:
[~sokolov] There may be ano
[
https://issues.apache.org/jira/browse/LUCENE-8753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922609#comment-16922609
]
Bruno Roustant commented on LUCENE-8753:
Ok, I followed your advice to inc
[
https://issues.apache.org/jira/browse/LUCENE-8753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16906219#comment-16906219
]
Bruno Roustant commented on LUCENE-8753:
New [PR 828|https://github.com/ap
[
https://issues.apache.org/jira/browse/LUCENE-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1682#comment-1682
]
Bruno Roustant commented on LUCENE-8906:
PR a
[
https://issues.apache.org/jira/browse/LUCENE-8921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1630#comment-1630
]
Bruno Roustant commented on LUCENE-8921:
PR a
[
https://issues.apache.org/jira/browse/LUCENE-8921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16886889#comment-16886889
]
Bruno Roustant commented on LUCENE-8921:
Yes, sure. I could work on a PR
Bruno Roustant created LUCENE-8921:
--
Summary: IndexSearcher.termStatistics should not require
TermStates but docFreq and totalTermFreq
Key: LUCENE-8921
URL: https://issues.apache.org/jira/browse/LUCENE-8921
[
https://issues.apache.org/jira/browse/SOLR-11866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Roustant updated SOLR-11866:
--
Attachment: (was: SOLR-11866.patch)
> Support efficient subset matching in query elevat
[
https://issues.apache.org/jira/browse/SOLR-11866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Roustant updated SOLR-11866:
--
Attachment: (was:
0001-New-SubsetMatchElevationProvider-in-QueryElevationCo.patch
[
https://issues.apache.org/jira/browse/SOLR-11866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883819#comment-16883819
]
Bruno Roustant commented on SOLR-11866:
---
Also, the doc will need to be update
[
https://issues.apache.org/jira/browse/SOLR-11866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883816#comment-16883816
]
Bruno Roustant commented on SOLR-11866:
---
I have updated with PR [#780|h
[
https://issues.apache.org/jira/browse/LUCENE-8753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881046#comment-16881046
]
Bruno Roustant commented on LUCENE-8753:
I have created a related Jira i
[
https://issues.apache.org/jira/browse/LUCENE-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881037#comment-16881037
]
Bruno Roustant commented on LUCENE-8906:
This issue has been encountere
Bruno Roustant created LUCENE-8906:
--
Summary: Lucene50PostingsReader.postings() casts BlockTermState
param to private IntBlockTermState
Key: LUCENE-8906
URL: https://issues.apache.org/jira/browse/LUCENE-8906
Bruno Roustant created LUCENE-8836:
--
Summary: Optimize DocValues TermsDict to continue scanning from
the last position when possible
Key: LUCENE-8836
URL: https://issues.apache.org/jira/browse/LUCENE-8836
[
https://issues.apache.org/jira/browse/LUCENE-8753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839429#comment-16839429
]
Bruno Roustant commented on LUCENE-8753:
Beyond the performance aspects
[
https://issues.apache.org/jira/browse/LUCENE-8753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813171#comment-16813171
]
Bruno Roustant edited comment on LUCENE-8753 at 4/9/19 9:2
[
https://issues.apache.org/jira/browse/LUCENE-8753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813171#comment-16813171
]
Bruno Roustant commented on LUCENE-8753:
I agree.
We profile wikimediumall
[
https://issues.apache.org/jira/browse/LUCENE-8753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813106#comment-16813106
]
Bruno Roustant edited comment on LUCENE-8753 at 4/9/19 8:1
[
https://issues.apache.org/jira/browse/LUCENE-8753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813106#comment-16813106
]
Bruno Roustant edited comment on LUCENE-8753 at 4/9/19 8:1
[
https://issues.apache.org/jira/browse/LUCENE-8753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813106#comment-16813106
]
Bruno Roustant commented on LUCENE-8753:
It took me some time to
[
https://issues.apache.org/jira/browse/LUCENE-8753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809251#comment-16809251
]
Bruno Roustant commented on LUCENE-8753:
{quote}I think this is simila
[
https://issues.apache.org/jira/browse/LUCENE-8753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808852#comment-16808852
]
Bruno Roustant commented on LUCENE-8753:
{quote}Is it due to the fact tha
[
https://issues.apache.org/jira/browse/LUCENE-8753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Roustant updated LUCENE-8753:
---
Attachment: luceneutil.benchmark.txt
> New PostingFormat - UniformSp
[
https://issues.apache.org/jira/browse/LUCENE-8753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Roustant updated LUCENE-8753:
---
Description:
This is a proposal to add a new PostingsFormat called "UniformSplit&qu
[
https://issues.apache.org/jira/browse/LUCENE-8753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808799#comment-16808799
]
Bruno Roustant commented on LUCENE-8753:
Here's the Luceneutil bench
Bruno Roustant created LUCENE-8753:
--
Summary: New PostingFormat - UniformSplit
Key: LUCENE-8753
URL: https://issues.apache.org/jira/browse/LUCENE-8753
Project: Lucene - Core
Issue Type
[
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&focusedCommentId=16517247#comment-16517247
]
Bruno Roustant commented on SOLR-11865:
---
Thanks for your incredible help [~dsm
[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496788#comment-16496788
]
Bruno Roustant commented on SOLR-11865:
---
You'
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
1 - 100 of 156 matches
Mail list logo
