Re: 8.6 release

[Joel Bernstein]

Hi Bruno,

Andrzej and I decided that SOLR-14537 is headed to master to bake for a
while and won't make it into the 8.6 release. So please feel free to cut
the branch when ready.


Joel Bernstein
http://joelsolr.blogspot.com/


On Mon, Jun 29, 2020 at 6:13 AM Andrzej Białecki  wrote:

> I wold like to include SOLR-14537 in 8.6 (it’s already tagged), the patch
> is ready and I’m just waiting for Joel to finish performance testing.
>
> On 27 Jun 2020, at 04:59, Tomás Fernández Löbbe 
> wrote:
>
> 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: Announcing Apachecon @Home 2020

[Atri Sharma]

This seems like a great opportunity -- I am planning to give a talk on
basics of Lucene and Solr.

Do we want our own track as well?

On Mon, Jun 29, 2020 at 6:30 PM Rich Bowen  wrote:
>
> Dear PMCs,
>
> We’re pleased to announce that ApacheCon 2020 will be held online,
> September 29th through October 1st, 2020. You can see the full details
> in the various other announcements that have been going out to other
> lists you’re on, so I won’t repeat all of that again here.
>
> My message for you is that, due to the online nature of the event, we’re
> freed of the normal space/time constraints that we have to deal with at
> in-person events. We can have pretty much as much content as we want, on
> as many topics as we want.
>
> If your project (or family of projects) wants to have a presence at
> ApacheCon, from one “what is it?” talk all the way up to a full track of
> content, please get in touch with me - rbo...@apache.org - as soon as
> possible to arrange that.
>
> We are on a very short timeline, due to a long list of blockers that we
> have had to deal with over the past few months, and so please don’t
> delay. I will need for you to designate a track chair who will be my
> single point of contact for your track. You can handle communication
> with your project however you like, but I need one person that I can
> rely on to be that point of contact. That track chair should subscribe
> to plann...@apachecon.com in order to be included in all relevant
> conversations
>
> I hope to have helpful documentation for track chairs, so you won’t be
> doing it all on your own.
>
> I really hope to see your project at ApacheCon @Home 2020.
>
> Rich Bowen
> VP Conferences, The Apache Software Foundation

-- 
Regards,

Atri
Apache Concerted

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

Re: PGP key to sign the 8.6 branch

[David Smiley]

I've been trying to get Bruno's key and have had great difficulty.
I can find his key with the web interface:
https://pgp.mit.edu/pks/lookup?search=broustant%40apache.org=vindex

But at the CLI I can't find it:

This fails:

gpg --keyserver pgp.mit.edu --search-keys broust...@apache.org

gpg: searching for "broust...@apache.org" from hkp server pgp.mit.edu

gpg: key "broust...@apache.org" not found on keyserver

And so does:

gpg --keyserver pgp.mit.edu -v --recv-keys 0x377C3BA26AD29C0A

gpg: requesting key 6AD29C0A from hkp server pgp.mit.edu

gpg: keyserver timed out

gpg: keyserver receive failed: Keyserver error

~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley


On Mon, Jun 29, 2020 at 10:33 AM Robert Muir  wrote:

> I have had problems with gpg last few hours too. pgp.mit.edu has been
> slow/not working even for my own key.
> But if i use an alternative server it works better.
>
> May not help you, as your key (6AD29C0A?) doesn't seem to exist on any of
> the other servers yet.
>
> $ gpg --verbose --keyserver pgp.mit.edu --recv-keys 322D7ECA
> gpg: keyserver receive failed: No keyserver available
> $ gpg --verbose --keyserver keyserver.ubuntu.com --recv-keys 322D7ECA
> gpg: data source: http://162.213.33.9:11371
> gpg: key 817AE1DD322D7ECA: number of dropped non-self-signatures: 6
> gpg: pub  rsa4096/817AE1DD322D7ECA 2009-11-05  Robert Muir (Code Signing
> Key) 
> gpg: key 817AE1DD322D7ECA: "Robert Muir (Code Signing Key) <
> rm...@apache.org>" not changed
> gpg: Total number processed: 1
> gpg:  unchanged: 1
>
> On Mon, Jun 29, 2020 at 10:09 AM Bruno Roustant 
> wrote:
>
>> 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 be signed by
>> another committer. I asked David Smiley but it seems he encounters
>> difficulties to get back my key from the server.
>> Could someone help us to understand the issue?
>>
>> Thanks!
>>
>> Bruno
>>
>

