Re: Welcome Atri Sharma as Lucene/Solr committer

Congrats, Atri! On Wed, Sep 18, 2019 at 4:12 PM Adrien Grand wrote: > Hi all, > > Please join me in welcoming Atri Sharma as Lucene/ Solr committer! > > If you are following activity on Lucene, this name will likely sound > familiar to you: Atri has been very busy trying to improve Lucene over

Re: [POLL] Should notifications of NEW Jira issues go to dev@?

I've been playing with JIRA's built-in email digest subscription to see what it's like. At the bottom of this email is the first part of it, edited to be a fewer number of issues. See

Re: Welcome Atri Sharma as Lucene/Solr committer

Thank you so much, everybody, for your kind words. Regards, Atri On Thu, Sep 19, 2019 at 8:06 AM David Smiley wrote: > > Congrats and welcome Atri! -- Regards, Atri Apache Concerted - To unsubscribe, e-mail:

Re: Rethinking how we publish the Solr Ref Guide

Overall the direction here sounds good to me. I have/use the PDFs but lately less so since I'm more and more simply searching the asciidoc files within my IDE and viewing them nicely with the IDE plugin simultaneously. ~ David Smiley Apache Lucene/Solr Search Developer

Re: Welcome Atri Sharma as Lucene/Solr committer

Congrats and welcome Atri!

Re: Welcome Atri Sharma as Lucene/Solr committer

Congratulations and welcome, Atri! 2019年9月19日(木) 4:02 Tomás Fernández Löbbe : > > Welcome, Atri! > > On Wed, Sep 18, 2019 at 10:05 AM Steve Rowe wrote: >> >> Congrats and welcome, Atri! >> >> -- >> Steve >> >> > On Sep 18, 2019, at 3:11 AM, Adrien Grand wrote: >> > >> > Hi all, >> > >> > Please

Re: Rethinking how we publish the Solr Ref Guide

: > However Anshum does make a good point that users wouldn't know when : the pages have changed. I think it would be great to have a link on each : ref-guide page that shows the last modified date and links to the : history of that page in github : Perhaps we could instead provide a single

Re: Rethinking how we publish the Solr Ref Guide

> However Anshum does make a good point that users wouldn't know when the pages > have changed. I think it would be great to have a link on each ref-guide page > that shows the last modified date and links to the history of that page in > github We now have an "Errata" page, which is never

Re: Rethinking how we publish the Solr Ref Guide

I've had issues with asiidoc features available for the HTML version that didn't work in PDF, and it was pretty frustrating to work around it. I think just having the site would be an improvement for the development side, but I've never used the PDF version myself. Easy back-porting of

Re: Rethinking how we publish the Solr Ref Guide

+1 to skip pdf and auto publish ref guides to html on every merge to a branch. We could also start publishing a draft 9.x guide there, clearly labeled as work in progress. Jan Høydahl > 18. sep. 2019 kl. 19:38 skrev Chris Hostetter : > > > First and foremost I should mention: I'm currently

Re: [POLL] Should notifications of NEW Jira issues go to dev@?

My vote: [v ] Leave it as is I guess one could achieve the same goal without sending to dev@ if Jira allowed users to configure notifications for certain projects individually. We could then document somewhere that option for those who don’t want to subscribe to issues@. Now the notification

Re: Welcome Atri Sharma as Lucene/Solr committer

Welcome, Atri! On Wed, Sep 18, 2019 at 10:05 AM Steve Rowe wrote: > Congrats and welcome, Atri! > > -- > Steve > > > On Sep 18, 2019, at 3:11 AM, Adrien Grand wrote: > > > > Hi all, > > > > Please join me in welcoming Atri Sharma as Lucene/ Solr committer! > > > > If you are following activity

Re: [POLL] Should notifications of NEW Jira issues go to dev@?

[x] A mail to dev@ for every new JIRA [x] One daily digest mail per day with a list of new JIRAs One of the two looks fine. I think these methods seem possible to prevent missing new issues from the issues@ folder. On Thu, Sep 19, 2019 at 12:46 AM Atri Sharma wrote: > [v] leave it as it is — I

