While much of the content in this thread is valid and is important,
especially concerns, pain points, and implementation details... we've
gotten way off topic.
road map != implementation details. We should keep to a much a higher
level discussion to get this knocked out.
Lets outline the
I'd like to port over as much as possible. There is a lot of great stuff there
and it only opens our user base up. That said I think they are nice to haves
not requirements
From: Christopher Currens
Sent: 11/22/2011 10:13 AM
To: lucene-net-dev@lucene.apache.org
other possible goals (these can be assigned to any milestone and pushed
back when needed)
* Enhanced BCL support - interfaces, operator overloads, etc.
* FxCop support - fix or suppress messages
* Investigate CLSCompliance - already partially done by prescott and many
thanks for that.
*
Some of the contrib material is very important.
I am still using ikvmc to compile lucene because I use the FSTLookup which
is only available in version 3. It provides guesses for misspelled words
for drop downs and such and is more efficient than a general fuzzy search.
On Tue, Nov 22, 2011 at
On 2011-11-22, Prescott Nasser wrote:
My goal is to release 2.9.4 this month - it looks like we have no -1s
from our dev list so in the next day or so I will put that to the
general incubator list.
Please remember to mention you need two more IPMC member votes.
With the 4.0 release we
My goal is to release 2.9.4 this month - it looks like we have no -1s
from our dev list so in the next day or so I will put that to the
general incubator list.
Please remember to mention you need two more IPMC member votes.
I just sent that vote email out - do you want me to update?
On 2011-11-23, Prescott Nasser wrote:
My goal is to release 2.9.4 this month - it looks like we have no -1s
from our dev list so in the next day or so I will put that to the
general incubator list.
Please remember to mention you need two more IPMC member votes.
I just sent that vote email
In the same vain: sort out the build process in a way that doesn't
require the tools to be checked into svn.
https://cwiki.apache.org/confluence/display/LUCENENET/Road+Map
Posting these under floating goals on wiki. I already have some ideas on
how this can be done, so I've linked the above
[
https://issues.apache.org/jira/browse/PYLUCENE-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155389#comment-13155389
]
Michael McCandless commented on PYLUCENE-12:
I noticed one unfriendliness
[
https://issues.apache.org/jira/browse/PYLUCENE-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155397#comment-13155397
]
Michael McCandless commented on PYLUCENE-12:
Hmm, one more unfriendliness: if
I'm trying to wrap Weka, a popular machine learning system, with PyLucene.
One of the Weka classes, weka.core.Utils, has a public static variable,
and a public static method, with the same name (see below). When I
compile it, JCC has no way to say that, and I get the following:
In file included
[
https://issues.apache.org/jira/browse/LUCENE-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154937#comment-13154937
]
Shai Erera commented on LUCENE-3583:
You're right, I didn't notice it. I'll work on
[
https://issues.apache.org/jira/browse/LUCENE-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154947#comment-13154947
]
Shai Erera commented on LUCENE-3583:
Committed Robert's changes to trunk rev 1204851.
[
https://issues.apache.org/jira/browse/LUCENE-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154950#comment-13154950
]
Shai Erera commented on LUCENE-3583:
Ok found it: testInvalidFormat expected
[
https://issues.apache.org/jira/browse/SOLR-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar resolved SOLR-2699.
-
Resolution: Fixed
Fix Version/s: 4.0
Assignee: Yonik Seeley
The
[
https://issues.apache.org/jira/browse/SOLR-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155017#comment-13155017
]
Shalin Shekhar Mangar commented on SOLR-2755:
-
Patrick, I'm not sure that the
[
https://issues.apache.org/jira/browse/SOLR-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155035#comment-13155035
]
Jan Høydahl commented on SOLR-2607:
---
+1 I saw this earlier but just thought about it
[
https://issues.apache.org/jira/browse/SOLR-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-2904:
Attachment: SOLR-2904-branch_3x.patch
Patch for branch_3x.
[
https://issues.apache.org/jira/browse/SOLR-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-1565:
Attachment: SOLR-1565-branch_3x.patch
Patch for branch_3x.
[
https://issues.apache.org/jira/browse/SOLR-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-1565:
Fix Version/s: (was: 3.5)
3.6
StreamingUpdateSolrServer
[
https://issues.apache.org/jira/browse/SOLR-2904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-2904:
Fix Version/s: (was: 3.5)
3.6
[
https://issues.apache.org/jira/browse/LUCENE-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155094#comment-13155094
]
Uwe Schindler commented on LUCENE-3464:
---
I will add a comment to the javadocs with
[
https://issues.apache.org/jira/browse/LUCENE-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-3464.
---
Resolution: Fixed
Committed 3.x revision: 1204970
Merged to trunk revision: 1204971
I merged the changed from LUCENE-3583 and uwe's javadoc improvements
into the release branch and kicked off a RC2
I will let you know once it is up.
simon
On Tue, Nov 22, 2011 at 7:42 AM, Shai Erera ser...@gmail.com wrote:
I fixed LUCENE-3583. It was a test issue, so I'm not sure if it's
[
https://issues.apache.org/jira/browse/LUCENE-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155136#comment-13155136
]
Robert Muir commented on LUCENE-3583:
-
Shai: thanks for getting to the bottom of
[
https://issues.apache.org/jira/browse/LUCENE-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-3583:
Fix Version/s: (was: 3.6)
3.5
benchmark tests always fail on
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/1025/
1 tests failed.
REGRESSION:
org.apache.solr.client.solrj.embedded.LargeVolumeJettyTest.testMultiThreaded
Error Message:
java.lang.AssertionError: Some threads threw uncaught exceptions!
Stack Trace:
Choose a specific Directory implementation running the CheckIndex main
--
Key: LUCENE-3586
URL: https://issues.apache.org/jira/browse/LUCENE-3586
Project: Lucene - Java
[
https://issues.apache.org/jira/browse/SOLR-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155174#comment-13155174
]
Luca Cavanna commented on SOLR-566:
---
I would be willing to work on this.
I agree that
[
https://issues.apache.org/jira/browse/SOLR-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher reassigned SOLR-2607:
--
Assignee: Erik Hatcher
Clean up /clients directory
---
[
https://issues.apache.org/jira/browse/LUCENE-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155184#comment-13155184
]
Simon Willnauer commented on LUCENE-3586:
-
I think this makes sense though.
[
https://issues.apache.org/jira/browse/SOLR-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155188#comment-13155188
]
Erik Hatcher commented on SOLR-2607:
I'll take this one... since I'm the culprit
[
https://issues.apache.org/jira/browse/SOLR-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Kats closed SOLR-2910.
---
PingRequest fails if there is no defaultSearchField in the schema.xml
[
https://issues.apache.org/jira/browse/LUCENE-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Cavanna reassigned LUCENE-3586:
Assignee: Luca Cavanna
Choose a specific Directory implementation running the
[
https://issues.apache.org/jira/browse/LUCENE-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155195#comment-13155195
]
Luca Cavanna commented on LUCENE-3586:
--
Cool! Thanks, tomorrow I'll add a patch for
[
https://issues.apache.org/jira/browse/SOLR-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155212#comment-13155212
]
Yury Kats commented on SOLR-2910:
-
q should be *:*
PingRequest fails if
[
https://issues.apache.org/jira/browse/SOLR-2910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155213#comment-13155213
]
Yury Kats commented on SOLR-2910:
-
{noformat}str name=q*:*/str{noformat}
[
https://issues.apache.org/jira/browse/SOLR-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155226#comment-13155226
]
Erik Hatcher commented on SOLR-2607:
I went ahead and took care of this on trunk. svn
[
https://issues.apache.org/jira/browse/SOLR-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-2607.
Resolution: Fixed
Fix Version/s: 4.0
Clean up /clients directory
[
https://issues.apache.org/jira/browse/SOLR-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher reopened SOLR-2607:
going to re-open... we may want to also remove client/ fully? It's nice to
have the pointer to the
[
https://issues.apache.org/jira/browse/LUCENE-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155233#comment-13155233
]
Uwe Schindler commented on LUCENE-3586:
---
Hi Simon, hi Luca,
Maybe we get some
[
https://issues.apache.org/jira/browse/LUCENE-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155235#comment-13155235
]
Uwe Schindler commented on LUCENE-3586:
---
About the issue at all:
we should maybe
[
https://issues.apache.org/jira/browse/LUCENE-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155235#comment-13155235
]
Uwe Schindler edited comment on LUCENE-3586 at 11/22/11 4:33 PM:
Please vote to release the RC2 artifacts at:
http://people.apache.org/~simonw/staging_area/lucene-solr-3.5.0-RC2-rev1204988/
as Lucene 3.5.0 and Solr 3.5.0.
Simon Willnauer
-
To unsubscribe, e-mail:
Mike,
You're right about putting together a higher level discussion. Here are the
road map items I see. I am interested in other have to say.
None of the items I have listed are contigent on the other so they can be
done in parallel or out of order.
1) Complete the release of 2.9.4
2)
[
https://issues.apache.org/jira/browse/SOLR-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155258#comment-13155258
]
Shawn Heisey commented on SOLR-2906:
Something odd happens with the filterCache. When
[
https://issues.apache.org/jira/browse/SOLR-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155267#comment-13155267
]
Yonik Seeley commented on SOLR-2906:
bq. The cache size and the number of inserts don't
Add PythonReusableAnalyzerBase, so we can create analyzers in Python
Key: PYLUCENE-12
URL: https://issues.apache.org/jira/browse/PYLUCENE-12
Project: PyLucene
Issue Type:
[
https://issues.apache.org/jira/browse/PYLUCENE-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated PYLUCENE-12:
---
Attachment: PYLUCENE-12.patch
Patch w/ basic test.
Add
[
https://issues.apache.org/jira/browse/SOLR-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155280#comment-13155280
]
Shawn Heisey commented on SOLR-2906:
The only static warming I have is a *:* search
[
https://issues.apache.org/jira/browse/SOLR-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155280#comment-13155280
]
Shawn Heisey edited comment on SOLR-2906 at 11/22/11 5:32 PM:
--
[
https://issues.apache.org/jira/browse/LUCENE-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155285#comment-13155285
]
Luca Cavanna commented on LUCENE-3586:
--
Hi Uwe, hi all,
you're right, I know
Regarding the short term goals that Scott mentioned, I agree. I think over
the past 9 months that we've been active, it's time we see what we need to
do to graduate from the incubator. Also, 3.0.3 is actually close to a
release, *depending* on how we feel about the Contrib libraries, which I'll
[
https://issues.apache.org/jira/browse/SOLR-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155290#comment-13155290
]
Shawn Heisey commented on SOLR-2906:
I might have figured out the problem, and if I
[
https://issues.apache.org/jira/browse/SOLR-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155291#comment-13155291
]
Mark Johnson commented on SOLR-1301:
Has anyone updated this contrib to work with the
My goal is to release 2.9.4 this month - it looks like we have no -1s from our
dev list so in the next day or so I will put that to the general incubator list.
I'd then like to release 2.9.4g the first or second week of January.
My thoughts would be to try and have 3.0.3 ready by march and 4.0
[
https://issues.apache.org/jira/browse/SOLR-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155296#comment-13155296
]
Shawn Heisey commented on SOLR-2906:
I can't reproduce it with LFUCache or FastLRUCache
[
https://issues.apache.org/jira/browse/SOLR-2438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated SOLR-2438:
-
Attachment: SOLR-2438-3x.patch
Here's what the 3x version would look like if anyone's interested.
I wanted to take some time to discuss our position on the Contrib projects.
Digy and I were a little off topic in the roadmap thread and I brought it
up. Digy mentioned he always felt that it was a nice to have but
not necessarily required for a release. I can't say I disagree.
I had some time
[
https://issues.apache.org/jira/browse/SOLR-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155339#comment-13155339
]
Dawid Weiss commented on SOLR-2888:
---
I would like to commit this in if there are no
+1
My basic Solr testing worked fine.
Erik
On Nov 22, 2011, at 11:43 , Simon Willnauer wrote:
Please vote to release the RC2 artifacts at:
http://people.apache.org/~simonw/staging_area/lucene-solr-3.5.0-RC2-rev1204988/
as Lucene 3.5.0 and Solr 3.5.0.
Simon Willnauer
Add news to website for David and Eric's latest book, AS3ESS
Key: SOLR-2911
URL: https://issues.apache.org/jira/browse/SOLR-2911
Project: Solr
Issue Type: Task
+1
On Tue, Nov 22, 2011 at 11:43 AM, Simon Willnauer
simon.willna...@googlemail.com wrote:
Please vote to release the RC2 artifacts at:
http://people.apache.org/~simonw/staging_area/lucene-solr-3.5.0-RC2-rev1204988/
as Lucene 3.5.0 and Solr 3.5.0.
Simon Willnauer
+1
Mike McCandless
http://blog.mikemccandless.com
On Tue, Nov 22, 2011 at 11:43 AM, Simon Willnauer
simon.willna...@googlemail.com wrote:
Please vote to release the RC2 artifacts at:
http://people.apache.org/~simonw/staging_area/lucene-solr-3.5.0-RC2-rev1204988/
as Lucene 3.5.0 and Solr
[
https://issues.apache.org/jira/browse/SOLR-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steffen Elberg Godskesen updated SOLR-2509:
---
Attachment: SOLR-2509.patch
This patch passes James' new unit tests, but
This one should have also been in 3.5 to work around the SIGSEGVs. But with
Mike's patch checking that IndexReaders are open, this should be not so
important.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
[
https://issues.apache.org/jira/browse/LUCENE-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155404#comment-13155404
]
Uwe Schindler commented on LUCENE-3200:
---
MMapDirectory missed a explicit nulling of
:
http://people.apache.org/~simonw/staging_area/lucene-solr-3.5.0-RC2-rev1204988/
+0
Two things jumped out at me as being bad, but i'm not certain if either
warrant a re-spin...
1) in the src builds, attempts at building javadocs result in an ant
failure because of a warning that it
On Tue, Nov 22, 2011 at 4:04 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
:
http://people.apache.org/~simonw/staging_area/lucene-solr-3.5.0-RC2-rev1204988/
+0
Two things jumped out at me as being bad, but i'm not certain if either
warrant a re-spin...
1) in the src builds,
[
https://issues.apache.org/jira/browse/SOLR-2911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-2911:
---
Attachment: as3ess_book.jpg
solr_website.patch
FYI the attached image goes in:
2) if you build lucene or solr from source, the version in the artifact
names are 3.5-SNAPSHOT ... last time i checked, a release named 3.5
would have it's build.xml such that building from source w/o explicitly
setting the version props would result in 3.6-SNAPSHOT (or
3.5.1-SNAPSHOT) so it
: Lucene: The last time this was done was with the 2.1.0 release. From
...
: Solr: Prior to the Lucene-Solr development merge, Solr always did the
...
Cool ... so I just haven't been paying attention and this is expected.
thanks.
-Hoss
Attempting to link to Java SE JavaDocs is competely unreliable
--
Key: LUCENE-3587
URL: https://issues.apache.org/jira/browse/LUCENE-3587
Project: Lucene - Java
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LUCENE-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-3587:
-
Attachment: LUCENE-3587.trunk.patch
Patch against trunk demonstrating the change i suggest we make (to
[
https://issues.apache.org/jira/browse/LUCENE-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-3587:
-
Attachment: LUCENE-3587.3x.patch
equivalent patch for the 3x (and 3.5) branches.
: Agreed -- we shouldn't / can't ship a package-list from Oracle, but we
: should change the hardcoded javadoc.link value in common-build.xml to
: (ie: the empty string) ... that causes the build to succeed completely --
: if users want happy/shiny/pretty links to java.lang.* classes then
On Tue, Nov 22, 2011 at 7:08 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
...I think we should not only commit them to trunk 3x but also
the 3.5 branch and spin an RC3. It would look really silly to release
3.5 RC2 with a hardcoded URL in the build.xml that 404s and fails the build.
Try harder to prevent SIGSEGV on cloned MMapIndexInputs
---
Key: LUCENE-3588
URL: https://issues.apache.org/jira/browse/LUCENE-3588
Project: Lucene - Java
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/LUCENE-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3588:
--
Attachment: LUCENE-3588.patch
Try harder to prevent SIGSEGV on cloned MMapIndexInputs
[
https://issues.apache.org/jira/browse/LUCENE-3588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-3588:
Attachment: LUCENE-3588.patch
+1, i added a simple test, sigsegv's without patch, passes with it.
: If the fact that javadocs fails because Oracle removed the
: package-list for java5 javadocs is a blocker,
:
: then on RC3 should i vote -1 because the tests often completely hang
: on java5 due to JVM concurrency bugs?
a) API Compatibility has nothing to do with which JVM you choose to try
On Tue, Nov 22, 2011 at 8:22 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
I mean seriously ... WTF is the point of a release that we know is broken
for all users? the main reason we even have an RC2 is because one test
(in a contrib!) would fail on some OS's -- if that's worth making
[
https://issues.apache.org/jira/browse/LUCENE-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155622#comment-13155622
]
Robert Muir commented on LUCENE-3587:
-
+1 to the patch (i think its the best
: But I'm just pointing out that with bugs like the javadocs thing,
: its not really a lucene bug. Likely its a transient issue with
: oracle's configuration... does that mean all of our past releases are
: broken too Because, ant javadocs won't work there either.
Those releases are already
[
https://issues.apache.org/jira/browse/LUCENE-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155634#comment-13155634
]
Steven Rowe commented on LUCENE-3587:
-
I think we should just stop failing the build
On Tue, Nov 22, 2011 at 9:21 PM, Chris Hostetter
hossman_luc...@fucit.org wrote:
(Remember: fail on warning is not a feature of javadoc, or the
javadoc/ nat target -- it's something special we do in our build.xml.
It's sometihng that in general i think is a very good idea, and i don't
suggest
Build: https://builds.apache.org/job/Lucene-trunk/1743/
No tests ran.
Build Log (for compile errors):
[...truncated 8603 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail:
[
https://issues.apache.org/jira/browse/LUCENE-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-3587:
Attachment: LUCENE-3587.keep-javadoc-link.3x.patch
Attempting to link to Java SE JavaDocs is
[
https://issues.apache.org/jira/browse/LUCENE-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-3587:
Attachment: LUCENE-3587.keep-javadoc-link.trunk.patch
Trunk branch_3x versions of patch to
[
https://issues.apache.org/jira/browse/SOLR-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13155693#comment-13155693
]
Lance Norskog commented on SOLR-2358:
-
Lamport Clocks are a time-tested way to sequence
90 matches
Mail list logo