Re: PGP key to sign the 8.6 branch

[Robert Muir]

I have had problems with gpg last few hours too. pgp.mit.edu has been
slow/not working even for my own key.
But if i use an alternative server it works better.

May not help you, as your key (6AD29C0A?) doesn't seem to exist on any of
the other servers yet.

$ gpg --verbose --keyserver pgp.mit.edu --recv-keys 322D7ECA
gpg: keyserver receive failed: No keyserver available
$ gpg --verbose --keyserver keyserver.ubuntu.com --recv-keys 322D7ECA
gpg: data source: http://162.213.33.9:11371
gpg: key 817AE1DD322D7ECA: number of dropped non-self-signatures: 6
gpg: pub  rsa4096/817AE1DD322D7ECA 2009-11-05  Robert Muir (Code Signing
Key) 
gpg: key 817AE1DD322D7ECA: "Robert Muir (Code Signing Key) "
not changed
gpg: Total number processed: 1
gpg:  unchanged: 1

On Mon, Jun 29, 2020 at 10:09 AM Bruno Roustant 
wrote:

> 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 be signed by
> another committer. I asked David Smiley but it seems he encounters
> difficulties to get back my key from the server.
> Could someone help us to understand the issue?
>
> Thanks!
>
> Bruno
>

PGP key to sign the 8.6 branch

