Re: [VOTE] Lucene logo contest, third time's a charm

D. Binding. Dawid On Tue, Sep 1, 2020 at 10:21 PM Ryan Ernst wrote: > Dear Lucene and Solr developers! > > Sorry for the multiple threads. This should be the last one. > > In February a contest was started to design a new logo for Lucene > [jira-issue]. The initial attempt [first-vote] to call

master/gradle seems to expand JIRA IDs in documentation filepath references

Hi, I am doing some work in a branch named after JIRA and gradle refuses to build because explands a variable and then seems to expand the SOLR-XYZ in the path with the Jira link: Specifically: *[Lucene Documentation](${project.luceneDocUrl}/index.html) in solr/site.index.template.md (or maybe

Re: [VOTE] Lucene logo contest, third time's a charm

A2, A1

Re: Annoying but harmless exceptions due to filepermissions when running tests

: Hmmm, that’s kind of an dilemma then. Are you saying that : he test can see that the directory appears writable then tries : to write to it then gets tripped up by the framework? : : Seems to me that a test that tries to write, thinks it can and then : can’t should fail anyway. : : Well, I

Re: [VOTE] Lucene logo contest, third time's a charm

A2, A1, D (binding) On Tue, Sep 1, 2020 at 7:37 PM Varun Thacker wrote: > (non-binding) > vote: A1, A2, D > > On Tue, Sep 1, 2020 at 1:21 PM Ryan Ernst wrote: > >> Dear Lucene and Solr developers! >> >> Sorry for the multiple threads. This should be the last one. >> >> In February a contest

Re: Approach towards solving split package issues?

+1 to fixing and +1 to doing it in a major release. On Tue, Sep 1, 2020 at 4:32 PM Adrien Grand wrote: > +1 Changing packages of many classes should be done in a major. > > On Tue, Sep 1, 2020 at 5:50 PM Tomoko Uchida > wrote: > >> Just to make sure, could I confirm "when the changes will be

Re: [VOTE] Lucene logo contest, third time's a charm

(non-binding) vote: A1, A2, D On Tue, Sep 1, 2020 at 1:21 PM Ryan Ernst wrote: > Dear Lucene and Solr developers! > > Sorry for the multiple threads. This should be the last one. > > In February a contest was started to design a new logo for Lucene > [jira-issue]. The initial attempt

Re: [VOTE] Lucene logo contest, third time's a charm

D Regards Ameer On Wed, 2 Sep 2020 at 08:21, Steve Rowe wrote: > D (binding) > > -- > Steve > > > On Sep 1, 2020, at 4:21 PM, Ryan Ernst wrote: > > > > Dear Lucene and Solr developers! > > > > Sorry for the multiple threads. This should be the last one. > > > > In February a contest was

Re: [VOTE] Lucene logo contest, third time's a charm

D (binding) Andi.. > On Sep 1, 2020, at 12:21, Steve Rowe wrote: > > D (binding) > > -- > Steve > >> On Sep 1, 2020, at 4:21 PM, Ryan Ernst wrote: >> >> Dear Lucene and Solr developers! >> >> Sorry for the multiple threads. This should be the last one. >> >> In February a contest was

Re: [VOTE] Lucene logo contest, third time's a charm

D (binding) -- Steve > On Sep 1, 2020, at 4:21 PM, Ryan Ernst wrote: > > Dear Lucene and Solr developers! > > Sorry for the multiple threads. This should be the last one. > > In February a contest was started to design a new logo for Lucene > [jira-issue]. The initial attempt [first-vote]

Re: [VOTE] Lucene logo contest, third time's a charm

A1 :-) On Tue, Sep 1, 2020, 10:21 PM Ryan Ernst wrote: > Dear Lucene and Solr developers! > > Sorry for the multiple threads. This should be the last one. > > In February a contest was started to design a new logo for Lucene > [jira-issue]. The initial attempt [first-vote] to call a vote

Re: [VOTE] Lucene logo contest, third time's a charm

(non-binding) vote: A1, A2, D On Tue, Sep 1, 2020 at 4:31 PM Adrien Grand wrote: > A1, A2, D (binding) > > On Tue, Sep 1, 2020 at 10:21 PM Ryan Ernst wrote: > >> Dear Lucene and Solr developers! >> >> Sorry for the multiple threads. This should be the last one. >> >> In February a contest was

Re: Approach towards solving split package issues?

