[
https://issues.apache.org/jira/browse/SOLR-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847923#action_12847923
]
Andrzej Bialecki commented on SOLR-1837:
-
Re: bugs in Luke that result in missing
[
https://issues.apache.org/jira/browse/SOLR-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847936#action_12847936
]
Trey Grainger commented on SOLR-1837:
-
Re: bugs in Luke that result in missing terms - I
[
https://issues.apache.org/jira/browse/SOLR-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trey Grainger updated SOLR-1837:
Attachment: SOLR-1837.patch
Here's what I have thusfar. Only bug I currently know about is that
[
https://issues.apache.org/jira/browse/SOLR-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-1797:
---
Attachment: SOLR-1797.patch
Patch attached:
- makes lists synchronized for thread safety
- adds an
[
https://issues.apache.org/jira/browse/SOLR-1797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved SOLR-1797.
Resolution: Fixed
Fix Version/s: 1.5
Committed to newtrunk, and merged back to trunk.
I was
I work with Maven all the time, and recent Solr releases too. It would be
very useful if Solr SNAPSHOTs could get deployed to
https://repository.apache.org/index.html on an automated basis. Is anyone
opposed to this, and if not, could someone set this up? It would be really
sweet if it were
I don't see a compelling reason to go to 3.1. It is going to be very
confusing for users (when did 3.0 come out? Did I miss it?) At least
when MS Word jumped from 2.0 to 6.0 it wasn't to a minor version (i.e.
6.1). 2.0 seems reasonable, as does 1.5. Although 2.0 would be a good