Re: Notes from the committers' meeting at Activate 2019

: ASF has us legally covered, and from the foundation's side, GitHub : issues is equal to JIRA issues and GitHub PRs are equal to patches in : JIRA. : > People that wish to continue using their Apache committer accounts to : commit code may continue doing so on gitbox.apache.org with their

Re: Rethinking how we publish the Solr Ref Guide

First and foremost I should mention: I'm currently in favor of just about everything Cassandra has suggested here... : So, I propose making some radical changes. My ideas here require a shift : from thinking of the Guide as a release artifact like the binaries to : thinking of it similar to

Re: Rethinking how we publish the Solr Ref Guide

Thank you Cassandra for all of your effort so far. I just love that idea. As I said in my previous email (based on my discussion with Cassandra at Activate), having 2 processes, releases, one of which almost the responsibility of one person doesn't sound reasonable. It would also be great to get

Re: Welcome Atri Sharma as Lucene/Solr committer

Congrats and welcome, Atri! -- Steve > On Sep 18, 2019, at 3:11 AM, Adrien Grand wrote: > > Hi all, > > Please join me in welcoming Atri Sharma as Lucene/ Solr committer! > > If you are following activity on Lucene, this name will likely sound > familiar to you: Atri has been very busy

Re: Rethinking how we publish the Solr Ref Guide

+1 to automate... I never use the PDF I'd be happy to loose it. The page count is the best part of the PDF :). As far as indexing the ref guide... Cassandra gave a talk on that last year... https://www.youtube.com/watch?v=DixlnxAk08s=PLU6n9Voqu_1HW8-VavVMa9lP8-oF8Oh5t=14 On Wed, Sep 18, 2019 at

Re: Rethinking how we publish the Solr Ref Guide

+1 on the suggested process. +1 on PDF just being too big, though it is fun to quote the page count. An additional idea piggy-backing on this is that in step 4, we could also automatically build a local example/index that links to the public version. So, people could search the guide locally and

Rethinking how we publish the Solr Ref Guide

The delays getting the Ref Guides for 8.x releases out have caused me to think a bit about the Ref Guide publication process. It seems clear others aren't able to pick up the process when I can't and I’m sure there are a million individual reasons for that so I don't intend to shame or blame

Re: Direct I/O

Ahh yes sorry you are right Dawid and Uwe. Mike McCandless http://blog.mikemccandless.com On Wed, Sep 18, 2019 at 10:11 AM Uwe Schindler wrote: > The direct io has in fact the problem which was just wrongly named by > Dawid: Block alignment is needed - on disk and not in memory. In short:

Re: Welcome Atri Sharma as Lucene/Solr committer

Welcome! Karl On Wed, Sep 18, 2019 at 11:38 AM Namgyu Kim wrote: > Congratulations and welcome, Atri! XD > > 2019년 9월 19일 (목) 오전 12:24, Gus Heck 님이 작성: > >> Welcome :) >> >> On Wed, Sep 18, 2019 at 11:21 AM Kevin Risden wrote: >> >>> Congrats and welcome Atri! >>> >>> Kevin Risden >>> >>> >>>

Re: [POLL] Should notifications of NEW Jira issues go to dev@?

[v] leave it as it is — I like it quiet On Wed, 18 Sep 2019 at 19:42, Cassandra Targett wrote: > [v ] Leave it as is - I like quiet > > I like the clear separation between the lists. It already feels less > hectic/overwhelming to me. I will read both as often as I can anyway, so I > don’t feel

Re: The Lucene Solr Gradle Build Game plan

I've been eyeballing Mark's impressive work on the build system in Gradle. Hoss asked a numer of questions that relate to tests and I feel I should address them, even if some poorly. Here it comes, inlined with Hoss's questions. > If tests_jvms is a lucene/solr specific property, that needs to be

Re: Welcome Atri Sharma as Lucene/Solr committer

