Codec API
>> change, maybe to optimize a interesting use-cases, and then we must do some
>> development to fix N-2 BWC codec (as well as N-1 BWC codec that we already
>> must fix for such an example, today).
>>
>> Some users seem to keep their indices alive for a v
I personally have pretty positive experience with what I call softlimits. At
elastic we use them all over the place to catch issues when a user likely
misconfigures something or if there is likely a issue on the users end.
I think having an option on the IW that allows to limit the
innovation. So in
> practice that means that queries that require some specific file format or
> analyzers that change behaviors in major versions would not be part of the
> extended guarantee.
>
>
> Le mer. 6 janv. 2021 à 21:53, Yonik Seeley a écrit :
>>
>> O
John, can you explain what the usecase for such a new API is? I don't
see a user of the API in your code. Is there a query you can optimize
with this or what is the reasoning behind this change? I personally
think it's quite invasive to add this information and there must be a
good reason to add
Hello all,
Currently Lucene supports reading and writing indices that have been
created with the current or previous (N-1) version of Lucene. Lucene
refuses to open an index created by N-2 or earlier versions.
I would like to propose that Lucene adds support for opening indices
created by version
you can do something similar to this today by exploiting the
add/updateDocuments(Iterable doc) API. All docs in
this iterable will be sent to the same segment in order. If you have
multiple threads you can feed a defined number of docs per iterable
(stream them to be memory efficient) and then let
Eric, thanks so much for your open and true words! You will always be
part of this community if you subscribed to the lists or not. (you
can't escape :D) Thanks for your contributions, this is a team effort
and you are a part of it.
enjoy the welding!!
simon
On Wed, Dec 30, 2020 at 3:09 PM
Thank you ryan for pushing on this, being persistent and getting the vote
out.
On Tue, Sep 8, 2020 at 5:55 PM Ryan Ernst wrote:
> This vote is now closed. The results are as follows:
>
> Binding Results
> A1: 12 (55%)
> D: 6 (27%)
> A2: 4 (18%)
>
> All Results
> A1: 16 (55%)
> D: 7
A1, A2, D (binding)
On Thu, Sep 3, 2020 at 7:09 AM Noble Paul wrote:
> A1, A2, D binding
>
> On Thu, Sep 3, 2020 at 7:22 AM Jason Gerlowski
> wrote:
> >
> > A1, A2, D (binding)
> >
> > On Wed, Sep 2, 2020 at 10:47 AM Michael McCandless
> > wrote:
> > >
> > > A2, A1, C5, D (binding)
> > >
> >
+1 binding release looks good to me
On Thu, Aug 27, 2020 at 3:58 PM Atri Sharma wrote:
>
> +1 (binding)
>
> SUCCESS! [1:14:17.24939]
>
> On Thu, 27 Aug 2020 at 18:41, Michael Sokolov wrote:
>>
>> SUCCESS! [0:56:28.589654]
>>
>>
>>
>> +1
>>
>>
>>
>> On Wed, Aug 26, 2020 at 12:41 PM Nhat Nguyen
I'd actually like to build the RC earlier than the end of the week.
Unless somebody objects I'd like to build one tonight or tomorrow.
simon
On Tue, Aug 25, 2020 at 7:52 AM Ishan Chattopadhyaya
wrote:
>
> Thanks Simon and Ignacio!
>
> On Tue, 25 Aug, 2020, 11:21 am Simon Willnaue
+1 thank you! I was about to write the same email. Lets sync on the RM
I can certainly help... I need to go and find my code signing key
first :)
simon
On Tue, Aug 25, 2020 at 7:49 AM Ignacio Vera wrote:
>
> Hi,
>
> I propose a 8.6.2 bugfix release and I volunteer as RM. The motivation for
>
I thinks it’s fixed now. The 7.7.3 version was missing.
Simon
> On 16. May 2020, at 22:45, Erick Erickson wrote:
>
> Unfortunately the seed doesn’t reproduce, and I tried beasting it without
> getting any fails in 700 iterations (and counting).
>
> Here’s one example, I see three others in
I agree this is not a code change category vote. It’s a majority vote. -1s are
not vetos.
Simon
> On 12. May 2020, at 21:17, Atri Sharma wrote:
>
>
> I would argue against that — this is more of a project level decision with no
> changes to the core code base per se — more of restructuring
+1 binding
Sent from a mobile device
> On 12. May 2020, at 13:33, Jason Gerlowski wrote:
>
> -1 (binding)
>
>> On Tue, May 12, 2020 at 7:31 AM Alan Woodward wrote:
>>
>> +1 (binding)
>>
>> Alan Woodward
>>
On 12 May 2020, at 12:06, Jan Høydahl wrote:
>>>
>>> +1 (binding)
>>>
>>>
On Sun, May 10, 2020 at 3:41 PM Bram Van Dam wrote:
>
> On 10/05/2020 08:20, David Smiley wrote:
> > An idea just occurred to me that may help make a split nicer for Solr
> > than it is today. Solr could use a branch of the Lucene project that's
> > used for the Solr project.
>
> Maybe I'm alone
I can speak from experience that working with a snapshot is much
cleaner than working with submodules. We do this in elasticsearch for
a very long time now and our process here works just fine. It has a
bunch of advantages over a direct / source dependency like solr has
right now. I recall that
[
https://issues.apache.org/jira/browse/LUCENE-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16906502#comment-16906502
]
Simon Willnauer commented on LUCENE-8369:
-
+1 for option 1 above as well. Thanks [~nknize
[
https://issues.apache.org/jira/browse/LUCENE-8369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16902133#comment-16902133
]
Simon Willnauer commented on LUCENE-8369:
-
I don't think we should scarify the existence
[
https://issues.apache.org/jira/browse/LUCENE-8887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-8887.
-
Resolution: Duplicate
this seems to be opened accidentially
> CLONE - Add sett
[
https://issues.apache.org/jira/browse/LUCENE-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872690#comment-16872690
]
Simon Willnauer commented on LUCENE-8865:
-
[~hypothesisx86] I didn't run any benchmarks. maybe
[
https://issues.apache.org/jira/browse/LUCENE-8857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16868555#comment-16868555
]
Simon Willnauer commented on LUCENE-8857:
-
A couple of comments:
* can you open a PR
[
https://issues.apache.org/jira/browse/LUCENE-8865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-8865.
-
Resolution: Fixed
Fix Version/s: 8.2
master (9.0)
>
[
https://issues.apache.org/jira/browse/LUCENE-8857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866575#comment-16866575
]
Simon Willnauer commented on LUCENE-8857:
-
Why don't we just use the comparator and have
[
https://issues.apache.org/jira/browse/LUCENE-8853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-8853.
-
Resolution: Fixed
Fix Version/s: 8.2
master (9.0
[
https://issues.apache.org/jira/browse/LUCENE-8857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16866253#comment-16866253
]
Simon Willnauer commented on LUCENE-8857:
-
>From my perspective we should simplify this e
Simon Willnauer created LUCENE-8865:
---
Summary: Use incoming thread for execution if IndexSearcher has
an executor
Key: LUCENE-8865
URL: https://issues.apache.org/jira/browse/LUCENE-8865
Project
[
https://issues.apache.org/jira/browse/LUCENE-8829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863067#comment-16863067
]
Simon Willnauer commented on LUCENE-8829:
-
{quote}
Simon Willnauer That is a fun idea, although
[
https://issues.apache.org/jira/browse/LUCENE-8829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861848#comment-16861848
]
Simon Willnauer edited comment on LUCENE-8829 at 6/12/19 8:56 AM:
--
I'd
[
https://issues.apache.org/jira/browse/LUCENE-8829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861848#comment-16861848
]
Simon Willnauer commented on LUCENE-8829:
-
I'd remove the _ setShardIndex_ parameter alltogether
[
https://issues.apache.org/jira/browse/LUCENE-8829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861821#comment-16861821
]
Simon Willnauer commented on LUCENE-8829:
-
I do wonder if we can simplify this API now that we
[
https://issues.apache.org/jira/browse/LUCENE-8853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16861785#comment-16861785
]
Simon Willnauer commented on LUCENE-8853:
-
I attached a PR but I am not really happy
Simon Willnauer created LUCENE-8853:
---
Summary: FileSwitchDirectory is broken if temp outputs are used
Key: LUCENE-8853
URL: https://issues.apache.org/jira/browse/LUCENE-8853
Project: Lucene - Core
[
https://issues.apache.org/jira/browse/LUCENE-8835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-8835.
-
Resolution: Fixed
Assignee: Simon Willnauer
Fix Version/s: 8.2
[
https://issues.apache.org/jira/browse/LUCENE-8833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858441#comment-16858441
]
Simon Willnauer commented on LUCENE-8833:
-
I do like the idea of #warm but the footprint is much
[
https://issues.apache.org/jira/browse/LUCENE-8833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16857525#comment-16857525
]
Simon Willnauer commented on LUCENE-8833:
-
> what would the iocontext provide to b
Simon Willnauer created LUCENE-8835:
---
Summary: Respect file extension when listing files form
FileSwitchDirectory
Key: LUCENE-8835
URL: https://issues.apache.org/jira/browse/LUCENE-8835
Project
[
https://issues.apache.org/jira/browse/LUCENE-8833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856781#comment-16856781
]
Simon Willnauer commented on LUCENE-8833:
-
you are correct that's what elasticsearch does. Yet
Simon Willnauer created LUCENE-8833:
---
Summary: Allow subclasses of MMapDirecory to preload individual
IndexInputs
Key: LUCENE-8833
URL: https://issues.apache.org/jira/browse/LUCENE-8833
Project
[
https://issues.apache.org/jira/browse/LUCENE-8809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16856364#comment-16856364
]
Simon Willnauer commented on LUCENE-8809:
-
[~dnhatn] can we close this issue?
> Refr
[
https://issues.apache.org/jira/browse/LUCENE-8813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-8813.
-
Resolution: Fixed
Fix Version/s: 8.2
master (9.0
[
https://issues.apache.org/jira/browse/LUCENE-8813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16849506#comment-16849506
]
Simon Willnauer commented on LUCENE-8813:
-
I looked at this and I think the issue here
[
https://issues.apache.org/jira/browse/LUCENE-8757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16843726#comment-16843726
]
Simon Willnauer commented on LUCENE-8757:
-
[~atris] can we instead of asserting the order just
oject: Lucene - Core
>> Issue Type: Improvement
>> Reporter: Atri Sharma
>> Assignee: Simon Willnauer
>> Priority: Major
>>Attachments: LUCENE-8757.patch, LUCENE-8757.patch, LUCENE-8757.patch,
>> LUCENE-8757.patch
&g
[
https://issues.apache.org/jira/browse/LUCENE-8757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer reassigned LUCENE-8757:
---
Assignee: Simon Willnauer
> Better Segment To Thread Mapping Algori
[
https://issues.apache.org/jira/browse/LUCENE-8757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16837615#comment-16837615
]
Simon Willnauer commented on LUCENE-8757:
-
LGTM I will try to commit this in the coming days
[
https://issues.apache.org/jira/browse/LUCENE-8757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16837003#comment-16837003
]
Simon Willnauer commented on LUCENE-8757:
-
{quote}
I think there is an important justification
[
https://issues.apache.org/jira/browse/LUCENE-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835894#comment-16835894
]
Simon Willnauer commented on LUCENE-8785:
-
{quote} Please feel free to commit
[
https://issues.apache.org/jira/browse/LUCENE-8757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835481#comment-16835481
]
Simon Willnauer commented on LUCENE-8757:
-
Thanks for the additional iteration, now that we
[
https://issues.apache.org/jira/browse/LUCENE-7840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835473#comment-16835473
]
Simon Willnauer commented on LUCENE-7840:
-
LGTM
> BooleanQuery.rewriteNoScoring - optimize a
[
https://issues.apache.org/jira/browse/LUCENE-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-8785.
-
Resolution: Fixed
> TestIndexWriterDelete.testDeleteAllNoDeadlock fail
[
https://issues.apache.org/jira/browse/LUCENE-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-8785:
Fix Version/s: (was: 8.0.1)
(was: 8.1
[
https://issues.apache.org/jira/browse/LUCENE-7840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834778#comment-16834778
]
Simon Willnauer commented on LUCENE-7840:
-
I think there are some style issues in this patch
[
https://issues.apache.org/jira/browse/LUCENE-8757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834767#comment-16834767
]
Simon Willnauer commented on LUCENE-8757:
-
[~atris] I think the assertion in this part doesn't
[
https://issues.apache.org/jira/browse/LUCENE-8757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834525#comment-16834525
]
Simon Willnauer commented on LUCENE-8757:
-
[~atris] actually I thought about these defaults
[
https://issues.apache.org/jira/browse/LUCENE-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-8785:
Fix Version/s: 7.7.1
master (9.0)
8.1
[
https://issues.apache.org/jira/browse/LUCENE-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer reassigned LUCENE-8785:
---
Assignee: Simon Willnauer
> TestIndexWriterDelete.testDeleteAllNoDeadlock fail
[
https://issues.apache.org/jira/browse/LUCENE-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16834467#comment-16834467
]
Simon Willnauer commented on LUCENE-8785:
-
{quote}
If there is another thread coming in after we
[
https://issues.apache.org/jira/browse/LUCENE-8757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1683#comment-1683
]
Simon Willnauer commented on LUCENE-8757:
-
> Would it make sense to push this pa
[
https://issues.apache.org/jira/browse/LUCENE-8757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832343#comment-16832343
]
Simon Willnauer commented on LUCENE-8757:
-
Thanks [~atris], can you bring back the javadocs
[
https://issues.apache.org/jira/browse/LUCENE-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832336#comment-16832336
]
Simon Willnauer commented on LUCENE-8785:
-
{quote} I realize neither ES nor Solr expose
[
https://issues.apache.org/jira/browse/LUCENE-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831635#comment-16831635
]
Simon Willnauer commented on LUCENE-8785:
-
> But at the point we call clear() haven't we alre
[
https://issues.apache.org/jira/browse/LUCENE-8785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831612#comment-16831612
]
Simon Willnauer commented on LUCENE-8785:
-
[~mikemccand] I think this is caused by the fact
[
https://issues.apache.org/jira/browse/LUCENE-8776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831604#comment-16831604
]
Simon Willnauer commented on LUCENE-8776:
-
[~venkat11] I do understand your frustration. Believe
[
https://issues.apache.org/jira/browse/LUCENE-8757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831591#comment-16831591
]
Simon Willnauer commented on LUCENE-8757:
-
Hey Atri,
thanks for putting up this patch, here
[
https://issues.apache.org/jira/browse/LUCENE-8671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-8671.
-
Resolution: Fixed
Assignee: Simon Willnauer
Fix Version/s: master (9.0
[
https://issues.apache.org/jira/browse/LUCENE-8754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-8754.
-
Resolution: Fixed
Fix Version/s: master (9.0)
8.1
Awesome! Welcome to this group as a committer! It’s always special to grow a
committer base!
Simon
> On 9. Apr 2019, at 06:00, Tomás Fernández Löbbe wrote:
>
> Welcome!
>
>> On Mon, Apr 8, 2019 at 5:27 PM Christian Moen wrote:
>> Congratulations, Tomoko-san!
>>
>>> On Tue, Apr 9, 2019 at
Simon Willnauer created LUCENE-8754:
---
Summary: SegmentInfo#toString can cause
ConcurrentModificationException
Key: LUCENE-8754
URL: https://issues.apache.org/jira/browse/LUCENE-8754
Project: Lucene
[
https://issues.apache.org/jira/browse/LUCENE-8735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801820#comment-16801820
]
Simon Willnauer commented on LUCENE-8735:
-
thanks henning
> FileAlreadyExistsException af
[
https://issues.apache.org/jira/browse/LUCENE-8735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-8735.
-
Resolution: Fixed
Assignee: Simon Willnauer
Fix Version/s: 7.7.1
I pushed a fix for this, sorry for the noise. test-bug
On Thu, Mar 21, 2019 at 9:38 AM Dawid Weiss wrote:
> Ping. Jenkins builds fail on an assertion related to the recent
> changes in fst off-heap?
>
> D.
>
> On Thu, Mar 21, 2019 at 6:46 AM Policeman Jenkins Server
> wrote:
> >
> > Build:
I pushed a fix for this, sorry for the noise
On Thu, Mar 21, 2019 at 10:27 AM Policeman Jenkins Server <
jenk...@thetaphi.de> wrote:
> Build: https://jenkins.thetaphi.de/job/Lucene-Solr-8.x-Linux/288/
> Java: 32bit/jdk1.8.0_172 -client -XX:+UseSerialGC
>
> 6 tests failed.
> FAILED:
>
+1 - Java 8 EOLed last year - moving on in 2020 is reasonable and it's our
responsibility to move with the platform we are running on.
simon
On Wed, Mar 20, 2019 at 9:27 AM Jan Høydahl wrote:
> +1
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
>
> 19. mar.
[
https://issues.apache.org/jira/browse/LUCENE-8700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-8700.
-
Resolution: Invalid
We settled on the PR that IndexWriter#flushNextBuffer is sufficient
[
https://issues.apache.org/jira/browse/LUCENE-8692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16790895#comment-16790895
]
Simon Willnauer commented on LUCENE-8692:
-
> rollback gives you a way to close IndexWri
[
https://issues.apache.org/jira/browse/LUCENE-8692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16789320#comment-16789320
]
Simon Willnauer commented on LUCENE-8692:
-
{quote}
It definitely seems like there should
[
https://issues.apache.org/jira/browse/LUCENE-8671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785703#comment-16785703
]
Simon Willnauer commented on LUCENE-8671:
-
I don't think we should add a setter to FieldInfo
[
https://issues.apache.org/jira/browse/LUCENE-8692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785625#comment-16785625
]
Simon Willnauer commented on LUCENE-8692:
-
{quote}
For now I've updated the patch to take
[
https://issues.apache.org/jira/browse/LUCENE-8692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784438#comment-16784438
]
Simon Willnauer commented on LUCENE-8692:
-
{noformat}
I think there is an issue with the patch
[
https://issues.apache.org/jira/browse/LUCENE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16773011#comment-16773011
]
Simon Willnauer commented on LUCENE-3041:
-
[~romseygeek] any chance you can open a PR
[
https://issues.apache.org/jira/browse/LUCENE-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16771013#comment-16771013
]
Simon Willnauer commented on LUCENE-8292:
-
[~dsmiley] I coordinated this with [~romseygeek
I spoke to Alan about this before pushing and we have an unresolved solr
blocker too
> On 15. Feb 2019, at 22:56, David Smiley (JIRA) wrote:
>
>
>[
>
[
https://issues.apache.org/jira/browse/LUCENE-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-8292.
-
Resolution: Fixed
Fix Version/s: master (9.0)
8.x
[
https://issues.apache.org/jira/browse/LUCENE-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769324#comment-16769324
]
Simon Willnauer commented on LUCENE-8292:
-
I opened a PR here https://github.com/apache/lucene
[
https://issues.apache.org/jira/browse/LUCENE-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16767061#comment-16767061
]
Simon Willnauer commented on LUCENE-8292:
-
I do see both points here. [~dsmiley] I hate how
[
https://issues.apache.org/jira/browse/LUCENE-8662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763762#comment-16763762
]
Simon Willnauer commented on LUCENE-8662:
-
[~tomasflobbe] yes I think this should go into 8.0
[
https://issues.apache.org/jira/browse/LUCENE-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-8664.
-
Resolution: Fixed
Fix Version/s: master (9.0)
8.0
>
[
https://issues.apache.org/jira/browse/LUCENE-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16756032#comment-16756032
]
Simon Willnauer commented on LUCENE-8664:
-
pushed - thanks [~lucacavanna]
> Add equals/hashc
s
>> - I'd like to make sure that we would not consider this a bug.
>>
>> Erick, I don't think this feature would be suitable for "robust index
>> upgrades". To me it is really a best effort and shouldn't be trusted
>> too much.
>>
>> I think some
[
https://issues.apache.org/jira/browse/LUCENE-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754987#comment-16754987
]
Simon Willnauer commented on LUCENE-8664:
-
[~lucacavanna] what's the usecase for this? Why
[
https://issues.apache.org/jira/browse/LUCENE-8662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754984#comment-16754984
]
Simon Willnauer commented on LUCENE-8662:
-
{noformat}
If we think that it's a trap, we should
Hey folks,
tl;dr; I want to be able to open an indexreader on an old index if the
SegmentInfo version is supported and all segment codecs are available.
Today that's not possible even if I port old formats to current
versions.
Our BWC policy for quite a while has been N-1 major versions. That's
[
https://issues.apache.org/jira/browse/LUCENE-8639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-8639.
-
Resolution: Fixed
Fix Version/s: master (9.0)
7.7
[
https://issues.apache.org/jira/browse/LUCENE-8639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743155#comment-16743155
]
Simon Willnauer commented on LUCENE-8639:
-
[~mikemccand] can you take a look at the PR?
> Se
Simon Willnauer created LUCENE-8639:
---
Summary: SeqNo accounting in IW is broken if many threads start
indexing while we flush.
Key: LUCENE-8639
URL: https://issues.apache.org/jira/browse/LUCENE-8639
[
https://issues.apache.org/jira/browse/LUCENE-8525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740186#comment-16740186
]
Simon Willnauer commented on LUCENE-8525:
-
I do agree with [~rcmuir] here. There is not much
[
https://issues.apache.org/jira/browse/LUCENE-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16722290#comment-16722290
]
Simon Willnauer commented on LUCENE-8609:
-
[~sokolov] I opened [https://github.com/mikemccand
getting consistent docstats from IndexWriter
>> --
>>
>>Key: LUCENE-8609
>>URL: https://issues.apache.org/jira/browse/LUCENE-8609
>>Project: Lucene - Core
>> Issue Type: Improvement
>> Affects Versions: master (8.0), 7.
[
https://issues.apache.org/jira/browse/LUCENE-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-8609.
-
Resolution: Fixed
Fix Version/s: 7.7
master (8.0)
thanks
1 - 100 of 4317 matches
Mail list logo
