Re: 8.6 release

[Tomás Fernández Löbbe]

I tagged SOLR-14590 for 8.6, The PR is ready for review and I plan to merge
it soon

On Fri, Jun 26, 2020 at 12:54 PM Andrzej Białecki  wrote:

> Jan,
>
> I just removed SOLR-14182 from 8.6, this needs proper back-compat shims
> and testing, and I don’t have enough time to get it done properly for 8.6.
>
> On 26 Jun 2020, at 13:37, Jan Høydahl  wrote:
>
> Unresolved Solr issues tagged with 8.6:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SOLR%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%208.6
> 
>
>
> SOLR-14593   Package store API to disable file upload over HTTP
>Blocker
> SOLR-14580   CloudSolrClient cannot be initialized using 'zkHosts' builder
>   Blocker
> SOLR-14516   NPE during Realtime GET
>   Major
> SOLR-14502   increase bin/solr's post kill sleep
>   Minor
> SOLR-14398   package store PUT should be idempotent
>Trivial
> SOLR-14311   Shared schema should not have access to core level classes
>Major
> SOLR-14182   Move metric reporters config from solr.xml to ZK cluster
> properties Major
> SOLR-14066   Deprecate DIH
>   Blocker
> SOLR-14022   Deprecate CDCR from Solr in 8.x
>   Blocker
>
> Plus two private JIRA issues.
>
> Jan
>
> 26. jun. 2020 kl. 12:06 skrev Bruno Roustant :
>
> So the plan is to cut the release branch on next Tuesday June 30th. If you
> anticipate a problem with the date, please reply.
>
> Is there any JIRA issue that must be committed before the release is made
> and that has not already the appropriate "Fix Version"?
>
> Currently there 3 unresolved issues flagged as Fix Version = 8.6:
> Add tests for corruptions caused by byte flips LUCENE-9356
> 
> Fix linefiledocs compression or replace in tests LUCENE-9191
> 
> Can we merge small segments during refresh, for faster searching?
> LUCENE-8962 
>
>
> Le mer. 24 juin 2020 à 21:05, David Smiley  a
> écrit :
>
>> Thanks starting this discussion, Cassandra.
>>
>> I reviewed the issues I was involved with and I don't quite see something
>> worth noting.
>>
>> I plan to add a note about a change in defaults within UnifiedHighlighter
>> that could be a significant perf regression.  This wasn't introduced in 8.6
>> but introduced in 8.5 and it's significant enough to bring attention to.  I
>> could add it in 8.5's section but then add a short pointer to it in 8.6.
>>
>> ~ David
>>
>>
>> On Wed, Jun 24, 2020 at 2:52 PM Cassandra Targett 
>> wrote:
>>
>>> I started looking at the Ref Guide for 8.6 to get it ready, and notice
>>> there are no Upgrade Notes in `solr-upgrade-notes.adoc` for 8.6. Is it
>>> really true that none are needed at all?
>>>
>>> I’ll add what I usually do about new features/changes that maybe
>>> wouldn’t normally make the old Upgrade Notes section, I just find it
>>> surprising that there weren’t any devs who thought any of the 100 or so
>>> Solr changes warrant any user caveats.
>>> 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 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 <
 bruno.roust...@gmail.com> wrote:

> 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 release manager so I'll probably need
> some guidance. Currently I have two resource links on this subject:
> https://cwiki.apache.org/confluence/display/LUCENE/ReleaseTodo
>
> https://github.com/apache/lucene-solr/tree/master/dev-tools/scripts#releasewizardpy
> If you have more, please share with me.
>
> Bruno
>

>
>

Re: Wiki access to post SIP

[Gus Heck]

I tried to help Mike (user: nibeck) by creating the page for him but it
seems he also doesn't have edit perms.

On Fri, Jun 26, 2020 at 3:52 PM Nibeck, Mike  wrote:

> I need permission to post a proposal to the SIP pages. I don’t not current
> have access to add the sub-page to document the proposal.
>
>
>
> Mike Nibeck
>
> Software Engineering Manager
>
> OCIO – IT Design and Development
>
> Library of Congress
>
>
>


-- 
http://www.needhamsoftware.com (work)
http://www.the111shift.com (play)

Re: 8.6 release

[Andrzej Białecki]

Jan,

I just removed SOLR-14182 from 8.6, this needs proper back-compat shims and 
testing, and I don’t have enough time to get it done properly for 8.6.