+1 Changing packages of many classes should be done in a major. On Tue, Sep 1, 2020 at 5:50 PM Tomoko Uchida wrote: > Just to make sure, could I confirm "when the changes will be out"... > Resolving split package issues should break backward compatibility > (changing package names and moving

Re: [VOTE] Lucene logo contest, third time's a charm

A1, A2, D (binding) On Tue, Sep 1, 2020 at 10:21 PM Ryan Ernst wrote: > Dear Lucene and Solr developers! > > Sorry for the multiple threads. This should be the last one. > > In February a contest was started to design a new logo for Lucene > [jira-issue]. The initial attempt [first-vote] to

[VOTE] Lucene logo contest, third time's a charm

Dear Lucene and Solr developers! Sorry for the multiple threads. This should be the last one. In February a contest was started to design a new logo for Lucene [jira-issue]. The initial attempt [first-vote] to call a vote resulted in some confusion on the rules, as well the request for one

Re: [VOTE] Lucene logo contest, here we go again

dev@ got dropped from this, including the note here as well On Tue, Sep 1, 2020 at 12:15 PM Ryan Ernst wrote: > Apologies Baris, I messed up the links because I copied the first of > your links, and then replaced the number, thinking that would work > correctly. But..computers. > > To ensure

Re: SIP-10: Solr 9 examples: Can we use Ref Guide as a dogfood example?

That Jeopardy set reads very dubious. Content that was collected by scraping and available on various sharing sites (including Mega!). I would not feel comfortable working with that in our context. There are other dataset sources. I like the ones that Data is Plural newsletter collects:

Re: SIP-10: Solr 9 examples: Can we use Ref Guide as a dogfood example?

What about 200.000 Jeopardy questions in JSON format? https://www.reddit.com/r/datasets/comments/1uyd0t/20_jeopardy_questions_in_a_json_file/ I downloaded the file in a few seconds, and it also has

Re: [VOTE] Lucene logo contest, here we go again

A1, A2, D (non-binding) On Tue, Sep 1, 2020 at 11:28 AM Steve Rowe wrote: > D (binding) > > -- > Steve > > On Aug 31, 2020, at 8:26 PM, Ryan Ernst wrote: > > Dear Lucene and Solr developers! > > In February a contest was started to design a new logo for Lucene > [jira-issue]. The initial

Re: Approach towards solving split package issues?

Just to make sure, could I confirm "when the changes will be out"... Resolving split package issues should break backward compatibility (changing package names and moving classes from one module to another modules). So we have just two options, we can have these changes only on major releases -

Re: [VOTE] Lucene logo contest, here we go again

D (binding) -- Steve > On Aug 31, 2020, at 8:26 PM, Ryan Ernst wrote: > > Dear Lucene and Solr developers! > > In February a contest was started to design a new logo for Lucene > [jira-issue]. The initial attempt [first-vote] to call a vote resulted in > some confusion on the rules, as well

Remove ExternalFileField?

Is this another thing we really should remove? What use-cases are served by this that are _not_ served by updating SV numeric values? - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail:

RE: [JENKINS] Lucene » Lucene-Solr-Check-master - Build # 90 - Failure!

That's the issue: > Task :validateSourcePatterns tabs instead spaces: solr/bin/solr.cmd > Task :validateSourcePatterns FAILED - Uwe Schindler Achterdiek 19, D-28357 Bremen https://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Apache Jenkins Server > Sent:

Re: SIP-10: Solr 9 examples: Can we use Ref Guide as a dogfood example?

I've thought of providing instructions. But for good indexing, we should use adoc format as source, rather than html (as Cassandra's presentation showed), so that means dependencies to build by user to get asciidoctor library. And the way to get content, so either git clone or download the whole

Re: Approach towards solving split package issues?

> As I recall one issue was around where to put analysis packages? It's LUCENE-9317. I had worked on it before, you can see what changes will be needed for analyzers-common (and core). 2020年9月1日(火) 22:00 Michael Sokolov : > I'm in favor - there may be some difficult choices though. As I recall

Re: [VOTE] Lucene logo contest, here we go again

D (binding) > On Aug 31, 2020, at 8:26 PM, Ryan Ernst wrote: > > Dear Lucene and Solr developers! > > In February a contest was started to design a new logo for Lucene > [jira-issue]. The initial attempt [first-vote] to call a vote resulted in > some confusion on the rules, as well the

Re: Approach towards solving split package issues?

I'm in favor - there may be some difficult choices though. As I recall one issue was around where to put analysis packages? I forget the details, but there was some pretty strong feeling that you should have a functioning system with core only. However some basic analysis tools are required for

Re: [VOTE] Lucene logo contest, here we go again

A1, binding On Mon, Aug 31, 2020 at 8:26 PM Ryan Ernst wrote: > > Dear Lucene and Solr developers! > > In February a contest was started to design a new logo for Lucene > [jira-issue]. The initial attempt [first-vote] to call a vote resulted in > some confusion on the rules, as well the

Re: Approach towards solving split package issues?

yes, Jigsaw was on my mind too... > why not go ahead and try to clean it up right away? > So a strong +1 to clean this up! OK, maybe I should open two issues, one for Lucene and one for Solr, and link existing wip issues to them. Once we start it, these will be blockers for 9.0.0 release I