[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 be signed by another
committer. I asked David Smiley but it seems he encounters difficulties to
get back my key from the server.
Could someone help us to understand the issue?

Thanks!

Bruno

Announcing ApacheCon @Home 2020

[Rich Bowen]

Hi, Apache enthusiast!

(You’re receiving this because you’re subscribed to one or more dev or 
user mailing lists for an Apache Software Foundation project.)


The ApacheCon Planners and the Apache Software Foundation are pleased to 
announce that ApacheCon @Home will be held online, September 29th 
through October 1st, 2020. We’ll be featuring content from dozens of our 
projects, as well as content about community, how Apache works, business 
models around Apache software, the legal aspects of open source, and 
many other topics.


Full details about the event, and registration, is available at 
https://apachecon.com/acah2020


Due to the confusion around how and where this event was going to be 
held, and in order to open up to presenters from around the world who 
may previously have been unable or unwilling to travel, we’ve reopened 
the Call For Presentations until July 13th. Submit your talks today at 
https://acna2020.jamhosted.net/


We hope to see you at the event!
Rich Bowen, VP Conferences, The Apache Software Foundation

Announcing ApacheCon @Home 2020

[Rich Bowen]

Hi, Apache enthusiast!

(You’re receiving this because you’re subscribed to one or more dev or 
user mailing lists for an Apache Software Foundation project.)


The ApacheCon Planners and the Apache Software Foundation are pleased to 
announce that ApacheCon @Home will be held online, September 29th 
through October 1st, 2020. We’ll be featuring content from dozens of our 
projects, as well as content about community, how Apache works, business 
models around Apache software, the legal aspects of open source, and 
many other topics.


Full details about the event, and registration, is available at 
https://apachecon.com/acah2020


Due to the confusion around how and where this event was going to be 
held, and in order to open up to presenters from around the world who 
may previously have been unable or unwilling to travel, we’ve reopened 
the Call For Presentations until July 13th. Submit your talks today at 
https://acna2020.jamhosted.net/


We hope to see you at the event!
Rich Bowen, VP Conferences, The Apache Software Foundation

Announcing ApacheCon @Home 2020

[Rich Bowen]

Hi, Apache enthusiast!

(You’re receiving this because you’re subscribed to one or more dev or 
user mailing lists for an Apache Software Foundation project.)


The ApacheCon Planners and the Apache Software Foundation are pleased to 
announce that ApacheCon @Home will be held online, September 29th 
through October 1st, 2020. We’ll be featuring content from dozens of our 
projects, as well as content about community, how Apache works, business 
models around Apache software, the legal aspects of open source, and 
many other topics.


Full details about the event, and registration, is available at 
https://apachecon.com/acah2020


Due to the confusion around how and where this event was going to be 
held, and in order to open up to presenters from around the world who 
may previously have been unable or unwilling to travel, we’ve reopened 
the Call For Presentations until July 13th. Submit your talks today at 
https://acna2020.jamhosted.net/


We hope to see you at the event!
Rich Bowen, VP Conferences, The Apache Software Foundation

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

BadApple report

[Erick Erickson]

Holding fairly steady.

Raw fail count by week totals, most recent week first (corresponds to bits):
Week: 0  had  26 failures
Week: 1  had  26 failures
Week: 2  had  34 failures
Week: 3  had  128 failures

This week’s report includes the SuppressWarnings summary. This is really the 
baseline, I added a few more that are counted in this as part of getting clean 
compiles, included here so people can see what they look like.

Only one test has failed every week over the last 4:
Failures in the last 4 reports..
   Report   Pct runsfails   test
 0123   4.7  639 17  RollingRestartTest.test


Full report attached:

DO NOT ENABLE LIST:
MoveReplicaHDFSTest.testFailedMove
MoveReplicaHDFSTest.testNormalFailedMove
TestControlledRealTimeReopenThread.testCRTReopen
TestICUNormalizer2CharFilter.testRandomStrings
TestICUTokenizerCJK
TestImpersonationWithHadoopAuth.testForwarding
TestLTRReRankingPipeline.testDifferentTopN
TestRandomChains


DO NOT ANNOTATE LIST
CdcrBidirectionalTest.testBiDir
IndexSizeTriggerTest.testMergeIntegration
IndexSizeTriggerTest.testMixedBounds
IndexSizeTriggerTest.testSplitIntegration
IndexSizeTriggerTest.testTrigger
InfixSuggestersTest.testShutdownDuringBuild
ShardSplitTest.test
ShardSplitTest.testSplitMixedReplicaTypes
ShardSplitTest.testSplitWithChaosMonkey
Test2BPostings.test
TestLatLonShapeQueries.testRandomBig
TestPackedInts.testPackedLongValues
TestRandomChains.testRandomChainsWithLargeStrings
TestTriggerIntegration.testSearchRate

SuppressWarnings count: last week: 5,377, this week: 5,373, delta -4


*** Files with increased @SuppressWarnings annotations:

Suppress count increase in: 
solr/contrib/dataimporthandler/src/test/org/apache/solr/handler/dataimport/TestZKPropertiesWriter.java.
 Was: 2, now: 5
Suppress count increase in: 
solr/core/src/java/org/apache/solr/api/CustomContainerPlugins.java. Was: null, 
now: 4
Suppress count increase in: 
solr/core/src/java/org/apache/solr/handler/ReplicationHandler.java. Was: 13, 
now: 14
Suppress count increase in: 
solr/core/src/java/org/apache/solr/handler/admin/ContainerPluginsApi.java. Was: 
null, now: 3
Suppress count increase in: 
solr/core/src/java/org/apache/solr/search/JoinQParserPlugin.java. Was: 0, now: 2
Suppress count increase in: 
solr/core/src/java/org/apache/solr/search/join/CrossCollectionJoinQParser.java. 
Was: null, now: 1
Suppress count increase in: 
solr/core/src/test/org/apache/solr/handler/TestContainerPlugin.java. Was: null, 
now: 2
Suppress count increase in: 
solr/solrj/src/test/org/apache/solr/client/solrj/cloud/autoscaling/TestPolicy.java.
 Was: 109, now: 115
Suppress count increase in: 
solr/solrj/src/test/org/apache/solr/client/solrj/cloud/autoscaling/TestPolicy2.java.
 Was: 22, now: 23

*** Files with decreased @SuppressWarnings annotations:

Suppress count decrease in: 
solr/solrj/src/java/org/apache/solr/client/solrj/cloud/autoscaling/AutoScalingConfig.java.
 Was: 10, now: 6
Suppress count decrease in: 
solr/solrj/src/java/org/apache/solr/client/solrj/cloud/autoscaling/Policy.java. 
Was: 8, now: 7
Suppress count decrease in: 
solr/solrj/src/java/org/apache/solr/client/solrj/cloud/autoscaling/Preference.java.
 Was: 4, now: 3
Suppress count decrease in: 
solr/solrj/src/java/org/apache/solr/client/solrj/cloud/autoscaling/ReplicaCount.java.
 Was: 1, now: 0
Suppress count decrease in: 
solr/solrj/src/java/org/apache/solr/client/solrj/cloud/autoscaling/ReplicaInfo.java.
 Was: 3, now: 2
Suppress count decrease in: 
solr/solrj/src/java/org/apache/solr/client/solrj/cloud/autoscaling/VersionedData.java.
 Was: 1, now: 0
Suppress count decrease in: 
solr/solrj/src/java/org/apache/solr/client/solrj/io/stream/CloudSolrStream.java.
 Was: 3, now: 2
Suppress count decrease in: 
solr/solrj/src/java/org/apache/solr/client/solrj/io/stream/DeepRandomStream.java.
 Was: 1, now: 0
Suppress count decrease in: 
solr/solrj/src/java/org/apache/solr/client/solrj/io/stream/expr/StreamExpression.java.
 Was: 1, now: 0
Suppress count decrease in: 
solr/solrj/src/java/org/apache/solr/client/solrj/io/stream/expr/StreamExpressionNamedParameter.java.
 Was: 1, now: 0
Suppress count decrease in: 
solr/solrj/src/java/org/apache/solr/client/solrj/io/stream/expr/StreamExpressionValue.java.
 Was: 1, now: 0
Suppress count decrease in: 
solr/solrj/src/java/org/apache/solr/common/cloud/DocCollection.java. Was: 1, 
now: 0
Suppress count decrease in: 
solr/solrj/src/java/org/apache/solr/common/cloud/Replica.java. Was: 1, now: 0
Suppress count decrease in: 
solr/solrj/src/java/org/apache/solr/common/cloud/ZkNodeProps.java. Was: 2, now: 
1
Suppress count decrease in: 
solr/solrj/src/java/org/apache/solr/common/util/JsonSchemaValidator.java. Was: 
21, now: 15
Suppress count decrease in: 
solr/solrj/src/java/org/apache/solr/common/util/ValidatingJsonMap.java. Was: 
12, now: 11

Re: 8.6 release

[Andrzej Białecki]

I wold like to include SOLR-14537 in 8.6 (it’s already tagged), the patch is 
ready and I’m just waiting for Joel to finish performance testing.

> On 27 Jun 2020, at 04:59, Tomás Fernández Löbbe  wrote:
> 
> 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 
>>> 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 
 

Re: apache solr 8.5.2 Deployment in kubernetes using Helm

[Atri Sharma]

Please do not cross post across mailing lists.

On Mon, Jun 29, 2020 at 1:53 PM Kranthi Randev  wrote:

> Hi all,
> I'm looking for the Apache Solr deployment in kubernetes with Basic
> Authentication and Authorization,
>
> We are able to get Basic authentication but Authorization is Disabled and
> there is not straightforward procedure documentation for that,
>
> Please help me and provide the solution for the above issue.
>
> thanks and regards
> kranthi Ranadev
> [image: image.png]
>
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
> This message contains confidential information and is intended only for the
> individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail. Please notify the sender
> immediately by e-mail if you have received this e-mail by mistake and
> delete this e-mail from your system. If you are not the intended recipient
> you are notified that disclosing, copying, distributing or taking any
> action in reliance on the contents of this information is strictly
> prohibited. WARNING!! : Computer viruses can be transmitted via email. The
> recipient should check this email and any attachments for the presence of
> viruses. The company accepts no liability for any damage caused by any
> virus transmitted by this email. E-mail transmission cannot be guaranteed
> to be secure or error-free as information could be intercepted, corrupted,
> lost, destroyed, arrive late or incomplete, or contain viruses. The sender
> therefore does not accept liability for any errors or omissions in the
> contents of this message, which arise as a result of e-mail transmission.
> Warning!!: Although the company has taken reasonable precautions to ensure
> no viruses are present in this email, the company cannot accept
> responsibility for any loss or damage arising from the use of this email or
> attachments. Negligent misstatement: Our company accepts no liability for
> the content of this email, or for the consequences of any actions taken on
> the basis of the information provided, unless that information is
> subsequently confirmed in writing. If you are not the intended recipient
> you are notified that disclosing, copying, distributing or taking any
> action in reliance on the contents of this information is strictly
> prohibited.



-- 
Regards,

Atri
Apache Concerted

apache solr 8.5.2 Deployment in kubernetes using Helm

[Kranthi Randev]

Hi all,
I'm looking for the Apache Solr deployment in kubernetes with Basic
Authentication and Authorization,

We are able to get Basic authentication but Authorization is Disabled and
there is not straightforward procedure documentation for that,

Please help me and provide the solution for the above issue.

thanks and regards
kranthi Ranadev
[image: image.png]

-- 
This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
If you have received this email in error please notify the system manager. 
This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and 
delete this e-mail from your system. If you are not the intended recipient 
you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly 
prohibited. WARNING!! : Computer viruses can be transmitted via email. The 
recipient should check this email and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused by any 
virus transmitted by this email. E-mail transmission cannot be guaranteed 
to be secure or error-free as information could be intercepted, corrupted, 
lost, destroyed, arrive late or incomplete, or contain viruses. The sender 
therefore does not accept liability for any errors or omissions in the 
contents of this message, which arise as a result of e-mail transmission. 
Warning!!: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email, the company cannot accept 
responsibility for any loss or damage arising from the use of this email or 
attachments. Negligent misstatement: Our company accepts no liability for 
the content of this email, or for the consequences of any actions taken on 
the basis of the information provided, unless that information is 
subsequently confirmed in writing. If you are not the intended recipient 
you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly 
prohibited.

Re: Dependency hell again

[Dawid Weiss]

The problem with Solr dependencies is that they reflect ant state of
things (they are not transitive). So normally you'd just import
Zoookeeper and let it take care of upgrades to libraries it depends
on. This wouldn't be needed:

implementation ('org.xerial.snappy:snappy-java') { transitive = false
} // required for instantiating a Zookeeper server in tests

> Let me see if I'm on the right track. I'm working on upgrading Zookeeper to 
> 3.6.1 and I'm caught in dependency hell again. That version of ZK relies on 
> org.xerial.snappy:snappy-java=1.1.7.6, which is distributed with it.
>
> The problem is that we instantiate a ZookeeperServer in 
> solr/test-framework/src/java/org/apache/solr/cloud/ZkTestServer.java and it 
> blows up with NoClassDef Snappy(OutputStream | InputStream).
>
> I included the snappy jar in versions.props and did all the magic about 
> adding license and notice files etc. All ASL licensed so that's OK.

I'd need to see what you did. Is there an issue and a patch with this?

> Then adding the following line to solr/test-framework/build.gradle fixed 
> running the tests:
>
> implementation ('org.xerial.snappy:snappy-java') { transitive = false } // 
> required for instantiating a Zookeeper server in tests
>
> It doesn't seem to matter whether I put the above in the build.gradle files 
> in solr or solrj or test-framework, but since the file that blows up is in 
> test-framework that seems right?

I don't know. I'd have to see the code and analyze it.

> I still have to test whether we need something similar for running embedded 
> ZK, but before I go there I thought I'd ask if there's anything obviously 
> amiss with what I've done so far. Besides, it's late at night again… If it 
> needs to be include other places, is it right to include it in multiple 
> places? I’d guess that solr/core/build.gradle would be the other candidate 
> but have to test it out.

The best way to resolve such questions would be to work on making Solr
dependencies transitive - this would limit their number (number of
"this depends on ..." clauses, not JARs) and add clarity on what
depends on what [1]

D.

[1] https://issues.apache.org/jira/browse/LUCENE-9140

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