+1. We are probably already breaching this with 256 shards, something we
are still investigating.
On the question of other limits, there's also the limit on how many threads
your OS can support, we have in the past hit 65k threads and errored out
because of 64 shards per machine, not sure as yet
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-Windows/3716/
Java: 32bit/jdk1.6.0_45 -client -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED:
org.apache.solr.client.solrj.impl.BasicHttpSolrServerTest.testConnectionRefused
Error Message:
Stack Trace:
java.lang.AssertionError
at
abipc created SOLR-5743:
---
Summary: Faceting with BlockJoin support
Key: SOLR-5743
URL: https://issues.apache.org/jira/browse/SOLR-5743
Project: Solr
Issue Type: New Feature
Reporter: abipc
[
https://issues.apache.org/jira/browse/SOLR-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
abipc updated SOLR-5743:
Labels: features (was: )
Faceting with BlockJoin support
---
Key:
[
https://issues.apache.org/jira/browse/SOLR-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
abipc updated SOLR-5743:
Description:
For a sample inventory(note - nested documents) like this -
doc
field name=id10/field
field
[
https://issues.apache.org/jira/browse/SOLR-5743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
abipc updated SOLR-5743:
Description:
For a sample inventory like this -
doc
field name=id10/field
field name=type_sparent/field
field
Folks,
I created a release branch for 4.7
https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_4_7
Please backport stuff that should go into the branch until tomorrow
noon CEST. I'd appreciate if large changes could wait until 4.8 to
not unnecessarily destabilize 4.8. I will build an
before anybody jumps the gun - I am working on updateing the branch_4x
version wise (uwe take it easy one thing a time :)
On Tue, Feb 18, 2014 at 11:50 AM, Simon Willnauer
simon.willna...@gmail.com wrote:
Folks,
I created a release branch for 4.7
[
https://issues.apache.org/jira/browse/SOLR-2908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar reassigned SOLR-2908:
---
Assignee: Shalin Shekhar Mangar
To push the terms.limit parameter from the
[
https://issues.apache.org/jira/browse/SOLR-2908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13903956#comment-13903956
]
Shalin Shekhar Mangar commented on SOLR-2908:
-
Perhaps incorrect counts are
[
https://issues.apache.org/jira/browse/LUCENE-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13903971#comment-13903971
]
Michael McCandless commented on LUCENE-5449:
+1
Two ancient classes renamed
[
https://issues.apache.org/jira/browse/LUCENE-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13903983#comment-13903983
]
Benson Margulies commented on LUCENE-5449:
--
[~thetaphi], I am not enthusiastic
Hi
I tried to understand how do I merge changes that involve code refactoring,
e.g. class rename, from github to our SVN. I had such a need, but I also
thought about this issue, now that we accept PRs. So the scenario is this:
- In your git clone, you rename class Foo to Bar
- In order to commit
On Tue, Feb 18, 2014 at 1:18 PM, Shai Erera ser...@gmail.com wrote:
Second, has anyone perhaps found a way to overcome that issue? I thought
about maybe writing a script to detect that, looking at the patch file, but
it seems hard to detect that the deleted Foo is the new Bar. If it's just
hey folks,
I try to build an RC to checkout if everything goes alright and I now
spend 4 hours already without luck. The release script runs the solr
tests but they never pass. I tried it 6 times now and each time a
different test breaks. I am going to disable the solr test run in the
release
Well, git-svn has a heap of warnings against using it for merges; it's
also a really bad idea when renaming a whole package, as it does it
one-file-at-a-time.
If you have a workflow that works with the ASF mirror and svn, please
write it up on the Wiki!
On Tue, Feb 18, 2014 at 7:23 AM, Thomas
Github pull requests can be treated as individual cherry picked patch sets
really, not branch merges ? (ie rebased) from there on out you're in svn
land. No need to merge.
But indeed, it tries to detect it based on the file content, and doesn't
work 100% as manual svn moves.
On Tue, Feb 18,
Thomas, please help us comparative git ignoramuses, and detail the
sequence of commands you would use with git-svn to apply a PR,
starting from your fork/clone setup.
On Tue, Feb 18, 2014 at 7:31 AM, Thomas Matthijs li...@selckin.be wrote:
Github pull requests can be treated as individual cherry
The problem I see is that if you generate a patch using 'git diff', it
applies just fine to svn (if you generate it w/ --no-prefix) without any
warnings about missing files due the rename. Wanted to warn the community
about it, so that when committers assign themselves to PRs, they review the
[
https://issues.apache.org/jira/browse/LUCENE-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904002#comment-13904002
]
Uwe Schindler commented on LUCENE-5449:
---
Hi Beson, my comment was *for the future*.
[
https://issues.apache.org/jira/browse/LUCENE-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904003#comment-13904003
]
Michael McCandless commented on LUCENE-5449:
I think even if we switch to
[
https://issues.apache.org/jira/browse/LUCENE-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904004#comment-13904004
]
Benson Margulies commented on LUCENE-5449:
--
OK, then this is good to go. (I did
[
https://issues.apache.org/jira/browse/LUCENE-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904007#comment-13904007
]
Uwe Schindler commented on LUCENE-5449:
---
+1 to commit. I hope you get the file
[
https://issues.apache.org/jira/browse/LUCENE-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904010#comment-13904010
]
Greg Visotski commented on LUCENE-5000:
---
Hi Karl, I picked up your patch and have
Weird. The smoke script has always had solr tests disabled. Who enabled it?
Those fails in general have JIRA issues as far as I remember.
- Mark
On Feb 18, 2014, at 7:24 AM, Simon Willnauer simon.willna...@gmail.com
wrote:
hey folks,
I try to build an RC to checkout if everything
[
https://issues.apache.org/jira/browse/SOLR-5720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-5720:
-
Attachment: SOLR-5720.patch
New patch, handles the zero result case and added tests for zero
I tried using git apply on a patch (from github's .patch URL) that
included a rename. no sign of a rename; just a delete and an add. I
feel like I'm missing something.
On Tue, Feb 18, 2014 at 7:36 AM, Shai Erera ser...@gmail.com wrote:
The problem I see is that if you generate a patch using
Git does not track renames, but can show/detect it, the magic options are
-C and -M for diff/show etc
On Tue, Feb 18, 2014 at 2:16 PM, Benson Margulies bimargul...@gmail.comwrote:
I tried using git apply on a patch (from github's .patch URL) that
included a rename. no sign of a rename; just
Let me be specific. If I am sitting in a git clone that has been set
up with git svn, and I use git apply to apply the output of git
format-patch, if I dcommit, is the autodetection going to result in an
svn mv?
On Tue, Feb 18, 2014 at 8:20 AM, Thomas Matthijs li...@selckin.be wrote:
Git does
Hi Beson,
The problem is that by this approach the rename gets a delete and add with full
file content, versus a native SVN rename (which is a svn cp followed by a
delete of the original file). By this the history is lost, because for SVN you
patch looks like a complete removal of the original
Oh sorry, you were in GIT world. My response does not apply for you :-)
Regards,
Uwe
(GIT ignorant)
-
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,
On Tue, Feb 18, 2014 at 8:24 AM, Uwe Schindler u...@thetaphi.de wrote:
Hi Beson,
The problem is that by this approach the rename gets a delete and add with
full file content, versus a native SVN rename (which is a svn cp followed by
a delete of the original file). By this the history is
it is not the smoke test - I ran this:
python3.2 -u buildAndPushRelease.py -prepare -push simonw -sign
ECA39416 /home/simon/work/projects/lucene/lucene_solr_4_7/ 4.7.0 0
compared to this:
python3.2 -u buildAndPushRelease.py -prepare -push simonw -sign
ECA39416 -smoke
[
https://issues.apache.org/jira/browse/SOLR-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904036#comment-13904036
]
Raúl Grande commented on SOLR-4479:
---
Hi,
We have the same problem using SolrCloud v.
Because we run those tests locally and see the results on Jenkins and have an
understanding what the issues are. Perhaps you don't, but the Solr people do.
That's how we can release.
That script shouldn't run the solr tests.
- Mark
On Feb 18, 2014, at 8:28 AM, Simon Willnauer
Hmm I am not sure if I understand that rational. Anyway wouldn't it be
better to @Ignore the tests and re-enable once they are fixed? I just
wonder how I can tell if I broke something in solr while working on
lucene and I am supposed to ignore failing tests?
simon
On Tue, Feb 18, 2014 at 2:36
[
https://issues.apache.org/jira/browse/SOLR-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904053#comment-13904053
]
Stanislav Sandalnikov commented on SOLR-4479:
-
Hi Raul,
In our case this was
[
https://issues.apache.org/jira/browse/SOLR-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904063#comment-13904063
]
Steve Rowe commented on SOLR-5709:
--
Rob,
I see what you mean: ngroups should be the same
Unfortunately i can't find a way to make it explicitly show it will do a
svn rename, but it does do it, so that makes this solution not very useful
either i guess.
--- git ---
[master svntest] % git status
On branch master
Changes to be committed:
(use git reset HEAD file... to unstage)
[
https://issues.apache.org/jira/browse/SOLR-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-5609:
-
Attachment: SOLR-5609_5130.patch
more testcases
re-enabled the DeleteInactiveReplica test which was
[
https://issues.apache.org/jira/browse/SOLR-4479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904079#comment-13904079
]
Raúl Grande commented on SOLR-4479:
---
Thanks a lot!
It worked fine with that param!
Welcome Anshum!
-Yonik
http://heliosearch.org - native off-heap filters and fieldcache for solr
On Sun, Feb 16, 2014 at 10:14 PM, Anshum Gupta ans...@anshumgupta.net wrote:
Thanks Mark.
I spent most of my life in New Delhi, India other than short stints in
different parts of the country
FYI,
I build a RC from revision 1569289 and you can download it here [1] to
run / test it use the smoke tester here [2] I also added a 4_7 only
build to my jenkins to run tests on the release branch [3]
[1]
http://people.apache.org/~simonw/staging_area/lucene-solr-4.7.0-RC0-rev1569289/
[2]
Looks fixed now...
-Yonik
http://heliosearch.org - native off-heap filters and fieldcache for solr
On Mon, Feb 17, 2014 at 10:37 AM, Mark Miller markrmil...@gmail.com wrote:
Yup, something seems wrong. Supposed to be fast mirroring. We probably have
to reach out to infra if we want to know
Yes, sorry forgot to update. I opened an issue for INFRA and they fixed it.
Our mirror was locked because of a failed update or something.
This is something we should be aware and monitor from time to time...
Shai
On Tue, Feb 18, 2014 at 4:49 PM, Yonik Seeley yo...@heliosearch.com wrote:
Thanks Simon.
On 2/17/14, 4:50 AM, Simon Willnauer simon.willna...@gmail.com wrote:
just put this annotation at the class level:
@SuppressCodecs(Lucene3x)
simon
On Mon, Feb 17, 2014 at 4:56 AM, Smiley, David W. dsmi...@mitre.org
wrote:
I wrote a test that requires DocValues. It failed on me
Build: https://builds.apache.org/job/Lucene-Solr-Maven-4.x/593/
2 tests failed.
REGRESSION: org.apache.solr.cloud.BasicDistributedZk2Test.testDistribSearch
Error Message:
No live SolrServers available to handle this
request:[https://127.0.0.1:18844/collection1,
Günther Ruck created SOLR-5744:
--
Summary: Solrj configuerd with BinaryRequestWriter throws
NullpointerException if LangDetectLanguageIdentifierUpdateProcessorFactory is
configuerd
Key: SOLR-5744
URL:
: just put this annotation at the class level:
:
: @SuppressCodecs(Lucene3x)
Be aware of subtleties though... Just because a codec supports docvalues
doesn't mean it supports *all* of the docvalue features you need.
Example: the cursor tests failed in extremeley weird non-reproducible ways
Depends on your situation. For me, I can run the tests and have them pass 6
times in a row. It it was otherwise, I would fix the issue, as I have for years
now.
When I see a test failing commonly for another dev, I’ll also often jump in and
help fix the issue. As I have for years now.
I’ll
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-Linux/9410/
Java: 32bit/jdk1.7.0_60-ea-b04 -client -XX:+UseParallelGC
All tests passed
Build Log:
[...truncated 28008 lines...]
BUILD FAILED
/mnt/ssd/jenkins/workspace/Lucene-Solr-4.x-Linux/build.xml:459: The following
error occurred while
Fail is:
/mnt/ssd/jenkins/workspace/Lucene-Solr-4.x-Linux/solr/build.xml:240: Some
example solrconfig.xml files do not refer to the correct luceneMatchVersion: 4.8
- Mark
http://about.me/markrmiller
On Feb 18, 2014, at 12:00 PM, Policeman Jenkins Server jenk...@thetaphi.de
wrote:
Build:
I committed a fix for this - sorry for the noise here!
On Tue, Feb 18, 2014 at 6:04 PM, Mark Miller markrmil...@gmail.com wrote:
Fail is:
/mnt/ssd/jenkins/workspace/Lucene-Solr-4.x-Linux/solr/build.xml:240: Some
example solrconfig.xml files do not refer to the correct luceneMatchVersion:
[
https://issues.apache.org/jira/browse/SOLR-5727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-5727.
---
Resolution: Fixed
This has worked out nicely so far. If someone wants to do a closer review of
the
I may end up turning off SSL for these tests for a while. Until I have some
time to go in and figure out where the slowness is screwing the test.
- Mark
http://about.me/markrmiller
On Feb 18, 2014, at 9:59 AM, Apache Jenkins Server jenk...@builds.apache.org
wrote:
Build:
[
https://issues.apache.org/jira/browse/SOLR-5709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904280#comment-13904280
]
Rob Tulloh commented on SOLR-5709:
--
Thanks for reminding to look back at the
[
https://issues.apache.org/jira/browse/SOLR-5609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-5609:
-
Attachment: SOLR-5609_5130.patch
OverseerCollectionProcessorTest was failing
Don't let cores create
I turned off SSL for BasicDistributedZk2Test for now.
- Mark
On Feb 18, 2014, at 12:17 PM, Mark Miller markrmil...@gmail.com wrote:
I may end up turning off SSL for these tests for a while. Until I have some
time to go in and figure out where the slowness is screwing the test.
- Mark
I agree ignoring tests isn't a good idea, but someone from outside should be
able to determine if a failing test is critical or not. Maybe the solution
would be to keep running them, but have the failure message specify the Jira
entry associated with it. Then whoever runs the test, to build RC
Tim Allison created LUCENE-5450:
---
Summary: NPE and Illegal Argument Exception in wrapped
SpanMultiTerms with no matches
Key: LUCENE-5450
URL: https://issues.apache.org/jira/browse/LUCENE-5450
Project:
[
https://issues.apache.org/jira/browse/LUCENE-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated LUCENE-5450:
Attachment: LUCENE-5450.patch
Test case and v1 of patch attached.
NPE and Illegal Argument
Once I have transported a change from branch to branch via diff\apply, git
stops discussing a rename at all.
On February 18, 2014 9:06:30 AM EST, Thomas Matthijs li...@selckin.be wrote:
Unfortunately i can't find a way to make it explicitly show it will do
a
svn rename, but it does do it, so
[
https://issues.apache.org/jira/browse/LUCENE-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904399#comment-13904399
]
Tim Allison commented on LUCENE-1486:
-
Attached update with tests from
[
https://issues.apache.org/jira/browse/LUCENE-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated LUCENE-5205:
Attachment: LUCENE-5205.patch.gz
Thanks to [~iorixxx]'s recommendation, I added tests from
I'd like to see some sort of dashboard that would make clear at a
glance when something goes from failing rarely to failing frequently.
Anyone know how to get this reporting out of Jenkins?
-Yonik
http://heliosearch.org - native off-heap filters and fieldcache for solr
On Tue, Feb 18, 2014 at
On Feb 18, 2014, at 1:16 PM, Steve Molloy smol...@opentext.com wrote:
Maybe the solution would be to keep running them, but have the failure
message specify the Jira entry associated with it.
Yeah, it’s not a bad idea for long running issues.
Your not necessarily running into long running
huge +1 to marking it - I dont' like to ignore failing tests but it's
hard to tell if you are not close to it!
On Tue, Feb 18, 2014 at 7:16 PM, Steve Molloy smol...@opentext.com wrote:
I agree ignoring tests isn't a good idea, but someone from outside should be
able to determine if a failing
[
https://issues.apache.org/jira/browse/LUCENE-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904405#comment-13904405
]
Robert Muir commented on LUCENE-5450:
-
Hi Tim, thanks for reporting the bug.
[
https://issues.apache.org/jira/browse/LUCENE-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-5450:
Attachment: LUCENE-5450.patch
Here's what i was thinking (your tests and existing tests seem to
[
https://issues.apache.org/jira/browse/LUCENE-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904424#comment-13904424
]
Tim Allison commented on LUCENE-5450:
-
Looks great. Much simpler. Thank you!
NPE
David Smiley created LUCENE-5451:
Summary: Update Spatial4j to 0.4.1
Key: LUCENE-5451
URL: https://issues.apache.org/jira/browse/LUCENE-5451
Project: Lucene - Core
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LUCENE-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904442#comment-13904442
]
ASF subversion and git services commented on LUCENE-5438:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904449#comment-13904449
]
ASF subversion and git services commented on LUCENE-5438:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904456#comment-13904456
]
Michael McCandless commented on LUCENE-5450:
+1
NPE and Illegal Argument
[
https://issues.apache.org/jira/browse/LUCENE-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904469#comment-13904469
]
ASF subversion and git services commented on LUCENE-5450:
-
Commit
Colin Bartolome created SOLR-5745:
-
Summary: Add an UpdateRequest parameter that lets request wait
until no searchers are warming before committing
Key: SOLR-5745
URL:
[
https://issues.apache.org/jira/browse/LUCENE-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904506#comment-13904506
]
ASF subversion and git services commented on LUCENE-5450:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-5450.
-
Resolution: Fixed
Fix Version/s: 5.0
4.8
Thanks Tim!
NPE and
[
https://issues.apache.org/jira/browse/SOLR-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Lucey updated SOLR-2894:
--
Attachment: SOLR-2894.patch
This is the updated version of our implementation of Pivot Facets, as
Nik Everett created LUCENE-5452:
---
Summary: Combine matches from multiple fields into one with the
postings highlighter
Key: LUCENE-5452
URL: https://issues.apache.org/jira/browse/LUCENE-5452
Project:
[
https://issues.apache.org/jira/browse/LUCENE-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904559#comment-13904559
]
Robert Muir commented on LUCENE-5452:
-
Hi Nik, is there an advantage with the current
[
https://issues.apache.org/jira/browse/SOLR-5720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joel Bernstein updated SOLR-5720:
-
Attachment: SOLR-5720.patch
New patch using fieldType.indexedToReadable(bytesRef, charsRef) when
[
https://issues.apache.org/jira/browse/LUCENE-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904569#comment-13904569
]
David Smiley commented on LUCENE-5205:
--
FWIW my concern with any new query parser,
[
https://issues.apache.org/jira/browse/LUCENE-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904610#comment-13904610
]
Nik Everett commented on LUCENE-5452:
-
I hadn't really thought of doing it a level
[
https://issues.apache.org/jira/browse/LUCENE-5451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904638#comment-13904638
]
David Smiley commented on LUCENE-5451:
--
I'd just like to take a moment to clarify
[
https://issues.apache.org/jira/browse/LUCENE-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904675#comment-13904675
]
Robert Muir commented on LUCENE-5452:
-
Cool, maybe we can actually optimize the
Robert Muir created LUCENE-5453:
---
Summary: some trivial refactoring to postingshighlighter
Key: LUCENE-5453
URL: https://issues.apache.org/jira/browse/LUCENE-5453
Project: Lucene - Core
Issue
[
https://issues.apache.org/jira/browse/LUCENE-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-5453:
Attachment: LUCENE-5453.patch
simple patch
some trivial refactoring to postingshighlighter
[
https://issues.apache.org/jira/browse/SOLR-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-4470:
--
Fix Version/s: (was: 4.7)
5.0
Support for basic http auth in internal solr
Would someone have a few minutes to validate this race condition fix?
Thanks!
-- Forwarded message --
From: Ramkumar Aiyengar (JIRA) j...@apache.org
Date: 8 Jan 2014 16:49
Subject: [jira] [Created] (SOLR-5620) Race condition while setting
ZkStateReader.aliases
To:
Hoss Man created SOLR-5746:
--
Summary: solr.xml parsing of str vs int vs bool is brittle;
fails silently; expects odd type for shareSchema
Key: SOLR-5746
URL: https://issues.apache.org/jira/browse/SOLR-5746
[
https://issues.apache.org/jira/browse/SOLR-5746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904881#comment-13904881
]
Hoss Man commented on SOLR-5746:
I think what we should do is...
* change the parsing
[
https://issues.apache.org/jira/browse/LUCENE-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated LUCENE-5447:
---
Attachment: LUCENE-5447.patch
Patch fixing the issue; includes LUCENE-5447-test.patch.
Committing
[
https://issues.apache.org/jira/browse/LUCENE-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated LUCENE-5447:
---
Fix Version/s: 5.0
4.7
StandardTokenizer should break at consecutive chars
[
https://issues.apache.org/jira/browse/LUCENE-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated LUCENE-5447:
---
Attachment: LUCENE-5447.patch
Final patch, adding a test for UAX29URLEmailTokenizer and a
[
https://issues.apache.org/jira/browse/LUCENE-5447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904947#comment-13904947
]
ASF subversion and git services commented on LUCENE-5447:
-
Commit
[
https://issues.apache.org/jira/browse/SOLR-5620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned SOLR-5620:
-
Assignee: Mark Miller
Race condition while setting ZkStateReader.aliases
[
https://issues.apache.org/jira/browse/LUCENE-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904971#comment-13904971
]
ASF subversion and git services commented on LUCENE-5449:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904973#comment-13904973
]
ASF subversion and git services commented on LUCENE-5449:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-5449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13904976#comment-13904976
]
ASF subversion and git services commented on LUCENE-5449:
-
Commit
1 - 100 of 120 matches
Mail list logo