Re: [VOTE] Lucene logo contest, here we go again

here is my vote: A1, A2 (binding) On Tue, Sep 1, 2020 at 1:49 PM Aurélien MAZOYER wrote: > Hi community, > > I would vote for A1. > > Aurélien > > > > On Tue, 1 Sep 2020 at 13:26, Andrzej Białecki wrote: > > > A1, D (binding) > > > > > On 1 Sep 2020, at 02:26, Ryan Ernst wrote: > > > > > >

Re: [VOTE] Lucene logo contest, here we go again

A1, D (binding) > On 1 Sep 2020, at 02:26, Ryan Ernst wrote: > > Dear Lucene and Solr developers! > > In February a contest was started to design a new logo for Lucene > [jira-issue]. The initial attempt [first-vote] to call a vote resulted in > some confusion on the rules, as well the request

RE: Approach towards solving split package issues?

Hi, The biggest issue is that split packages make migrating to the Java 9 module system impossible. It's not allowed to have same package name (with classes) in different JAR files. Some of those require to open up visibility of classes. Some split packages issues were done because of package

Re: [VOTE] Lucene logo contest, here we go again

Ryan, FYI the links to proposals C are incorrect as they all use the attachment ID of the first proposal, so all links point to the same logo, here are the correct links: [C1] https://issues.apache.org/jira/secure/attachment/13006392/lucene_logo1_full.pdf [C2]

Re: [VOTE] Lucene logo contest, here we go again

A1, D (binding) On Tue, Sep 1, 2020 at 3:33 AM Anshum Gupta wrote: > Based on the options, I like the current one the most. > > D (binding) > > On Mon, Aug 31, 2020 at 5:26 PM Ryan Ernst wrote: > >> Dear Lucene and Solr developers! >> >> In February a contest was started to design a new logo

Re: [VOTE] Lucene logo contest, here we go again

Based on the options, I like the current one the most. D (binding) On Mon, Aug 31, 2020 at 5:26 PM Ryan Ernst wrote: > Dear Lucene and Solr developers! > > In February a contest was started to design a new logo for Lucene > [jira-issue]. The initial attempt [first-vote] to call a vote resulted

Re: [VOTE] Lucene logo contest, here we go again

D (binding) On Tue, Sep 1, 2020 at 5:15 PM Jan Høydahl wrote: > > D (binding) > > Jan > > 1. sep. 2020 kl. 02:26 skrev Ryan Ernst : > > Dear Lucene and Solr developers! > > In February a contest was started to design a new logo for Lucene > [jira-issue]. The initial attempt [first-vote] to call

Re: Approach towards solving split package issues?

This is a big headache for many things. I wouldn't mind doing this even for 9x. This is a major release, why not go ahead and try to clean it up right away? Dawid On Mon, Aug 31, 2020 at 11:50 PM Tomoko Uchida wrote: > > Hello devs, > > we have lots of package name conflicts (shared package

[ANNOUNCE] Apache Solr 8.6.2 released

01 September 2020, Apache Solr™ 8.6.2 available The Lucene PMC is pleased to announce the release of Apache Solr 8.6.2 Solr is the popular, blazing fast, open source NoSQL search platform from the Apache Lucene project. Its major features include powerful full-text search, hit highlighting,

[ANNOUNCE] Apache Lucene 8.6.2 released

01 September 2020, Apache Lucene™ 8.6.2 available The Lucene PMC is pleased to announce the release of Apache Lucene 8.6.2. Apache Lucene is a high-performance, full-featured text search engine library written entirely in Java. It is a technology suitable for nearly any application that requires

Re: Checking dependencies in gradle after code is removed

bq. you get a lot of entries there That's why this is to large degree automated. You do have a lot of entries because it's a union of all dependencies across all sub-projects. While this may seem like a negative, it's not - it ensures everyone stays on the same set of dependencies. Makes life

Re: [VOTE] Lucene logo contest, here we go again

D (binding) Jan > 1. sep. 2020 kl. 02:26 skrev Ryan Ernst : > > Dear Lucene and Solr developers! > > In February a contest was started to design a new logo for Lucene > [jira-issue]. The initial attempt [first-vote] to call a vote resulted in > some confusion on the rules, as well the

Re: [VOTE] Lucene logo contest, here we go again

I'm still in favor of the current logo (D), binding vote. Dawid - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: SIP-10: Solr 9 examples: Can we use Ref Guide as a dogfood example?

I’d rather ship a tutorial and tooling that explains how to index the ref-guide, than shipping a binary index. What other full-text datasets have you considered as candidates for getting-started examples? Jan > 1. sep. 2020 kl. 05:53 skrev Alexandre Rafalovitch : > > I did not say it was