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

Any good text Information Retrieval dataset may be a good candidate. https://github.com/harpribot/awesome-information-retrieval#datasets these datasets have benchmarks and sample queries also. On Fri, Sep 4, 2020 at 11:26 AM David Smiley wrote: > It's tempting to accomplish two goals at once

Re: The "supported" way to run gradle -- was: Re: [jira] [Commented] (LUCENE-9495) Ref Guide gradle buildSite ignores version parameter

Yep; I also use oh-my-zsh with the gradle plugin, and so I simply type "gw" ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Wed, Sep 2, 2020 at 3:32 PM Jan Høydahl wrote: > I’m using zsh shell with oh-my-zsh and the gradle plugin. It adds an alias

Re: [JENKINS] Lucene » Lucene-Solr-Tests-8.x - Build # 118 - Still Failing!

I pushed a fix, there is no Deflater#setDictionary(ByteBuffer) on JDK 8. On Fri, Sep 4, 2020 at 11:04 AM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > Build: > https://ci-builds.apache.org/job/Lucene/job/Lucene-Solr-Tests-8.x/118/ > > All tests passed > > Build Log: > [...truncated

Re: Migrate Solr helm chart into apache/lucene-solr repo

Yea, ComDev is probably a place to discuss whether ASF wants to host some helm repo. We are discussing how to incubate solr-operator into ASF, and since operators are a superior way to manage a complex stateful k8s application, I’m not sure what benefit there would be for the project to also

Re: Checking dependencies in gradle after code is removed

> What's the path of the ".lock" file you refer to? versions.lock See help/dependencies.txt for more. D. - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org

Re: The "supported" way to run gradle -- was: Re: [jira] [Commented] (LUCENE-9495) Ref Guide gradle buildSite ignores version parameter

> I have 'gradle' aliased to 'gw' ( aka: 'gdub" => > https://github.com/gdubw/gdub ) ... which i thought was a recomendation I > had seen from Dawid but i'm not finidng it now, so i honestly have no idea > where I leaned about it. I think it might have been Mark Miller's; I'm on Windows and so

Re: The "supported" way to run gradle -- was: Re: [jira] [Commented] (LUCENE-9495) Ref Guide gradle buildSite ignores version parameter

I would rather do the opposite - have that wiki page reference (or link to) the help pages in the code... Don't get me wrong, but I prefer when it lives with the code in one repository so that changes can be updated, etc. I know, I'm old-fashioned. Don't even use md or anything like that. But

Re: The "supported" way to run gradle -- was: Re: [jira] [Commented] (LUCENE-9495) Ref Guide gradle buildSite ignores version parameter

vi forever! I think my counter-argument is that it’s hard to pack lots of information into a help file and have it be useful. My mental model here is that “gradlew help” should be short enough to give a direction without causing the reader's eyes to glaze over so linking in the Wiki page is

PayloadDecoder.FLOAT_DECODER

In reviewing SOLR-14787 , with the author verbally, he pointed out there's some duplicated code where he needed to decode a payload into a float. We have org.apache.lucene.analysis.payloads.PayloadHelper#decodeFloat(byte[], int) but

Re: Name for the directory above solr.home?

> I really wish the default cores dir was not solr.home itself but one > directory beneath. Why? That is worth exploring. I am ok - if others are - with solr.home containing *) solr.in.sh *) configset *) logs *) log and related configuration *) userfiles *) filestore *) solr.xml *) actual cores

Re: Name for the directory above solr.home?

I feel that maybe we don't treat it special mentally, but then it actually is. At least with minimum custom locations configured. Consider: 1) What is in "server", above "server/solr" * resources/log4j2.xml (because of magic jetty classpath mechanism) * logs * NOT server/solr/configsets (but

Re: Name for the directory above solr.home?

On Fri, Sep 4, 2020 at 10:42 AM Alexandre Rafalovitch wrote: > I feel that maybe we don't treat it special mentally, but then it > actually is. At least with minimum custom locations configured. > > Consider: > 1) What is in "server", above "server/solr" > * resources/log4j2.xml (because of

Re: Migrate Solr helm chart into apache/lucene-solr repo

Discussion on-going here https://lists.apache.org/thread.html/rcb608739206d788785081073a0deb417ffa9981634975fc5525dc769%40%3Cdev.community.apache.org%3E On 2020/09/03 16:22:37, "Christine Poerschke (BLOOMBERG/ LONDON)" wrote: > I'd suggest Apache Community Development as a potential place for

Re: Checking dependencies in gradle after code is removed

Thanks! This "/help" folder is something I've overlooked. You've done a fine job of maintaining a variety of information for developers. Cassandra (and everyone really): should we move /dev-docs somewhere else? A new person browsing seeing "dev-docs" might notice it first (alphabetically first

Re: Name for the directory above solr.home?

On Fri, Sep 4, 2020 at 11:24 AM Alexandre Rafalovitch wrote: > > I really wish the default cores dir was not solr.home itself but one > directory beneath. > Why? That is worth exploring. > Because core discovery looks for cores in directories that are not cores (e.g. filestore) > > I am ok -

Re: Name for the directory above solr.home?

coreRootDirectory! If it takes a relative path, I am good with that. Great even. We can update default solr.xml and fix documentation/whatever. The rest of the files can go in solr.home. Updated SIP-10 as primary path to explore for layout. Regards, Alex. P.s. server/solr should be

Re: The "supported" way to run gradle -- was: Re: [jira] [Commented] (LUCENE-9495) Ref Guide gradle buildSite ignores version parameter

re: “gradle newbie”. Can we reference: https://cwiki.apache.org/confluence/display/SOLR/Building+Solr+with+Gradle? I think it makes sense to put a reference to that in the gradle help file rather than try to reproduce that info in the text and then have to keep them coordinated. I’m thinking

Re: [jira] [Commented] (SOLR-13973) Deprecate Tika

Let’s discuss how we can accommodate Drupal and Solarium (and others) with a minimal amount of pain to those projects rather than insist on keeping things the way they are. We’ve been recommending against using ExtractingRequestHandler in production for years and apparently that advice has

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

A1, D, A2 (binding) On Fri, Sep 4, 2020 at 12:46 AM David Smiley wrote: > > (binding) > vote: D, A1 > > > (thanks Ryan for your thorough vote instructions & preparation) - To unsubscribe, e-mail:

Re: SIP-10 Improve Getting Started experience

+100 > On Sep 4, 2020, at 1:11 AM, David Smiley wrote: > > Thank you, thank you, thank you! > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley > > > On Wed, Aug 26, 2020 at 3:42 PM Alexandre Rafalovitch > wrote: > Dear all, > > Based on the

Re: The "supported" way to run gradle -- was: Re: [jira] [Commented] (LUCENE-9495) Ref Guide gradle buildSite ignores version parameter

> That gets kind of circular and the two can certainly get out of sync... > Right. I personally much prefer editing text files in the repository than wiki pages (and I rarely look at our cwiki, sadly). Dawid

Re: Migrate Solr helm chart into apache/lucene-solr repo

Agree with Jan ... the solr-operator is the way we should recommend deploying Solr in Kubernetes vs. using Helm. On Fri, Sep 4, 2020 at 5:45 AM Jan Høydahl wrote: > Yea, ComDev is probably a place to discuss whether ASF wants to host some > helm repo. > > We are discussing how to incubate

Re: Checking dependencies in gradle after code is removed

The location doesn't really matter I think - I just wouldn't want it to be mixed with lots of other content... These things are build-related. The same content appears when you type ./gradlew help or even just ./gradlew Try it. Dawid On Fri, Sep 4, 2020 at 5:32 PM David Smiley wrote: >