Congratulations and welcome, Atri! XD 2019년 9월 19일 (목) 오전 12:24, Gus Heck 님이 작성: > Welcome :) > > On Wed, Sep 18, 2019 at 11:21 AM Kevin Risden wrote: > >> Congrats and welcome Atri! >> >> Kevin Risden >> >> >> On Wed, Sep 18, 2019 at 11:05 AM Yonik Seeley wrote: >> >>> Congrats Atri! >>> >>>

Re: 8.3 release

As I’ve mentioned to some of you over the past couple of weeks, I want to propose that we don’t “release” the Ref Guide at all the way we have been doing it. It deserves a separate thread, which since it’s come up a few times this week I should start now, but in essence, my idea is to no

Re: [POLL] Should notifications of NEW Jira issues go to dev@?

[ ] Leave it as is - I like quiet [x] A mail to dev@ for every new JIRA [x] One daily digest mail per day with a list of new JIRAs [ ] Other (explain): ___ On Wed, Sep 18, 2019 at 5:10 AM Jan Høydahl wrote: > Hi, > > The transition to issues@ and builds@ lists (LUCENE-8951) is

Re: Welcome Atri Sharma as Lucene/Solr committer

Welcome :) On Wed, Sep 18, 2019 at 11:21 AM Kevin Risden wrote: > Congrats and welcome Atri! > > Kevin Risden > > > On Wed, Sep 18, 2019 at 11:05 AM Yonik Seeley wrote: > >> Congrats Atri! >> >> -Yonik >> >> >> On Wed, Sep 18, 2019 at 3:12 AM Adrien Grand wrote: >> >>> Hi all, >>> >>> Please

Re: 8.3 release

I learned recently that it's actually all documented here: https://lucene.apache.org/solr/guide/8_1/how-to-contribute.html#ref-guide-publication-process On Tue, Sep 17, 2019 at 7:31 PM Ishan Chattopadhyaya < ichattopadhy...@gmail.com> wrote: > Hi Adrien, > Indeed, meant to write about starting

Re: Welcome Atri Sharma as Lucene/Solr committer

Congrats and welcome Atri! Kevin Risden On Wed, Sep 18, 2019 at 11:05 AM Yonik Seeley wrote: > Congrats Atri! > > -Yonik > > > On Wed, Sep 18, 2019 at 3:12 AM Adrien Grand wrote: > >> Hi all, >> >> Please join me in welcoming Atri Sharma as Lucene/ Solr committer! >> >> If you are following

Re: Welcome Atri Sharma as Lucene/Solr committer

Congrats Atri! -Yonik On Wed, Sep 18, 2019 at 3:12 AM Adrien Grand wrote: > Hi all, > > Please join me in welcoming Atri Sharma as Lucene/ Solr committer! > > If you are following activity on Lucene, this name will likely sound > familiar to you: Atri has been very busy trying to improve

Re: Notes from the committers' meeting at Activate 2019

Yes I've used that GitHub issues interface many many times and IMHO and it sucks. I put up with it because it's free and I'm not rich. I have a small herd of stuff I have tossed up in git hub over the years across 2 accounts, and I maintain JesterJ in GitHub... I'd move it to Jira in a heart beat

Re: [POLL] Should notifications of NEW Jira issues go to dev@?

[v ] Leave it as is - I like quiet I like the clear separation between the lists. It already feels less hectic/overwhelming to me. I will read both as often as I can anyway, so I don’t feel I’ll miss anything if the lists stay the way they are now. There is a Jira plugin to support email

Re: Direct I/O

The direct io has in fact the problem which was just wrongly named by Dawid: Block alignment is needed - on disk and not in memory. In short: You can't read or write a single byte anywhere in file; you need a buffering layer in-between that takes care of alignment. NativeUnixDir does this. Uwe

Re: Direct I/O

Thanks for the explanation, Mike! D. On Wed, Sep 18, 2019 at 3:21 PM Michael McCandless wrote: > > Dawid, it's confusing: direct IO is different from a direct ByteBuffer! > > Direct IO means you bypass all kernel "smarts", so the Linux buffer cache is > not used, no IO scheduling, no write

Re: [POLL] Should notifications of NEW Jira issues go to dev@?