> On 26 Jun 2020, at 13:37, Jan Høydahl  wrote:
> 
> Unresolved Solr issues tagged with 8.6:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SOLR%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%208.6
>  
> 
>  
> 
> SOLR-14593   Package store API to disable file upload over HTTP   
>Blocker 
> SOLR-14580   CloudSolrClient cannot be initialized using 'zkHosts' builder
>Blocker 
> SOLR-14516   NPE during Realtime GET  
>Major   
> SOLR-14502   increase bin/solr's post kill sleep  
>Minor   
> SOLR-14398   package store PUT should be idempotent   
>Trivial 
> SOLR-14311   Shared schema should not have access to core level classes   
>Major   
> SOLR-14182   Move metric reporters config from solr.xml to ZK cluster 
> properties Major   
> SOLR-14066   Deprecate DIH
>Blocker 
> SOLR-14022   Deprecate CDCR from Solr in 8.x  
>Blocker 
> 
> Plus two private JIRA issues.
> 
> Jan
> 
>> 26. jun. 2020 kl. 12:06 skrev Bruno Roustant > >:
>> 
>> So the plan is to cut the release branch on next Tuesday June 30th. If you 
>> anticipate a problem with the date, please reply.
>> 
>> Is there any JIRA issue that must be committed before the release is made 
>> and that has not already the appropriate "Fix Version"?
>> 
>> Currently there 3 unresolved issues flagged as Fix Version = 8.6:
>> Add tests for corruptions caused by byte flips LUCENE-9356 
>> 
>> Fix linefiledocs compression or replace in tests LUCENE-9191
>>  Can we merge small 
>> segments during refresh, for faster searching? LUCENE-8962 
>> 
>> 
>> 
>> Le mer. 24 juin 2020 à 21:05, David Smiley > > a écrit :
>> Thanks starting this discussion, Cassandra.
>> 
>> I reviewed the issues I was involved with and I don't quite see something 
>> worth noting.
>> 
>> I plan to add a note about a change in defaults within UnifiedHighlighter 
>> that could be a significant perf regression.  This wasn't introduced in 8.6 
>> but introduced in 8.5 and it's significant enough to bring attention to.  I 
>> could add it in 8.5's section but then add a short pointer to it in 8.6.
>> 
>> ~ David
>> 
>> 
>> On Wed, Jun 24, 2020 at 2:52 PM Cassandra Targett > > wrote:
>> I started looking at the Ref Guide for 8.6 to get it ready, and notice there 
>> are no Upgrade Notes in `solr-upgrade-notes.adoc` for 8.6. Is it really true 
>> that none are needed at all?
>> 
>> I’ll add what I usually do about new features/changes that maybe wouldn’t 
>> normally make the old Upgrade Notes section, I just find it surprising that 
>> there weren’t any devs who thought any of the 100 or so Solr changes warrant 
>> any user caveats.
>> On Jun 17, 2020, 12:27 PM -0500, Tomás Fernández Löbbe 
>> mailto: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 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 >> > wrote:
>>> 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 release manager so I'll probably need some 
>>> guidance. Currently I have two resource links on this subject:
>>> https://cwiki.apache.org/confluence/display/LUCENE/ReleaseTodo 
>>> 
>>> https://github.com/apache/lucene-solr/tree/master/dev-tools/scripts#releasewizardpy
>>>  
>>> 
>>> If you have more, please share with me.
>>> 
>>> Bruno
> 

Wiki access to post SIP

[Nibeck, Mike]

I need permission to post a proposal to the SIP pages. I don't not current have 
access to add the sub-page to document the proposal.

Mike Nibeck
Software Engineering Manager
OCIO - IT Design and Development
Library of Congress

Re: Should Solr expose OS specific file paths?

[Ilan Ginzburg]

I believe output from Solr (logs or returned strings representing paths)
should conform to the host platform convention.
Solr should accept either convention as input regardless of the platform
it's running on.

Ilan

On Fri, Jun 26, 2020 at 6:11 PM David Smiley  wrote:

