[
https://issues.apache.org/jira/browse/LUCENE-4828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601556#comment-13601556
]
Yonik Seeley commented on LUCENE-4828:
--
For highlighting, I've heard it argued both
[
https://issues.apache.org/jira/browse/LUCENE-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-4816.
Resolution: Fixed
Fix Version/s: 4.3
5.0
[
https://issues.apache.org/jira/browse/LUCENE-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601578#comment-13601578
]
Commit Tag Bot commented on LUCENE-4816:
[trunk commit] Michael McCandless
[
https://issues.apache.org/jira/browse/SOLR-4536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tricia Jenkins updated SOLR-4536:
-
Attachment: SOLR-4536.patch
I think I see what's happening now. As the comment in TestHarness
[
https://issues.apache.org/jira/browse/LUCENE-4816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601593#comment-13601593
]
Commit Tag Bot commented on LUCENE-4816:
[branch_4x commit] Michael McCandless
Thanks, we'll see what I can see. The weird bit Is I was looking at the
normal output and it's almost like the location of the index changes part
way through. The fail is on:
I'd say it's something in the Solr test code (like Uwe mentioned), not
in the test framework. If you have a repeatable
Ariel Lieberman created SOLR-4572:
-
Summary: Mistake in the comment in source
...surround.parser.QueryParser.jj
Key: SOLR-4572
URL: https://issues.apache.org/jira/browse/SOLR-4572
Project: Solr
Phil John created SOLR-4573:
---
Summary: oejh.HttpGenerator:Ignoring extra content when accessing
Solr HTTP Admin Console in Solr Cloud example
Key: SOLR-4573
URL: https://issues.apache.org/jira/browse/SOLR-4573
The following two commits (one for trunk, one for 4.x) changed a bunch
of properties. I rely on the one named solr.core.name for my config,
so when I upgraded from 4.2-SNAPSHOT to 4.3-SNAPSHOT, Solr wouldn't
start my cores.
http://svn.apache.org/r1451797
http://svn.apache.org/r1454477
I
[
https://issues.apache.org/jira/browse/SOLR-4573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601654#comment-13601654
]
Mark Miller commented on SOLR-4573:
---
I'm seeing this as well - I have not had a chance to
[
https://issues.apache.org/jira/browse/SOLR-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601674#comment-13601674
]
Patanachai Tangchaisin commented on SOLR-4186:
--
I also got this problem.
In my
[
https://issues.apache.org/jira/browse/SOLR-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601675#comment-13601675
]
John Wooden commented on SOLR-3030:
---
Thanks for pointing this out. We've now switched to
Mark Miller created SOLR-4574:
-
Summary: Both the CoreAdmin and Collections API will silently
return success on an unknown ACTION paramater.
Key: SOLR-4574
URL: https://issues.apache.org/jira/browse/SOLR-4574
Erick Erickson created SOLR-4575:
Summary: SOLR-4196 made defining solr.core.name as a system prop
(and others) fail.
Key: SOLR-4575
URL: https://issues.apache.org/jira/browse/SOLR-4575
Project: Solr
Hmmm, this is certainly stuff that I changed. The problem is that when we
make a properties file in a core (where you are already reading something
from the core directory), then it's equally silly to require that the
core.properties file contain
solr.core.name=mycollection
for instance.
See
[
https://issues.apache.org/jira/browse/SOLR-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-4574:
--
Summary: The Collections API will silently return success on an unknown
ACTION parameter. (was: Both
[
https://issues.apache.org/jira/browse/SOLR-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-4574:
--
Attachment: SOLR-4574.patch
Easier said then done on changing the CoreAdmin logic - I've left it and
I took a quick look and my first question would be *why this test even
passes* if it throws exceptions internally and clearly cannot clean up
after itself:
[junit4:junit4] 2 WARNING: best effort to remove
Mark Miller created SOLR-4576:
-
Summary: Collections API validation errors should cause an
exception on clients and otherwise act as validation errors with the Core Admin
API.
Key: SOLR-4576
URL:
[
https://issues.apache.org/jira/browse/SOLR-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601742#comment-13601742
]
Mark Miller commented on SOLR-4494:
---
I'm using this as a master issue - I'll create sub
[
https://issues.apache.org/jira/browse/SOLR-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-4494:
--
Fix Version/s: 5.0
Clean up and polish Collections API
---
[
https://issues.apache.org/jira/browse/SOLR-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601746#comment-13601746
]
Mark Miller commented on SOLR-4576:
---
Currently, you don't even get anything in the
[
https://issues.apache.org/jira/browse/SOLR-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-4575:
---
Attachment: SOLR-4575.patch
Patch restoring old behavior with the current code lines commented out.
[
https://issues.apache.org/jira/browse/SOLR-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-4576:
--
Attachment: SOLR-4576.patch
Here is a first pass at fixing this.
Collections API
[
https://issues.apache.org/jira/browse/SOLR-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-4576:
--
Issue Type: Bug (was: Improvement)
Collections API validation errors should cause an exception on
[
https://issues.apache.org/jira/browse/SOLR-4567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-4567:
-
Description:
Alexandre Rafalovitch reported on the solr-user mailing list
[
https://issues.apache.org/jira/browse/SOLR-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601793#comment-13601793
]
Shawn Heisey commented on SOLR-4547:
Patch does apply cleanly to trunk, the CHANGES.txt
Adrien Grand created LUCENE-4830:
Summary: Sorter API: use an abstract doc map instead of an array
Key: LUCENE-4830
URL: https://issues.apache.org/jira/browse/LUCENE-4830
Project: Lucene - Core
[
https://issues.apache.org/jira/browse/SOLR-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601803#comment-13601803
]
Shawn Heisey commented on SOLR-4575:
Patch didn't work. For those following along, the
[
https://issues.apache.org/jira/browse/SOLR-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601803#comment-13601803
]
Shawn Heisey edited comment on SOLR-4575 at 3/13/13 11:30 PM:
--
[
https://issues.apache.org/jira/browse/LUCENE-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated LUCENE-4830:
-
Attachment: LUCENE-4830.patch
Patch. I also changed SortingAtomicReader.liveDocs() to be a view
[
https://issues.apache.org/jira/browse/SOLR-4567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601873#comment-13601873
]
Commit Tag Bot commented on SOLR-4567:
--
[trunk commit] Steven Rowe
[
https://issues.apache.org/jira/browse/SOLR-4567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601885#comment-13601885
]
Commit Tag Bot commented on SOLR-4567:
--
[branch_4x commit] Steven Rowe
[
https://issues.apache.org/jira/browse/SOLR-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated SOLR-4575:
-
Attachment: SOLR-4575.patch
Preliminary patch. At least it assigns the correct value in the
Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/799/
4 tests failed.
REGRESSION: org.apache.solr.cloud.BasicDistributedZk2Test.testDistribSearch
Error Message:
No registered leader was found, collection:collection1 slice:shard1
Stack Trace:
org.apache.solr.common.SolrException: No
[
https://issues.apache.org/jira/browse/SOLR-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson updated SOLR-4575:
-
Attachment: SOLR-4575.patch
Final (I hope) patch with tests. Lots of very important implicit
Mark Miller created SOLR-4577:
-
Summary: The collections API should return responses (sucess or
failure) for each node it attempts to work with.
Key: SOLR-4577
URL: https://issues.apache.org/jira/browse/SOLR-4577
[
https://issues.apache.org/jira/browse/SOLR-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601974#comment-13601974
]
Mark Miller commented on SOLR-4575:
---
We might want to consider letting this change wait
Mark Miller created SOLR-4578:
-
Summary: CoreAdminHandler#handleCreateAction gets a SolrCore and
does not close it in SolrCloud mode.
Key: SOLR-4578
URL: https://issues.apache.org/jira/browse/SOLR-4578
[
https://issues.apache.org/jira/browse/SOLR-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13601994#comment-13601994
]
Mark Miller commented on SOLR-4578:
---
Should be
{code}
if
[
https://issues.apache.org/jira/browse/SOLR-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-4578:
--
Component/s: SolrCloud
Fix Version/s: 5.0
4.3
Assignee: Mark Miller
[
https://issues.apache.org/jira/browse/SOLR-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-4297:
Attachment: SOLR-4297.patch
Test and fix.
Atomic update including
albert newbgirl created SOLR-4579:
-
Summary: A replicas lost 10 sequential documents, and we can't
search these documents from this replicas forever
Key: SOLR-4579
URL:
[
https://issues.apache.org/jira/browse/SOLR-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602013#comment-13602013
]
albert newbgirl commented on SOLR-4579:
---
There is some exception in the leader logļ¼
[
https://issues.apache.org/jira/browse/SOLR-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602014#comment-13602014
]
albert newbgirl commented on SOLR-4579:
---
Oh, some log on the replicas at the same
[
https://issues.apache.org/jira/browse/SOLR-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602031#comment-13602031
]
Commit Tag Bot commented on SOLR-4297:
--
[trunk commit] Shalin Shekhar Mangar
[
https://issues.apache.org/jira/browse/SOLR-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar resolved SOLR-4297.
-
Resolution: Fixed
Fix Version/s: 5.0
4.3
Fixed in
[
https://issues.apache.org/jira/browse/SOLR-4297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602038#comment-13602038
]
Commit Tag Bot commented on SOLR-4297:
--
[branch_4x commit] Shalin Shekhar Mangar
[
https://issues.apache.org/jira/browse/LUCENE-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602063#comment-13602063
]
Shai Erera commented on LUCENE-4795:
bq. At search time they make two
101 - 149 of 149 matches
Mail list logo