Going for a daily digest bot we could clarify this in the email text: Here is a list of new Lucene/Solr issues created on -MM-DD LUCENE-NNN Nice new feature SOLR-NNNUnfortunate bug To get updates for these issues in the future, watch them in JIRA. To get updates for all issues,

Re: [POLL] Should notifications of NEW Jira issues go to dev@?

[x] Leave it as is - I like quiet It's not that much that I like quiet, but rather that I can easily imagine it become confusing over time as new contributors join the list and think they get notified about all interactions on JIRA, only to notice several days later that it only includes

Re: Direct I/O

OK I opened https://issues.apache.org/jira/browse/LUCENE-8982. Mike McCandless http://blog.mikemccandless.com On Wed, Sep 18, 2019 at 9:23 AM Michael McCandless < luc...@mikemccandless.com> wrote: > Aha! Yes, Uwe, now I remember you explained this to me, that we can now > do direct IO purely

Re: [POLL] Should notifications of NEW Jira issues go to dev@?

Either one of "Created" notifications works for me and would be very nice: > [X] A mail to dev@ for every new JIRA > [X] One daily digest mail per day with a list of new JIRAs I sort of had that workflow already with GMail rules, so it would be nice to have it more explicitly. And, the subscribed

Re: Direct I/O

Aha! Yes, Uwe, now I remember you explained this to me, that we can now do direct IO purely in java. I think we should fix up NativeUnixDirectory, and then run some more benchmarks to see if it helps? I'll open an issue. And definitely big +1 to give us fadvise/madvise in Java so we can test

Re: Direct I/O

Dawid, it's confusing: direct IO is different from a direct ByteBuffer! Direct IO means you bypass all kernel "smarts", so the Linux buffer cache is not used, no IO scheduling, no write cache that the pdflush daemon must periodically move to disk, etc. This is normally a bad idea, and better to

Re: Welcome Atri Sharma as Lucene/Solr committer

Thank you, everybody, for the warm welcome. I work at Amazon, where I am focused on the core product search engine which serves all of our retail entities. My background is in relational and non relational databases, with a penchant for statistical and heuristics based query optimisation. I was

Re: Notes from the committers' meeting at Activate 2019

It seems like there are two discussions happening here 1> moving code _development_ to GitHub 2> moving JIRA to GitHub I want to talk about <2> Gus: Have you looked at "issues" in GitHub? See: https://github.com/apache/accumulo/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc On a _very_

Re: Welcome Atri Sharma as Lucene/Solr committer

/me humbly bows I'm glad you are here, Atri! Erik > On Sep 18, 2019, at 03:11, Adrien Grand wrote: > > Hi all, > > Please join me in welcoming Atri Sharma as Lucene/ Solr committer! > > If you are following activity on Lucene, this name will likely sound > familiar to you:

Re: [POLL] Should notifications of NEW Jira issues go to dev@?

Always some clown doesn't follow the rules. I think there's significant value in seeing the new JIRAs go by, and 4 e-mails a day isn't onerous so either of the choices I've marked are fine with me. And thanks for working on this! Unfortunately my laptop is in the shop with screen problems and all

Re: Welcome Atri Sharma as Lucene/Solr committer

Welcome Atri! Well deserved. On Wed, Sep 18, 2019 at 6:47 AM Michael Sokolov wrote: > > Welcome Atri! > > On Wed, Sep 18, 2019, 3:12 AM Adrien Grand wrote: >> >> Hi all, >> >> Please join me in welcoming Atri Sharma as Lucene/ Solr committer! >> >> If you are following activity on Lucene, this

Re: Github PR Collaboration Question

Thanks for chiming in guys. I created a JIRA for this (SOLR-13775). Haven't really thought about wording or anything yet, if either of you have any suggestions. Otherwise I'll hope to get to this over the weekend. Jason On Tue, Sep 17, 2019 at 3:39 PM David Smiley wrote: > > RE the idea of

Re: Welcome Atri Sharma as Lucene/Solr committer