> I started a conversation in Slack with Jason but think Slack is too narrow
> of an audience so I'm going to copy-paste it here.  We want your opinions!
> Here's a copy of it; I hope this doesn't look terrible on the mailing list.
>
> David Smiley  Today at 11:49 AM
> 
> I'd like to debate a point relating to Solr's APIs and file paths it might
> expose, as it relates to the operating system Solr runs on.
> 6 replies
> --
> David Smiley   20 minutes ago
> 
> Apparently there is a streaming expression that can expose file paths
> rooted at a "/userfiles" dir on Solr
> David Smiley   17 minutes ago
> 
> I have a strong opinion that any service exposing (returns) file paths to
> other machines should do so in a way that is operating-system neutral.
> David Smiley   14 minutes ago
> 
> Thus if you're going to list the contents of a directory tree of all files
> at once, then you do it like "foo/bar/baz.txt" always, even if the server
> happens to be running on Windows
> David Smiley   13 minutes ago
> 
> The client parsing this should not have to know what OS the server is
> running in order to parse it.  It should just assume '/' separator.
> gerlowskija   13 minutes ago
> 
> Whereas in discussing this with David - I have the opposite opinion.  I
> think we should take-in/return paths in an OS-specific way.Because that’s
> what existing APIs expect currently (CoreAdmin, etc.), and because I
> imagine an admin setting up their cluster on Windows, well, expects to use
> Windows filepaths.
>

Should Solr expose OS specific file paths?

[David Smiley]

I started a conversation in Slack with Jason but think Slack is too narrow
of an audience so I'm going to copy-paste it here.  We want your opinions!
Here's a copy of it; I hope this doesn't look terrible on the mailing list.

David Smiley  Today at 11:49 AM

I'd like to debate a point relating to Solr's APIs and file paths it might
expose, as it relates to the operating system Solr runs on.
6 replies
--
David Smiley   20 minutes ago

Apparently there is a streaming expression that can expose file paths
rooted at a "/userfiles" dir on Solr
David Smiley   17 minutes ago

I have a strong opinion that any service exposing (returns) file paths to
other machines should do so in a way that is operating-system neutral.
David Smiley   14 minutes ago

Thus if you're going to list the contents of a directory tree of all files
at once, then you do it like "foo/bar/baz.txt" always, even if the server
happens to be running on Windows
David Smiley   13 minutes ago

The client parsing this should not have to know what OS the server is
running in order to parse it.  It should just assume '/' separator.
gerlowskija   13 minutes ago

Whereas in discussing this with David - I have the opposite opinion.  I
think we should take-in/return paths in an OS-specific way.Because that’s
what existing APIs expect currently (CoreAdmin, etc.), and because I
imagine an admin setting up their cluster on Windows, well, expects to use
Windows filepaths.

Re: [JENKINS] Lucene-Solr-master-Linux (64bit/jdk-12.0.2) - Build # 27137 - Unstable!

[Erick Erickson]

The method that throws the exception has, guess what? A “SuppressWarnings” 
for unchecked.

