Re: Lucene Java 2.9.2
Other than what's left of the TokenStream issues, I think we just need a compression solution - which shouldn't be difficult. - Mark Robert Muir wrote: > https://issues.apache.org/jira/browse/SOLR-1657 > > i just struckthrough the things that are done. > > >> Mark, Robert: How far are we with progress in solr? Were there any >> additional problems with 3.0.0? >> >> Uwe >> >> - >> Uwe Schindler >> H.-H.-Meier-Allee 63, D-28213 Bremen >> http://www.thetaphi.de >> eMail: u...@thetaphi.de >> >> >> >>> -Original Message- >>> From: Uwe Schindler [mailto:u...@thetaphi.de] >>> Sent: Tuesday, January 05, 2010 1:34 PM >>> To: java-dev@lucene.apache.org >>> Subject: RE: Lucene Java 2.9.2 >>> >>> My plan was to release it together with 3.0.1. Both version then will have >>> the same bug fix status. >>> >>> I have the scripts here to build the artifacts (as I added fast vector >>> highlighter poms), so I could do it for both and start the release. >>> >>> - >>> Uwe Schindler >>> H.-H.-Meier-Allee 63, D-28213 Bremen >>> http://www.thetaphi.de >>> eMail: u...@thetaphi.de >>> >>> >>>> -Original Message- >>>> From: Michael McCandless [mailto:luc...@mikemccandless.com] >>>> Sent: Tuesday, January 05, 2010 12:26 PM >>>> To: java-dev@lucene.apache.org >>>> Subject: Re: Lucene Java 2.9.2 >>>> >>>> Lucene 2.9.2 hasn't been released yet, but I think we should release >>>> it at some point soonish? It's accumulated some important bug fixes. >>>> >>>> Mike >>>> >>>> On Mon, Jan 4, 2010 at 10:59 PM, George Aroush >>>> >>> wrote: >>> >>>>> Hi Folks, >>>>> >>>>> Over at Lucene.Net, we have 2.9.1 ready for official release. This is >>>>> >>> a >>> >>>>> port of the current Lucene Java 2.9.1 release. >>>>> >>>>> When I raised the question about releasing Lucene.Net 2.9.1, a >>>>> >>> question >>> >>>> was >>>> >>>>> asked to port over LUCENE-2190 for which a patch was quickly made >>>>> >>> (see: >>> >>>>> https://issues.apache.org/jira/browse/LUCENENET-331). This begs the >>>>> question, if Lucene.Net takes just this one patch, than Lucene.Net >>>>> >>> 2.9.1 >>> >>>> is >>>> >>>>> now 2.9.1.1 (which I personally don't like to see happening as I >>>>> >>> prefer >>> >>>> to >>>> >>>>> see a 1-to-1 release match). >>>>> >>>>> So, I examined the list of fixes made in 2.9.2 here: >>>>> https://issues.apache.org/jira/browse/LUCENE/fixforversion/12314342 >>>>> >>> and >>> >>>>> found that this is a small task to port over. >>>>> >>>>> So far so good? Good. >>>>> >>>>> Now, as far as I know, Lucene Java never made an official 2.9.2 >>>>> >>> release, >>> >>>> or >>>> >>>>> is this in the works (I don't recall seeing any email about it)? If >>>>> >>> so, >>> >>>>> what's the time line? I think our decision on the Lucene.Net side >>>>> >>> will >>> >>>> be >>>> >>>>> based on the answer to this question. >>>>> >>>>> Thanks. >>>>> >>>>> -- George >>>>> >>>>> >>>>> - >>>>> To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org >>>>> For additional commands, e-mail: java-dev-h...@lucene.apache.org >>>>> >>>>> >>>>> >>>> - >>>> To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org >>>> For additional commands, e-mail: java-dev-h...@lucene.apache.org >>>> >>> >>> - >>> To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org >>> For additional commands, e-mail: java-dev-h...@lucene.apache.org >>> >> >> - >> To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: java-dev-h...@lucene.apache.org >> >> >> > > > > -- - Mark http://www.lucidimagination.com - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
RE: Lucene Java 2.9.2
Yes, the goal is to be 1-to-1 in sync which is how it always has been and why version number consistency is important. A Lucene.Net assembly, has version number with 4 digits, like so: "Lucene.Net 2.9.1.016" -- the last number "016" is used to both signify an internal release, as the port is progressing, and bug fix specific to porting issues. In this case, my question was about porting over only 1 patch from Lucene Java 2.9.2 to Lucene.Net 2.9.1 (i.e.: a patch found in newer version of Lucene Java to an older version of Lucene.Net). If we do so, (which I'm against the idea and over at Lucene.Net we decided not to do so) than this can lead to version confusion if not well documented and possibly introduce behavior differences (based on what the 1 ported patch ends up fixing). Not only this, as you pointed out, what if Lucene Java 2.9.3 comes up, than what? -- George -Original Message- From: Chris Hostetter [mailto:hossman_luc...@fucit.org] Sent: Tuesday, January 05, 2010 3:52 PM To: java-dev@lucene.apache.org Subject: Re: Lucene Java 2.9.2 : https://issues.apache.org/jira/browse/LUCENENET-331). This begs the : question, if Lucene.Net takes just this one patch, than Lucene.Net 2.9.1 is : now 2.9.1.1 (which I personally don't like to see happening as I prefer to : see a 1-to-1 release match). As a general comment on this topic: I would suggest that if the goal of Lucene.Net is to be a 1-to-1 port (which seems like a good goal, but is certainly not mandatory if the Lucene.Net community has other ambitions) then the cleanest thing for users would be to keep the version numbers in sync 1-to-1. it reasises some questions about what to do if a bug is discovered in the *porting*. ie: if after "Lucene.Net 2.9.2" is released, it's discovered that there was a glitch, and it doesn't actually match the behavior of Lucene-JAva 2.9.2" what should be done? ... "Lucene.Net 2.9.3" and "Lucene.Net 2.9.2.1" could all concivably conflict with version numbers Lucene-Java *might* someday release. Having an anotaiton strategy that doesn't extend the dot notation used by Lucene-Java might make sense (ie: "Lucene.Net 2.9.2-a" -Hoss - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
Re: Lucene Java 2.9.2
On Tue, 5 Jan 2010, Chris Hostetter wrote: : https://issues.apache.org/jira/browse/LUCENENET-331). This begs the : question, if Lucene.Net takes just this one patch, than Lucene.Net 2.9.1 is : now 2.9.1.1 (which I personally don't like to see happening as I prefer to : see a 1-to-1 release match). As a general comment on this topic: I would suggest that if the goal of Lucene.Net is to be a 1-to-1 port (which seems like a good goal, but is certainly not mandatory if the Lucene.Net community has other ambitions) then the cleanest thing for users would be to keep the version numbers in sync 1-to-1. it reasises some questions about what to do if a bug is discovered in the *porting*. ie: if after "Lucene.Net 2.9.2" is released, it's discovered that there was a glitch, and it doesn't actually match the behavior of Lucene-JAva 2.9.2" what should be done? ... "Lucene.Net 2.9.3" and "Lucene.Net 2.9.2.1" could all concivably conflict with version numbers Lucene-Java *might* someday release. Having an anotaiton strategy that doesn't extend the dot notation used by Lucene-Java might make sense (ie: "Lucene.Net 2.9.2-a" Indeed, this is the approach taken by PyLucene: using the Lucene Java release number it was built from and adding a dash followed by a single number. For example, PyLucene 3.0.0-1 is the current release matching Lucene Java's 3.0.0 release. If a PyLucene-specific bug were found, it would likely be fixed in a PyLucene 3.0.0-2 release unless it coincided with a Lucene Java 3.0.1 release. Andi.. - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
Re: Lucene Java 2.9.2
: https://issues.apache.org/jira/browse/LUCENENET-331). This begs the : question, if Lucene.Net takes just this one patch, than Lucene.Net 2.9.1 is : now 2.9.1.1 (which I personally don't like to see happening as I prefer to : see a 1-to-1 release match). As a general comment on this topic: I would suggest that if the goal of Lucene.Net is to be a 1-to-1 port (which seems like a good goal, but is certainly not mandatory if the Lucene.Net community has other ambitions) then the cleanest thing for users would be to keep the version numbers in sync 1-to-1. it reasises some questions about what to do if a bug is discovered in the *porting*. ie: if after "Lucene.Net 2.9.2" is released, it's discovered that there was a glitch, and it doesn't actually match the behavior of Lucene-JAva 2.9.2" what should be done? ... "Lucene.Net 2.9.3" and "Lucene.Net 2.9.2.1" could all concivably conflict with version numbers Lucene-Java *might* someday release. Having an anotaiton strategy that doesn't extend the dot notation used by Lucene-Java might make sense (ie: "Lucene.Net 2.9.2-a" -Hoss - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
Re: Lucene Java 2.9.2
https://issues.apache.org/jira/browse/SOLR-1657 i just struckthrough the things that are done. > Mark, Robert: How far are we with progress in solr? Were there any > additional problems with 3.0.0? > > Uwe > > - > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > > >> -Original Message- >> From: Uwe Schindler [mailto:u...@thetaphi.de] >> Sent: Tuesday, January 05, 2010 1:34 PM >> To: java-dev@lucene.apache.org >> Subject: RE: Lucene Java 2.9.2 >> >> My plan was to release it together with 3.0.1. Both version then will have >> the same bug fix status. >> >> I have the scripts here to build the artifacts (as I added fast vector >> highlighter poms), so I could do it for both and start the release. >> >> - >> Uwe Schindler >> H.-H.-Meier-Allee 63, D-28213 Bremen >> http://www.thetaphi.de >> eMail: u...@thetaphi.de >> >> > -Original Message- >> > From: Michael McCandless [mailto:luc...@mikemccandless.com] >> > Sent: Tuesday, January 05, 2010 12:26 PM >> > To: java-dev@lucene.apache.org >> > Subject: Re: Lucene Java 2.9.2 >> > >> > Lucene 2.9.2 hasn't been released yet, but I think we should release >> > it at some point soonish? It's accumulated some important bug fixes. >> > >> > Mike >> > >> > On Mon, Jan 4, 2010 at 10:59 PM, George Aroush >> wrote: >> > > Hi Folks, >> > > >> > > Over at Lucene.Net, we have 2.9.1 ready for official release. This is >> a >> > > port of the current Lucene Java 2.9.1 release. >> > > >> > > When I raised the question about releasing Lucene.Net 2.9.1, a >> question >> > was >> > > asked to port over LUCENE-2190 for which a patch was quickly made >> (see: >> > > https://issues.apache.org/jira/browse/LUCENENET-331). This begs the >> > > question, if Lucene.Net takes just this one patch, than Lucene.Net >> 2.9.1 >> > is >> > > now 2.9.1.1 (which I personally don't like to see happening as I >> prefer >> > to >> > > see a 1-to-1 release match). >> > > >> > > So, I examined the list of fixes made in 2.9.2 here: >> > > https://issues.apache.org/jira/browse/LUCENE/fixforversion/12314342 >> and >> > > found that this is a small task to port over. >> > > >> > > So far so good? Good. >> > > >> > > Now, as far as I know, Lucene Java never made an official 2.9.2 >> release, >> > or >> > > is this in the works (I don't recall seeing any email about it)? If >> so, >> > > what's the time line? I think our decision on the Lucene.Net side >> will >> > be >> > > based on the answer to this question. >> > > >> > > Thanks. >> > > >> > > -- George >> > > >> > > >> > > - >> > > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org >> > > For additional commands, e-mail: java-dev-h...@lucene.apache.org >> > > >> > > >> > >> > - >> > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org >> > For additional commands, e-mail: java-dev-h...@lucene.apache.org >> >> >> >> - >> To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: java-dev-h...@lucene.apache.org > > > > - > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > -- Robert Muir rcm...@gmail.com - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
RE: Lucene Java 2.9.2
Thanks Uwe. Looks like we are only weeks away (maybe days). If so, then I see a good reason for Lucene.Net to also release 2.9.2. Btw, is the complete list of patches for 2.9.2 here: https://issues.apache.org/jira/browse/LUCENE/fixforversion/12314342 If so, I see 1 outstanding open issue: LUCENE-2190 Thanks. -- George -Original Message- From: Uwe Schindler [mailto:u...@thetaphi.de] Sent: Tuesday, January 05, 2010 7:43 AM To: java-dev@lucene.apache.org Subject: RE: Lucene Java 2.9.2 I wanted to mention: I wanted to wait a little bit to have progress with the last transitions in solr to 3.0 (tokenstreams are almost finished), Version support, and some segment based problems. E.g. in 3.0, we had some methods accidentally removed with deprecations and so on. In my opinion, transition of solr is a good stress test of the 3.0 API. Because of that I wanted to wait a little bit for feedback about 3.0 from solr. Mark, Robert: How far are we with progress in solr? Were there any additional problems with 3.0.0? Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Uwe Schindler [mailto:u...@thetaphi.de] > Sent: Tuesday, January 05, 2010 1:34 PM > To: java-dev@lucene.apache.org > Subject: RE: Lucene Java 2.9.2 > > My plan was to release it together with 3.0.1. Both version then will have > the same bug fix status. > > I have the scripts here to build the artifacts (as I added fast vector > highlighter poms), so I could do it for both and start the release. > > - > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > > > -Original Message- > > From: Michael McCandless [mailto:luc...@mikemccandless.com] > > Sent: Tuesday, January 05, 2010 12:26 PM > > To: java-dev@lucene.apache.org > > Subject: Re: Lucene Java 2.9.2 > > > > Lucene 2.9.2 hasn't been released yet, but I think we should release > > it at some point soonish? It's accumulated some important bug fixes. > > > > Mike > > > > On Mon, Jan 4, 2010 at 10:59 PM, George Aroush > wrote: > > > Hi Folks, > > > > > > Over at Lucene.Net, we have 2.9.1 ready for official release. This is > a > > > port of the current Lucene Java 2.9.1 release. > > > > > > When I raised the question about releasing Lucene.Net 2.9.1, a > question > > was > > > asked to port over LUCENE-2190 for which a patch was quickly made > (see: > > > https://issues.apache.org/jira/browse/LUCENENET-331). This begs the > > > question, if Lucene.Net takes just this one patch, than Lucene.Net > 2.9.1 > > is > > > now 2.9.1.1 (which I personally don't like to see happening as I > prefer > > to > > > see a 1-to-1 release match). > > > > > > So, I examined the list of fixes made in 2.9.2 here: > > > https://issues.apache.org/jira/browse/LUCENE/fixforversion/12314342 > and > > > found that this is a small task to port over. > > > > > > So far so good? Good. > > > > > > Now, as far as I know, Lucene Java never made an official 2.9.2 > release, > > or > > > is this in the works (I don't recall seeing any email about it)? If > so, > > > what's the time line? I think our decision on the Lucene.Net side > will > > be > > > based on the answer to this question. > > > > > > Thanks. > > > > > > -- George > > > > > > > > > - > > > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > > > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > > > > > > > > > - > > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > > > - > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
RE: Lucene Java 2.9.2
I wanted to mention: I wanted to wait a little bit to have progress with the last transitions in solr to 3.0 (tokenstreams are almost finished), Version support, and some segment based problems. E.g. in 3.0, we had some methods accidentally removed with deprecations and so on. In my opinion, transition of solr is a good stress test of the 3.0 API. Because of that I wanted to wait a little bit for feedback about 3.0 from solr. Mark, Robert: How far are we with progress in solr? Were there any additional problems with 3.0.0? Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Uwe Schindler [mailto:u...@thetaphi.de] > Sent: Tuesday, January 05, 2010 1:34 PM > To: java-dev@lucene.apache.org > Subject: RE: Lucene Java 2.9.2 > > My plan was to release it together with 3.0.1. Both version then will have > the same bug fix status. > > I have the scripts here to build the artifacts (as I added fast vector > highlighter poms), so I could do it for both and start the release. > > - > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > > > -Original Message- > > From: Michael McCandless [mailto:luc...@mikemccandless.com] > > Sent: Tuesday, January 05, 2010 12:26 PM > > To: java-dev@lucene.apache.org > > Subject: Re: Lucene Java 2.9.2 > > > > Lucene 2.9.2 hasn't been released yet, but I think we should release > > it at some point soonish? It's accumulated some important bug fixes. > > > > Mike > > > > On Mon, Jan 4, 2010 at 10:59 PM, George Aroush > wrote: > > > Hi Folks, > > > > > > Over at Lucene.Net, we have 2.9.1 ready for official release. This is > a > > > port of the current Lucene Java 2.9.1 release. > > > > > > When I raised the question about releasing Lucene.Net 2.9.1, a > question > > was > > > asked to port over LUCENE-2190 for which a patch was quickly made > (see: > > > https://issues.apache.org/jira/browse/LUCENENET-331). This begs the > > > question, if Lucene.Net takes just this one patch, than Lucene.Net > 2.9.1 > > is > > > now 2.9.1.1 (which I personally don't like to see happening as I > prefer > > to > > > see a 1-to-1 release match). > > > > > > So, I examined the list of fixes made in 2.9.2 here: > > > https://issues.apache.org/jira/browse/LUCENE/fixforversion/12314342 > and > > > found that this is a small task to port over. > > > > > > So far so good? Good. > > > > > > Now, as far as I know, Lucene Java never made an official 2.9.2 > release, > > or > > > is this in the works (I don't recall seeing any email about it)? If > so, > > > what's the time line? I think our decision on the Lucene.Net side > will > > be > > > based on the answer to this question. > > > > > > Thanks. > > > > > > -- George > > > > > > > > > - > > > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > > > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > > > > > > > > > - > > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > > > - > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
RE: Lucene Java 2.9.2
My plan was to release it together with 3.0.1. Both version then will have the same bug fix status. I have the scripts here to build the artifacts (as I added fast vector highlighter poms), so I could do it for both and start the release. - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Michael McCandless [mailto:luc...@mikemccandless.com] > Sent: Tuesday, January 05, 2010 12:26 PM > To: java-dev@lucene.apache.org > Subject: Re: Lucene Java 2.9.2 > > Lucene 2.9.2 hasn't been released yet, but I think we should release > it at some point soonish? It's accumulated some important bug fixes. > > Mike > > On Mon, Jan 4, 2010 at 10:59 PM, George Aroush wrote: > > Hi Folks, > > > > Over at Lucene.Net, we have 2.9.1 ready for official release. This is a > > port of the current Lucene Java 2.9.1 release. > > > > When I raised the question about releasing Lucene.Net 2.9.1, a question > was > > asked to port over LUCENE-2190 for which a patch was quickly made (see: > > https://issues.apache.org/jira/browse/LUCENENET-331). This begs the > > question, if Lucene.Net takes just this one patch, than Lucene.Net 2.9.1 > is > > now 2.9.1.1 (which I personally don't like to see happening as I prefer > to > > see a 1-to-1 release match). > > > > So, I examined the list of fixes made in 2.9.2 here: > > https://issues.apache.org/jira/browse/LUCENE/fixforversion/12314342 and > > found that this is a small task to port over. > > > > So far so good? Good. > > > > Now, as far as I know, Lucene Java never made an official 2.9.2 release, > or > > is this in the works (I don't recall seeing any email about it)? If so, > > what's the time line? I think our decision on the Lucene.Net side will > be > > based on the answer to this question. > > > > Thanks. > > > > -- George > > > > > > - > > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > > > > > - > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
Re: Lucene Java 2.9.2
Lucene 2.9.2 hasn't been released yet, but I think we should release it at some point soonish? It's accumulated some important bug fixes. Mike On Mon, Jan 4, 2010 at 10:59 PM, George Aroush wrote: > Hi Folks, > > Over at Lucene.Net, we have 2.9.1 ready for official release. This is a > port of the current Lucene Java 2.9.1 release. > > When I raised the question about releasing Lucene.Net 2.9.1, a question was > asked to port over LUCENE-2190 for which a patch was quickly made (see: > https://issues.apache.org/jira/browse/LUCENENET-331). This begs the > question, if Lucene.Net takes just this one patch, than Lucene.Net 2.9.1 is > now 2.9.1.1 (which I personally don't like to see happening as I prefer to > see a 1-to-1 release match). > > So, I examined the list of fixes made in 2.9.2 here: > https://issues.apache.org/jira/browse/LUCENE/fixforversion/12314342 and > found that this is a small task to port over. > > So far so good? Good. > > Now, as far as I know, Lucene Java never made an official 2.9.2 release, or > is this in the works (I don't recall seeing any email about it)? If so, > what's the time line? I think our decision on the Lucene.Net side will be > based on the answer to this question. > > Thanks. > > -- George > > > - > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