Welcome Atri! On Wed, Sep 18, 2019, 3:12 AM Adrien Grand wrote: > Hi all, > > Please join me in welcoming Atri Sharma as Lucene/ Solr committer! > > If you are following activity on Lucene, this name will likely sound > familiar to you: Atri has been very busy trying to improve Lucene over >

Re: Welcome Atri Sharma as Lucene/Solr committer

Welcome Atri! Joel Bernstein http://joelsolr.blogspot.com/ On Wed, Sep 18, 2019 at 6:32 AM Jason Gerlowski wrote: > Congratulations and welcome Atri! > > On Wed, Sep 18, 2019 at 6:24 AM Shalin Shekhar Mangar > wrote: > > > > Congratulations and welcome Atri! > > > > On Wed, Sep 18, 2019 at

Re: Welcome Atri Sharma as Lucene/Solr committer

Congratulations and welcome Atri! On Wed, Sep 18, 2019 at 6:24 AM Shalin Shekhar Mangar wrote: > > Congratulations and welcome Atri! > > On Wed, Sep 18, 2019 at 3:12 AM Adrien Grand wrote: >> >> Hi all, >> >> Please join me in welcoming Atri Sharma as Lucene/ Solr committer! >> >> If you are

Re: Welcome Atri Sharma as Lucene/Solr committer

Congratulations and welcome Atri! On Wed, Sep 18, 2019 at 3:12 AM Adrien Grand wrote: > Hi all, > > Please join me in welcoming Atri Sharma as Lucene/ Solr committer! > > If you are following activity on Lucene, this name will likely sound > familiar to you: Atri has been very busy trying to

Re: 8.3 release

That timeframe sounds good. A major focus for me will be completing and merging SOLR-13105 which is part of the ref guide. Joel Bernstein http://joelsolr.blogspot.com/ On Tue, Sep 17, 2019 at 9:19 PM Anshum Gupta wrote: > I think it makes

Re: Welcome Atri Sharma as Lucene/Solr committer

Congratulations Atri! Mike McCandless http://blog.mikemccandless.com On Wed, Sep 18, 2019 at 5:49 AM Ishan Chattopadhyaya < ichattopadhy...@gmail.com> wrote: > Congrats and welcome, Atri! > > On Wed, 18 Sep, 2019, 12:15 PM MUNENDRA S N, > wrote: > >> Congratulations and welcome, Atri >> >>

Re: Welcome Atri Sharma as Lucene/Solr committer

Congrats and welcome, Atri! On Wed, 18 Sep, 2019, 12:15 PM MUNENDRA S N, wrote: > Congratulations and welcome, Atri > > > On Wed, Sep 18, 2019 at 2:12 PM Mikhail Khludnev wrote: > >> Welcome, Atri. >> >> On Wed, Sep 18, 2019 at 10:12 AM Adrien Grand wrote: >> >>> Hi all, >>> >>> Please join

Re: [POLL] Should notifications of NEW Jira issues go to dev@?

[ ] Leave it as is - I like quiet [ ] A mail to dev@ for every new JIRA [v] One daily digest mail per day with a list of new JIRAs [ ] Other (explain): ___ On Wed, Sep 18, 2019 at 12:10 PM Jan Høydahl wrote: > Hi, > > The transition to issues@ and builds@ lists (LUCENE-8951) is

Re: Welcome Atri Sharma as Lucene/Solr committer

Congratulations and welcome, Atri On Wed, Sep 18, 2019 at 2:12 PM Mikhail Khludnev wrote: > Welcome, Atri. > > On Wed, Sep 18, 2019 at 10:12 AM Adrien Grand wrote: > >> Hi all, >> >> Please join me in welcoming Atri Sharma as Lucene/ Solr committer! >> >> If you are following activity on

[POLL] Should notifications of NEW Jira issues go to dev@?

Hi, The transition to issues@ and builds@ lists (LUCENE-8951) is now completed, and I already enjoy a quieter dev@ folder! I'd like to check with all of you whether there is interest in getting notified here at dev@ about NEW Jira issue created. Currently there is an average of 4 new issues

Re: Welcome Atri Sharma as Lucene/Solr committer