> On Jun 26, 2020, at 11:13 AM, Policeman Jenkins Server  
> wrote:
> 
> Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/27137/
> Java: 64bit/jdk-12.0.2 -XX:+UseCompressedOops -XX:+UseParallelGC
> 
> 1 tests failed.
> FAILED:  
> org.apache.solr.client.solrj.io.stream.StreamDecoratorTest.testParallelTerminatingDaemonUpdateStream
> 
> Error Message:
> --> http://127.0.0.1:34941/solr/collection1: An exception has occurred on the 
> server, refer to server log for details.
> 
> Stack Trace:
> java.io.IOException: --> http://127.0.0.1:34941/solr/collection1: An 
> exception has occurred on the server, refer to server log for details.
>   at 
> __randomizedtesting.SeedInfo.seed([D0C55D0D61A89513:21A1856535C25A0D]:0)
>   at 
> org.apache.solr.client.solrj.io.stream.SolrStream.read(SolrStream.java:232)
>   at 
> org.apache.solr.client.solrj.io.stream.StreamDecoratorTest.testParallelTerminatingDaemonUpdateStream(StreamDecoratorTest.java:3096)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.base/java.lang.reflect.Method.invoke(Method.java:567)
>   at 
> com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1754)
>   at 
> com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:942)
>   at 
> com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:978)
>   at 
> com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:992)
>   at 
> com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
>   at 
> org.apache.lucene.util.TestRuleSetupTeardownChained$1.evaluate(TestRuleSetupTeardownChained.java:49)
>   at 
> org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:45)
>   at 
> org.apache.lucene.util.TestRuleThreadAndTestName$1.evaluate(TestRuleThreadAndTestName.java:48)
>   at 
> org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:64)
>   at 
> org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:47)
>   at 
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
>   at 
> com.carrotsearch.randomizedtesting.ThreadLeakControl$StatementRunner.run(ThreadLeakControl.java:370)
>   at 
> com.carrotsearch.randomizedtesting.ThreadLeakControl.forkTimeoutingTask(ThreadLeakControl.java:819)
>   at 
> com.carrotsearch.randomizedtesting.ThreadLeakControl$3.evaluate(ThreadLeakControl.java:470)
>   at 
> com.carrotsearch.randomizedtesting.RandomizedRunner.runSingleTest(RandomizedRunner.java:951)
>   at 
> com.carrotsearch.randomizedtesting.RandomizedRunner$5.evaluate(RandomizedRunner.java:836)
>   at 
> com.carrotsearch.randomizedtesting.RandomizedRunner$6.evaluate(RandomizedRunner.java:887)
>   at 
> com.carrotsearch.randomizedtesting.RandomizedRunner$7.evaluate(RandomizedRunner.java:898)
>   at 
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
>   at 
> com.carrotsearch.randomizedtesting.rules.SystemPropertiesRestoreRule$1.evaluate(SystemPropertiesRestoreRule.java:57)
>   at 
> org.apache.lucene.util.AbstractBeforeAfterRule$1.evaluate(AbstractBeforeAfterRule.java:45)
>   at 
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
>   at 
> org.apache.lucene.util.TestRuleStoreClassName$1.evaluate(TestRuleStoreClassName.java:41)
>   at 
> com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
>   at 
> com.carrotsearch.randomizedtesting.rules.NoShadowingOrOverridesOnMethodsRule$1.evaluate(NoShadowingOrOverridesOnMethodsRule.java:40)
>   at 
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
>   at 
> com.carrotsearch.randomizedtesting.rules.StatementAdapter.evaluate(StatementAdapter.java:36)
>   at 
> org.apache.lucene.util.TestRuleAssertionsRequired$1.evaluate(TestRuleAssertionsRequired.java:53)
>   at 
> org.apache.lucene.util.TestRuleMarkFailure$1.evaluate(TestRuleMarkFailure.java:47)
>   at 
> org.apache.lucene.util.TestRuleIgnoreAfterMaxFailures$1.evaluate(TestRuleIgnoreAfterMaxFailures.java:64)
>   at 
> org.apache.lucene.util.TestRuleIgnoreTestSuites$1.evaluate(TestRuleIgnoreTestSuites.java:54)
>   at 
> 

Re: 8.6 release

[Theyaa Matti]

Thank you!

On Fri, Jun 26, 2020 at 10:01 AM David Smiley 
wrote:

> RE 8.x:  Ant!
> Gradle is master (9.x)
>
> ~ David
>
>
> On Fri, Jun 26, 2020 at 10:00 AM Theyaa Matti 
> wrote:
>
>> Would 8.6 use gradle for build or still use Ant?
>>
>> On Fri, Jun 26, 2020 at 9:35 AM Michael Sokolov 
>> wrote:
>>
>>> I think Simon is working on LUCENE-8962 and seems to be close, but we
>>> have been here before; it's quite possible we need more time to fully
>>> bake this change. I'll let him weigh in on whether he thinks targeting
>>> 8.6 is reasonable, but we might need to slip until 8.7 for that one
>>>
>>> On Fri, Jun 26, 2020 at 6:06 AM Bruno Roustant 
>>> wrote:
>>> >
>>> > So the plan is to cut the release branch on next Tuesday June 30th. If
>>> you anticipate a problem with the date, please reply.
>>> >
>>> > Is there any JIRA issue that must be committed before the release is
>>> made and that has not already the appropriate "Fix Version"?
>>> >
>>> > Currently there 3 unresolved issues flagged as Fix Version = 8.6:
>>> > Add tests for corruptions caused by byte flips LUCENE-9356
>>> > Fix linefiledocs compression or replace in tests LUCENE-9191
>>> > Can we merge small segments during refresh, for faster searching?
>>> LUCENE-8962
>>> >
>>> >
>>> > Le mer. 24 juin 2020 à 21:05, David Smiley 
>>> a écrit :
>>> >>
>>> >> Thanks starting this discussion, Cassandra.
>>> >>
>>> >> I reviewed the issues I was involved with and I don't quite see
>>> something worth noting.
>>> >>
>>> >> I plan to add a note about a change in defaults within
>>> UnifiedHighlighter that could be a significant perf regression.  This
>>> wasn't introduced in 8.6 but introduced in 8.5 and it's significant enough
>>> to bring attention to.  I could add it in 8.5's section but then add a
>>> short pointer to it in 8.6.
>>> >>
>>> >> ~ David
>>> >>
>>> >>
>>> >> On Wed, Jun 24, 2020 at 2:52 PM Cassandra Targett <
>>> casstarg...@gmail.com> wrote:
>>> >>>
>>> >>> I started looking at the Ref Guide for 8.6 to get it ready, and
>>> notice there are no Upgrade Notes in `solr-upgrade-notes.adoc` for 8.6. Is
>>> it really true that none are needed at all?
>>> >>>
>>> >>> I’ll add what I usually do about new features/changes that maybe
>>> wouldn’t normally make the old Upgrade Notes section, I just find it
>>> surprising that there weren’t any devs who thought any of the 100 or so
>>> Solr changes warrant any user caveats.
>>> >>> 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 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 <
>>> bruno.roust...@gmail.com> wrote:
>>> >
>>> > 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 release manager so I'll probably
>>> need some guidance. Currently I have two resource links on this subject:
>>> > https://cwiki.apache.org/confluence/display/LUCENE/ReleaseTodo
>>> >
>>> https://github.com/apache/lucene-solr/tree/master/dev-tools/scripts#releasewizardpy
>>> > If you have more, please share with me.
>>> >
>>> > Bruno
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>>
>>>

Re: 8.6 release

[David Smiley]

RE 8.x:  Ant!
Gradle is master (9.x)

~ David


On Fri, Jun 26, 2020 at 10:00 AM Theyaa Matti  wrote:

> Would 8.6 use gradle for build or still use Ant?
>
> On Fri, Jun 26, 2020 at 9:35 AM Michael Sokolov 
> wrote:
>
>> I think Simon is working on LUCENE-8962 and seems to be close, but we
>> have been here before; it's quite possible we need more time to fully
>> bake this change. I'll let him weigh in on whether he thinks targeting
>> 8.6 is reasonable, but we might need to slip until 8.7 for that one
>>
>> On Fri, Jun 26, 2020 at 6:06 AM Bruno Roustant 
>> wrote:
>> >
>> > So the plan is to cut the release branch on next Tuesday June 30th. If
>> you anticipate a problem with the date, please reply.
>> >
>> > Is there any JIRA issue that must be committed before the release is
>> made and that has not already the appropriate "Fix Version"?
>> >
>> > Currently there 3 unresolved issues flagged as Fix Version = 8.6:
>> > Add tests for corruptions caused by byte flips LUCENE-9356
>> > Fix linefiledocs compression or replace in tests LUCENE-9191
>> > Can we merge small segments during refresh, for faster searching?
>> LUCENE-8962
>> >
>> >
>> > Le mer. 24 juin 2020 à 21:05, David Smiley 
>> a écrit :
>> >>
>> >> Thanks starting this discussion, Cassandra.
>> >>
>> >> I reviewed the issues I was involved with and I don't quite see
>> something worth noting.
>> >>
>> >> I plan to add a note about a change in defaults within
>> UnifiedHighlighter that could be a significant perf regression.  This
>> wasn't introduced in 8.6 but introduced in 8.5 and it's significant enough
>> to bring attention to.  I could add it in 8.5's section but then add a
>> short pointer to it in 8.6.
>> >>
>> >> ~ David
>> >>
>> >>
>> >> On Wed, Jun 24, 2020 at 2:52 PM Cassandra Targett <
>> casstarg...@gmail.com> wrote:
>> >>>
>> >>> I started looking at the Ref Guide for 8.6 to get it ready, and
>> notice there are no Upgrade Notes in `solr-upgrade-notes.adoc` for 8.6. Is
>> it really true that none are needed at all?
>> >>>
>> >>> I’ll add what I usually do about new features/changes that maybe
>> wouldn’t normally make the old Upgrade Notes section, I just find it
>> surprising that there weren’t any devs who thought any of the 100 or so
>> Solr changes warrant any user caveats.
>> >>> 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 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 <
>> bruno.roust...@gmail.com> wrote:
>> >
>> > 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 release manager so I'll probably need
>> some guidance. Currently I have two resource links on this subject:
>> > https://cwiki.apache.org/confluence/display/LUCENE/ReleaseTodo
>> >
>> https://github.com/apache/lucene-solr/tree/master/dev-tools/scripts#releasewizardpy
>> > If you have more, please share with me.
>> >
>> > Bruno
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
>>

Re: 8.6 release

[Theyaa Matti]

Would 8.6 use gradle for build or still use Ant?

On Fri, Jun 26, 2020 at 9:35 AM Michael Sokolov  wrote:

> I think Simon is working on LUCENE-8962 and seems to be close, but we
> have been here before; it's quite possible we need more time to fully
> bake this change. I'll let him weigh in on whether he thinks targeting
> 8.6 is reasonable, but we might need to slip until 8.7 for that one
>
> On Fri, Jun 26, 2020 at 6:06 AM Bruno Roustant 
> wrote:
> >
> > So the plan is to cut the release branch on next Tuesday June 30th. If
> you anticipate a problem with the date, please reply.
> >
> > Is there any JIRA issue that must be committed before the release is
> made and that has not already the appropriate "Fix Version"?
> >
> > Currently there 3 unresolved issues flagged as Fix Version = 8.6:
> > Add tests for corruptions caused by byte flips LUCENE-9356
> > Fix linefiledocs compression or replace in tests LUCENE-9191
> > Can we merge small segments during refresh, for faster searching?
> LUCENE-8962
> >
> >
> > Le mer. 24 juin 2020 à 21:05, David Smiley  a
> écrit :
> >>
> >> Thanks starting this discussion, Cassandra.
> >>
> >> I reviewed the issues I was involved with and I don't quite see
> something worth noting.
> >>
> >> I plan to add a note about a change in defaults within
> UnifiedHighlighter that could be a significant perf regression.  This
> wasn't introduced in 8.6 but introduced in 8.5 and it's significant enough
> to bring attention to.  I could add it in 8.5's section but then add a
> short pointer to it in 8.6.
> >>
> >> ~ David
> >>
> >>
> >> On Wed, Jun 24, 2020 at 2:52 PM Cassandra Targett <
> casstarg...@gmail.com> wrote:
> >>>
> >>> I started looking at the Ref Guide for 8.6 to get it ready, and notice
> there are no Upgrade Notes in `solr-upgrade-notes.adoc` for 8.6. Is it
> really true that none are needed at all?
> >>>
> >>> I’ll add what I usually do about new features/changes that maybe
> wouldn’t normally make the old Upgrade Notes section, I just find it
> surprising that there weren’t any devs who thought any of the 100 or so
> Solr changes warrant any user caveats.
> >>> 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 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 <
> bruno.roust...@gmail.com> wrote:
> >
> > 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 release manager so I'll probably need
> some guidance. Currently I have two resource links on this subject:
> > https://cwiki.apache.org/confluence/display/LUCENE/ReleaseTodo
> >
> https://github.com/apache/lucene-solr/tree/master/dev-tools/scripts#releasewizardpy
> > If you have more, please share with me.
> >
> > Bruno
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>

Re: 8.6 release

[Michael Sokolov]

I think Simon is working on LUCENE-8962 and seems to be close, but we
have been here before; it's quite possible we need more time to fully
bake this change. I'll let him weigh in on whether he thinks targeting
8.6 is reasonable, but we might need to slip until 8.7 for that one