Welcome, Atri. On Wed, Sep 18, 2019 at 10:12 AM Adrien Grand wrote: > Hi all, > > Please join me in welcoming Atri Sharma as Lucene/ Solr committer! > > If you are following activity on Lucene, this name will likely sound > familiar to you: Atri has been very busy trying to improve Lucene over

Re: [ANNOUNCE] New builds@ and issues@ mailing lists

REMINDER As you may have noticed, it's now much more quite around here at dev@. Automated email announcements from JIRA, Git and Jenkins now go to the new lists. If you missed this announcement earlier (due to all the noise), now is the time to subscribe, see instructions below. -- Jan

Re: Welcome Atri Sharma as Lucene/Solr committer

Welcome Atri On Wed, 18 Sep 2019 at 17:31, jim ferenczi wrote: > Congratulations Atri! > > Le mer. 18 sept. 2019 à 09:28, Ignacio Vera a écrit : > >> Welcome Atri! >> >> On Wed, Sep 18, 2019 at 9:12 AM Adrien Grand wrote: >> >>> Hi all, >>> >>> Please join me in welcoming Atri Sharma as

Re: Welcome Atri Sharma as Lucene/Solr committer

Welcome, Atri! -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 18. sep. 2019 kl. 09:11 skrev Adrien Grand : > > Hi all, > > Please join me in welcoming Atri Sharma as Lucene/ Solr committer! > > If you are following activity on Lucene, this name will likely sound

Re: Notes from the committers' meeting at Activate 2019

We as a project won't need to worry about "system of record" or what MS will do in the future. Really. I encourage all to read INFRA's post about the ASF-GitHub agreement here https://blogs.apache.org/infra/entry/apache-and-github-a-friendly In the last paragraph it states: > For many projects,

Re: Welcome Atri Sharma as Lucene/Solr committer

Congratulations and welcome, Atri!  Anshum > On Sep 18, 2019, at 12:11 AM, Adrien Grand wrote: > > Hi all, > > Please join me in welcoming Atri Sharma as Lucene/ Solr committer! > > If you are following activity on Lucene, this name will likely sound > familiar to you: Atri has been very

Re: Welcome Atri Sharma as Lucene/Solr committer

Congratulations and welcome, Atri. Dawid On Wed, Sep 18, 2019 at 9:12 AM Adrien Grand wrote: > > Hi all, > > Please join me in welcoming Atri Sharma as Lucene/ Solr committer! > > If you are following activity on Lucene, this name will likely sound > familiar to you: Atri has been very busy

Re: Welcome Atri Sharma as Lucene/Solr committer

Congratulations ! jim ferenczi 于2019年9月18日周三 下午3:31写道： > Congratulations Atri! > > Le mer. 18 sept. 2019 à 09:28, Ignacio Vera a écrit : > >> Welcome Atri! >> >> On Wed, Sep 18, 2019 at 9:12 AM Adrien Grand wrote: >> >>> Hi all, >>> >>> Please join me in welcoming Atri Sharma as Lucene/ Solr

Re: Welcome Atri Sharma as Lucene/Solr committer

Congratulations Atri! Le mer. 18 sept. 2019 à 09:28, Ignacio Vera a écrit : > Welcome Atri! > > On Wed, Sep 18, 2019 at 9:12 AM Adrien Grand wrote: > >> Hi all, >> >> Please join me in welcoming Atri Sharma as Lucene/ Solr committer! >> >> If you are following activity on Lucene, this name

Re: Welcome Atri Sharma as Lucene/Solr committer

Welcome Atri! On Wed, Sep 18, 2019 at 9:12 AM Adrien Grand wrote: > Hi all, > > Please join me in welcoming Atri Sharma as Lucene/ Solr committer! > > If you are following activity on Lucene, this name will likely sound > familiar to you: Atri has been very busy trying to improve Lucene over >

Welcome Atri Sharma as Lucene/Solr committer

Hi all, Please join me in welcoming Atri Sharma as Lucene/ Solr committer! If you are following activity on Lucene, this name will likely sound familiar to you: Atri has been very busy trying to improve Lucene over the past months. In particular, Atri recently started improving our top-hits