On Fri, Jun 26, 2020 at 6:06 AM Bruno Roustant  wrote:
>
> So the plan is to cut the release branch on next Tuesday June 30th. If you 
> anticipate a problem with the date, please reply.
>
> Is there any JIRA issue that must be committed before the release is made and 
> that has not already the appropriate "Fix Version"?
>
> Currently there 3 unresolved issues flagged as Fix Version = 8.6:
> Add tests for corruptions caused by byte flips LUCENE-9356
> Fix linefiledocs compression or replace in tests LUCENE-9191
> Can we merge small segments during refresh, for faster searching? LUCENE-8962
>
>
> Le mer. 24 juin 2020 à 21:05, David Smiley  a écrit 
> :
>>
>> Thanks starting this discussion, Cassandra.
>>
>> I reviewed the issues I was involved with and I don't quite see something 
>> worth noting.
>>
>> I plan to add a note about a change in defaults within UnifiedHighlighter 
>> that could be a significant perf regression.  This wasn't introduced in 8.6 
>> but introduced in 8.5 and it's significant enough to bring attention to.  I 
>> could add it in 8.5's section but then add a short pointer to it in 8.6.
>>
>> ~ David
>>
>>
>> On Wed, Jun 24, 2020 at 2:52 PM Cassandra Targett  
>> wrote:
>>>
>>> I started looking at the Ref Guide for 8.6 to get it ready, and notice 
>>> there are no Upgrade Notes in `solr-upgrade-notes.adoc` for 8.6. Is it 
>>> really true that none are needed at all?
>>>
>>> I’ll add what I usually do about new features/changes that maybe wouldn’t 
>>> normally make the old Upgrade Notes section, I just find it surprising that 
>>> there weren’t any devs who thought any of the 100 or so Solr changes 
>>> warrant any user caveats.
>>> On Jun 17, 2020, 12:27 PM -0500, Tomás Fernández Löbbe 
>>> , wrote:
>>>
>>> +1. Thanks Bruno
>>>
>>> On Wed, Jun 17, 2020 at 6:22 AM Mike Drob  wrote:

 +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 Bruno Roustant  
 wrote:
>
> 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 release manager so I'll probably need some 
> guidance. Currently I have two resource links on this subject:
> https://cwiki.apache.org/confluence/display/LUCENE/ReleaseTodo
> https://github.com/apache/lucene-solr/tree/master/dev-tools/scripts#releasewizardpy
> If you have more, please share with me.
>
> Bruno

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: StreamExpressionTest failures

[Erick Erickson]

Wonder if Uwe has any insights?

> On Jun 25, 2020, at 9:32 PM, Joel Bernstein  wrote:
> 
> This just started failing out of the blue today. I wonder what changed? Is it 
> straightforward to detect windows in the test cases?
> 
> 
> Joel Bernstein
> http://joelsolr.blogspot.com/
> 
> 
> On Thu, Jun 25, 2020 at 7:46 PM Erick Erickson  
> wrote:
> This test fails on line 3500, here’s the code block. Notice that the test 
> carefully constructs
> the test string with the system file separator. Even so, the the tuple has a 
> *nix style separator
> and the test string a Windows separator.
> 
> 
> final String expectedSecondLevel1Path = "directory1" + File.separator + 
> "secondLevel1.txt";
> for (int i = 0; i < 4; i++) {
>   Tuple t = tuples.get(i);
>   assertEquals("secondLevel1.txt line " + String.valueOf(i+1), t.get("line"));
>   assertEquals(expectedSecondLevel1Path, t.get("file"));
> }
> 
> FAILED:  
> org.apache.solr.client.solrj.io.stream.StreamExpressionTest.testCatStreamDirectoryCrawl
> 
> Error Message:
> expected: but 
> was:
> -
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: 8.6 release

[Jan Høydahl]

Unresolved Solr issues tagged with 8.6:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SOLR%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%208.6
 

 

SOLR-14593   Package store API to disable file upload over HTTP 
 Blocker 
SOLR-14580   CloudSolrClient cannot be initialized using 'zkHosts' builder  
 Blocker 
SOLR-14516   NPE during Realtime GET
 Major   
SOLR-14502   increase bin/solr's post kill sleep
 Minor   
SOLR-14398   package store PUT should be idempotent 
 Trivial 
SOLR-14311   Shared schema should not have access to core level classes 
 Major   
SOLR-14182   Move metric reporters config from solr.xml to ZK cluster 
properties Major   
SOLR-14066   Deprecate DIH  
 Blocker 
SOLR-14022   Deprecate CDCR from Solr in 8.x
 Blocker 

Plus two private JIRA issues.

Jan

> 26. jun. 2020 kl. 12:06 skrev Bruno Roustant :
> 
> So the plan is to cut the release branch on next Tuesday June 30th. If you 
> anticipate a problem with the date, please reply.
> 
> Is there any JIRA issue that must be committed before the release is made and 
> that has not already the appropriate "Fix Version"?
> 
> Currently there 3 unresolved issues flagged as Fix Version = 8.6:
> Add tests for corruptions caused by byte flips LUCENE-9356 
> 
> Fix linefiledocs compression or replace in tests LUCENE-9191
>  Can we merge small 
> segments during refresh, for faster searching? LUCENE-8962 
> 
> 
> 
> Le mer. 24 juin 2020 à 21:05, David Smiley  > a écrit :
> Thanks starting this discussion, Cassandra.
> 
> I reviewed the issues I was involved with and I don't quite see something 
> worth noting.
> 
> I plan to add a note about a change in defaults within UnifiedHighlighter 
> that could be a significant perf regression.  This wasn't introduced in 8.6 
> but introduced in 8.5 and it's significant enough to bring attention to.  I 
> could add it in 8.5's section but then add a short pointer to it in 8.6.
> 
> ~ David
> 
> 
> On Wed, Jun 24, 2020 at 2:52 PM Cassandra Targett  > wrote:
> I started looking at the Ref Guide for 8.6 to get it ready, and notice there 
> are no Upgrade Notes in `solr-upgrade-notes.adoc` for 8.6. Is it really true 
> that none are needed at all?
> 
> I’ll add what I usually do about new features/changes that maybe wouldn’t 
> normally make the old Upgrade Notes section, I just find it surprising that 
> there weren’t any devs who thought any of the 100 or so Solr changes warrant 
> any user caveats.
> On Jun 17, 2020, 12:27 PM -0500, Tomás Fernández Löbbe  >, wrote:
>> +1. Thanks Bruno
>> 
>> On Wed, Jun 17, 2020 at 6:22 AM Mike Drob > > wrote:
>> +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 Bruno Roustant > > wrote:
>> 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 release manager so I'll probably need some 
>> guidance. Currently I have two resource links on this subject:
>> https://cwiki.apache.org/confluence/display/LUCENE/ReleaseTodo 
>> 
>> https://github.com/apache/lucene-solr/tree/master/dev-tools/scripts#releasewizardpy
>>  
>> 
>> If you have more, please share with me.
>> 
>> Bruno

Re: 8.6 release

[Bruno Roustant]

So the plan is to cut the release branch on next Tuesday June 30th. If you
anticipate a problem with the date, please reply.

Is there any JIRA issue that must be committed before the release is made
and that has not already the appropriate "Fix Version"?

Currently there 3 unresolved issues flagged as Fix Version = 8.6:
Add tests for corruptions caused by byte flips LUCENE-9356

Fix linefiledocs compression or replace in tests LUCENE-9191

Can we merge small segments during refresh, for faster searching?
LUCENE-8962 


Le mer. 24 juin 2020 à 21:05, David Smiley  a
écrit :

> Thanks starting this discussion, Cassandra.
>
> I reviewed the issues I was involved with and I don't quite see something
> worth noting.
>
> I plan to add a note about a change in defaults within UnifiedHighlighter
> that could be a significant perf regression.  This wasn't introduced in 8.6
> but introduced in 8.5 and it's significant enough to bring attention to.  I
> could add it in 8.5's section but then add a short pointer to it in 8.6.
>
> ~ David
>
>
> On Wed, Jun 24, 2020 at 2:52 PM Cassandra Targett 
> wrote:
>
>> I started looking at the Ref Guide for 8.6 to get it ready, and notice
>> there are no Upgrade Notes in `solr-upgrade-notes.adoc` for 8.6. Is it
>> really true that none are needed at all?
>>
>> I’ll add what I usually do about new features/changes that maybe wouldn’t
>> normally make the old Upgrade Notes section, I just find it surprising that
>> there weren’t any devs who thought any of the 100 or so Solr changes
>> warrant any user caveats.
>> 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 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 
>>> wrote:
>>>
 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 release manager so I'll probably need
 some guidance. Currently I have two resource links on this subject:
 https://cwiki.apache.org/confluence/display/LUCENE/ReleaseTodo

 https://github.com/apache/lucene-solr/tree/master/dev-tools/scripts#releasewizardpy
 If you have more, please share with me.

 Bruno

>>>

Re: Lucene Highlighting Not Working Properly!!

[Atri Sharma]

You will need to provide more details in order for somebody to help you.

On Fri, Jun 26, 2020 at 10:59 AM Ajaykumar Farakte  wrote:
>
> Hello Team ,
>
> I am using a lucene  highlighter  which is not properly working
> Can you please   help me to sort this issue.
> 
> Thanks & Regards,
> Ajay.
>

-- 
Regards,

Atri
Apache Concerted

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org