See http://fortyounce.servebeer.com/job/the%204547%20machine%20gun/154/
--
[...truncated 1011 lines...]
[junit4:junit4]
[junit4:junit4] Suite: org.apache.lucene.index.TestCheckIndex
[junit4:junit4] Completed on J3 in 0.03s, 3 tests
[junit4:junit4]
See http://fortyounce.servebeer.com/job/the%204547%20machine%20gun/155/
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[
https://issues.apache.org/jira/browse/SOLR-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolai Luthman updated SOLR-3177:
--
Attachment: statsfilterexclude.patch
I've made a patch for this, based on the code from the
Harish Verma created SOLR-4356:
--
Summary: SOLR 4.1 Out Of Memory error After commit of a few
thousand Solr Docs
Key: SOLR-4356
URL: https://issues.apache.org/jira/browse/SOLR-4356
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher updated SOLR-4352:
---
Attachment: SOLR-4352-erik.patch
Eric - how about this patch? It allows the sort parameter(s) to
Hayden Muhl created SOLR-4357:
-
Summary: Default field in query syntax documentation has confusing
error
Key: SOLR-4357
URL: https://issues.apache.org/jira/browse/SOLR-4357
Project: Solr
Issue
[
https://issues.apache.org/jira/browse/SOLR-4357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hayden Muhl updated SOLR-4357:
--
Attachment: SOLR-4357.patch
Small fix for documentation.
Default field in query
[
https://issues.apache.org/jira/browse/LUCENE-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher moved SOLR-4357 to LUCENE-4718:
Component/s: (was: documentation)
[
https://issues.apache.org/jira/browse/SOLR-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harish Verma updated SOLR-4356:
---
Comment: was deleted
(was: screenshots of Memory Dump)
SOLR 4.1 Out Of Memory error After
[
https://issues.apache.org/jira/browse/SOLR-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harish Verma updated SOLR-4356:
---
Attachment: memorydump2.png
memorydump1.png
screenshots of Memory Dump
On Fri, Jan 25, 2013 at 2:30 AM, Robert Muir rcm...@gmail.com wrote:
I think the bug is when its direct and the last block has the
optimized bitsPerValue=0 case.
Right. This was a test bug due to the fact that the reader moves the
file pointer in the for (i = 0; i valueCount; ++i) { assert
See http://fortyounce.servebeer.com/job/the%204547%20machine%20gun/206/
--
[...truncated 966 lines...]
[junit4:junit4]
[junit4:junit4] Suite: org.apache.lucene.index.TestPayloads
[junit4:junit4] Completed on J1 in 0.22s, 7 tests
[junit4:junit4]
See http://fortyounce.servebeer.com/job/the%204547%20machine%20gun/207/
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[
https://issues.apache.org/jira/browse/LUCENE-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562648#comment-13562648
]
Commit Tag Bot commented on LUCENE-4716:
[trunk commit] Shai Erera
[
https://issues.apache.org/jira/browse/LUCENE-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera resolved LUCENE-4716.
Resolution: Fixed
Fix Version/s: 5.0
4.2
Lucene Fields: New,Patch
[
https://issues.apache.org/jira/browse/LUCENE-4716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562661#comment-13562661
]
Commit Tag Bot commented on LUCENE-4716:
[branch_4x commit] Shai Erera
I'll dig.
Mike McCandless
http://blog.mikemccandless.com
On Fri, Jan 25, 2013 at 7:46 AM, Charlie Cron hudsonsevilt...@gmail.com wrote:
See http://fortyounce.servebeer.com/job/the%204547%20machine%20gun/206/
--
[...truncated 966 lines...]
[
https://issues.apache.org/jira/browse/SOLR-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562690#comment-13562690
]
Shalin Shekhar Mangar commented on SOLR-4354:
-
Amit, I don't complete
[
https://issues.apache.org/jira/browse/LUCENE-4708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562693#comment-13562693
]
Commit Tag Bot commented on LUCENE-4708:
[trunk commit] Adrien Grand
[
https://issues.apache.org/jira/browse/LUCENE-4708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562705#comment-13562705
]
Commit Tag Bot commented on LUCENE-4708:
[branch_4x commit] Adrien Grand
[
https://issues.apache.org/jira/browse/LUCENE-4708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand resolved LUCENE-4708.
--
Resolution: Fixed
Make LZ4 hash tables reusable
-
Here's an example query with q.op=AND:
causes of heart attack
And I have this synonym definition:
heart attack, myocardial infarction
So, what is the alleged query parser fix so that the query is treated as:
causes of (heart attack OR myocardial infarction)
The core problem with
Karl Wright created SOLR-4358:
-
Summary: SolrJ, by preventing multi-part post, loses key
information about file name that Tika needs
Key: SOLR-4358
URL: https://issues.apache.org/jira/browse/SOLR-4358
[
https://issues.apache.org/jira/browse/SOLR-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562734#comment-13562734
]
Mark Miller commented on SOLR-4356:
---
Please send questions like this to the user list -
On Fri, Jan 25, 2013 at 9:19 AM, Jack Krupansky j...@basetechnology.com wrote:
Here's an example query with q.op=AND:
causes of heart attack
And I have this synonym definition:
heart attack, myocardial infarction
So, what is the alleged query parser fix so that the query is treated
[
https://issues.apache.org/jira/browse/LUCENE-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562740#comment-13562740
]
Renaud Delbru commented on LUCENE-4642:
---
Hi,
are there still some open questions
[
https://issues.apache.org/jira/browse/SOLR-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562741#comment-13562741
]
Mark Miller commented on SOLR-4043:
---
I'm going to commit this in a moment so it can start
[
https://issues.apache.org/jira/browse/SOLR-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562743#comment-13562743
]
Karl Wright commented on SOLR-4328:
---
The Solr connector in the ManifoldCF project worked
[
https://issues.apache.org/jira/browse/LUCENE-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562745#comment-13562745
]
Robert Muir commented on LUCENE-4642:
-
I raised a lot of questions. I think they are
[
https://issues.apache.org/jira/browse/SOLR-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562759#comment-13562759
]
Commit Tag Bot commented on SOLR-4043:
--
[trunk commit] Mark Robert Miller
[
https://issues.apache.org/jira/browse/SOLR-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562760#comment-13562760
]
Eric Spiegelberg commented on SOLR-4352:
This patch is specifically for maintaining
André created LUCENE-4719:
--
Summary: Payloads per position broken
Key: LUCENE-4719
URL: https://issues.apache.org/jira/browse/LUCENE-4719
Project: Lucene - Core
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LUCENE-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562765#comment-13562765
]
Steve Rowe commented on LUCENE-4642:
Renaud, have you looked at
[
https://issues.apache.org/jira/browse/SOLR-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562769#comment-13562769
]
Erik Hatcher commented on SOLR-4352:
Eric - my patch covers both facet and pagination
[
https://issues.apache.org/jira/browse/LUCENE-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
André updated LUCENE-4719:
---
Fix Version/s: 4.1.1
Payloads per position broken
Key:
[
https://issues.apache.org/jira/browse/SOLR-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562771#comment-13562771
]
Erik Hatcher commented on SOLR-4352:
In your original patch, Eric, it doesn't account
[
https://issues.apache.org/jira/browse/SOLR-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated SOLR-4328:
--
Description:
In ManifoldCF, we've been seeing problems with SolrJ connections throwing
[
https://issues.apache.org/jira/browse/SOLR-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562780#comment-13562780
]
Commit Tag Bot commented on SOLR-4043:
--
[branch_4x commit] Mark Robert Miller
[
https://issues.apache.org/jira/browse/SOLR-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562787#comment-13562787
]
Eric Spiegelberg commented on SOLR-4352:
After comparing the two patches, my patch
[
https://issues.apache.org/jira/browse/LUCENE-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-4719.
-
Resolution: Not A Problem
Assignee: Robert Muir
read the javadocs: its ok that it returns
[
https://issues.apache.org/jira/browse/SOLR-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562798#comment-13562798
]
Jan Høydahl commented on SOLR-3177:
---
Thanks for the patch, Nikolai.
You'll have a
Mark Miller created SOLR-4359:
-
Summary: The RecentUpdates#update method should treat a problem
reading the next record the same as a problem parsing the record - log the
exception and break.
Key: SOLR-4359
URL:
[
https://issues.apache.org/jira/browse/SOLR-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-4043.
---
Resolution: Fixed
Thanks Raintung! Let's open new JIRA's for anything further needed on this.
[
https://issues.apache.org/jira/browse/LUCENE-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
André reopened LUCENE-4719:
Yes, you are right, but the value is also the same.
Payloads per position broken
[
https://issues.apache.org/jira/browse/LUCENE-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562801#comment-13562801
]
André edited comment on LUCENE-4719 at 1/25/13 4:04 PM:
-
Yes,
[
https://issues.apache.org/jira/browse/LUCENE-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
André updated LUCENE-4719:
---
Description: In 4.0 it worked. Since 4.1 getPayload() returns the same
value for every position of the same
Hi,
The below code is throwing the exception:
java.lang.NumberFormatException: For input string: 01.SZ at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
when the TopDocs docs = indexSearcher.search(phraseQuery, null, 10, sort);
line is called. This only happens
One clarification from my previous comment: One requirement is to prevent
false matches for instances of heart infarction and myocardial attack -
the current synonym filter does not preserver the path or term ordering
within the multi-term phrases. Even if the query parser does present the
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/3970/
Java: 32bit/jrockit-jdk1.6.0_33-R28.2.4-4.1.0 -XnoOpt
All tests passed
Build Log:
[...truncated 29961 lines...]
BUILD FAILED
/mnt/ssd/jenkins/workspace/Lucene-Solr-trunk-Linux/build.xml:305: The following
error occurred while
Francois-Xavier Bonnet created SOLR-4360:
Summary: TermVectorAccessor return terms that do not match with
current document
Key: SOLR-4360
URL: https://issues.apache.org/jira/browse/SOLR-4360
[
https://issues.apache.org/jira/browse/SOLR-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francois-Xavier Bonnet updated SOLR-4360:
-
Attachment: SOLR-4360.txt
Here is a patch
TermVectorAccessor
[
https://issues.apache.org/jira/browse/SOLR-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562848#comment-13562848
]
Commit Tag Bot commented on SOLR-4325:
--
[trunk commit] James Dyer
[
https://issues.apache.org/jira/browse/SOLR-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer resolved SOLR-4325.
--
Resolution: Fixed
DIH DateFormatEvaluator seems to have problems with DST changes - test
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-Linux/3948/
Java: 32bit/jdk1.6.0_38 -server -XX:+UseSerialGC
All tests passed
Build Log:
[...truncated 29807 lines...]
BUILD FAILED
/mnt/ssd/jenkins/workspace/Lucene-Solr-4.x-Linux/build.xml:305: The following
error occurred while executing
[
https://issues.apache.org/jira/browse/LUCENE-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562853#comment-13562853
]
Renaud Delbru commented on LUCENE-4642:
---
@steve:
{quote}
have you looked at
[
https://issues.apache.org/jira/browse/SOLR-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562854#comment-13562854
]
Commit Tag Bot commented on SOLR-4325:
--
[branch_4x commit] James Dyer
[
https://issues.apache.org/jira/browse/SOLR-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Nithian closed SOLR-4354.
--
Resolution: Invalid
My apologies that was embarrassing. I was looking at the 4.0 code that we use
and
[
https://issues.apache.org/jira/browse/SOLR-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reopened SOLR-4354:
---
Assignee: Mark Miller
Replication should perform full copy if slave's generation higher than
[
https://issues.apache.org/jira/browse/SOLR-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-4354.
---
Resolution: Duplicate
Replication should perform full copy if slave's generation higher than
[
https://issues.apache.org/jira/browse/SOLR-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562868#comment-13562868
]
Mark Miller commented on SOLR-4354:
---
No worries Amit - looks like this was a dupe of
[
https://issues.apache.org/jira/browse/LUCENE-4720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man moved SOLR-4360 to LUCENE-4720:
Lucene Fields: New
Affects Version/s: (was: 3.6.2)
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/134/
Java: 64bit/jdk1.6.0 -XX:+UseSerialGC
All tests passed
Build Log:
[...truncated 29905 lines...]
BUILD FAILED
/Users/jenkins/jenkins-slave/workspace/Lucene-Solr-trunk-MacOSX/build.xml:305:
The following error occurred while
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/3971/
Java: 32bit/jdk1.6.0_38 -client -XX:+UseParallelGC
All tests passed
Build Log:
[...truncated 29914 lines...]
BUILD FAILED
/mnt/ssd/jenkins/workspace/Lucene-Solr-trunk-Linux/build.xml:305: The following
error occurred while
Build: https://builds.apache.org/job/Lucene-Solr-Maven-4.x/226/
2 tests failed.
FAILED:
org.apache.solr.cloud.RecoveryZkTest.org.apache.solr.cloud.RecoveryZkTest
Error Message:
Resource in scope SUITE failed to close. Resource was registered from thread
Thread[id=3494,
James Dyer created SOLR-4361:
Summary: DIH request parameters with dots throws
UnsupportedOperationException
Key: SOLR-4361
URL: https://issues.apache.org/jira/browse/SOLR-4361
Project: Solr
[
https://issues.apache.org/jira/browse/SOLR-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562900#comment-13562900
]
James Dyer commented on SOLR-4361:
--
Example from user list:
I've just tried to upgrade
[
https://issues.apache.org/jira/browse/SOLR-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Matheis (steffkes) updated SOLR-4225:
Attachment: schema-browser_histogram.png
SOLR-4225.patch
[
https://issues.apache.org/jira/browse/SOLR-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562902#comment-13562902
]
Stefan Matheis (steffkes) edited comment on SOLR-4225 at 1/25/13 6:47 PM:
[
https://issues.apache.org/jira/browse/SOLR-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562927#comment-13562927
]
Commit Tag Bot commented on SOLR-4359:
--
[trunk commit] Mark Robert Miller
[
https://issues.apache.org/jira/browse/SOLR-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562934#comment-13562934
]
Commit Tag Bot commented on SOLR-4359:
--
[branch_4x commit] Mark Robert Miller
[
https://issues.apache.org/jira/browse/SOLR-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved SOLR-4359.
---
Resolution: Fixed
The RecentUpdates#update method should treat a problem reading the next
[
https://issues.apache.org/jira/browse/SOLR-4361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562947#comment-13562947
]
James Dyer commented on SOLR-4361:
--
Also, this workaround was mentioned. This should be
[
https://issues.apache.org/jira/browse/SOLR-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562954#comment-13562954
]
Hoss Man commented on SOLR-4225:
+1 ... nice.
Why are the numbers formated as
[
https://issues.apache.org/jira/browse/SOLR-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562963#comment-13562963
]
Stefan Matheis (steffkes) commented on SOLR-4225:
-
bq. Why are the numbers
[
https://issues.apache.org/jira/browse/SOLR-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562963#comment-13562963
]
Stefan Matheis (steffkes) edited comment on SOLR-4225 at 1/25/13 8:04 PM:
[
https://issues.apache.org/jira/browse/SOLR-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Matheis (steffkes) updated SOLR-4225:
Attachment: schema-browser_histogram.png
Instead of maybe .. have a look at
[
https://issues.apache.org/jira/browse/SOLR-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13563012#comment-13563012
]
Uwe Schindler commented on SOLR-4325:
-
Thanks James!
DIH
[
https://issues.apache.org/jira/browse/LUCENE-4695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13563061#comment-13563061
]
Commit Tag Bot commented on LUCENE-4695:
[trunk commit] Michael McCandless
Ahmet Arslan created SOLR-4362:
--
Summary: edismax, phrase query with slop, pf parameter
Key: SOLR-4362
URL: https://issues.apache.org/jira/browse/SOLR-4362
Project: Solr
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LUCENE-4695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-4695.
Resolution: Fixed
Add utility class for getting live values for a given
PositionLengthAttribute is sufficient to express the true graph, but
SynonymFilter has not been fully fixed to properly set it.
Specifically, it cannot create new positions, which is what's
necessary if you expand when applying synonyms (e.g., dns - domain
name service).
It is better to do the
[
https://issues.apache.org/jira/browse/LUCENE-4695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13563071#comment-13563071
]
Commit Tag Bot commented on LUCENE-4695:
[branch_4x commit] Michael McCandless
Can you provide the full stack trace?
Mike McCandless
http://blog.mikemccandless.com
On Fri, Jan 25, 2013 at 11:13 AM, JimAld jim.alder...@db.com wrote:
Hi,
The below code is throwing the exception:
java.lang.NumberFormatException: For input string: 01.SZ at
[
https://issues.apache.org/jira/browse/SOLR-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13563075#comment-13563075
]
Ahmet Arslan commented on SOLR-4362:
http://search-lucene.com/m/RwfwXkbfc
[
https://issues.apache.org/jira/browse/SOLR-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ahmet Arslan updated SOLR-4362:
---
Attachment: SOLR-4362.patch
A failing test case that demonstrates the problem.
Scott Smerchek created LUCENE-4721:
--
Summary: WordDelimiterFilter ignores payloads
Key: LUCENE-4721
URL: https://issues.apache.org/jira/browse/LUCENE-4721
Project: Lucene - Core
Issue
[
https://issues.apache.org/jira/browse/LUCENE-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Smerchek updated LUCENE-4721:
---
Attachment: LUCENE-4721.patch
WordDelimiterFilter ignores payloads
Michael McCandless created LUCENE-4722:
--
Summary: Can we move SortField.Type.SCORE/DOC to singleton
SortField instances instead...?
Key: LUCENE-4722
URL: https://issues.apache.org/jira/browse/LUCENE-4722
[
https://issues.apache.org/jira/browse/LUCENE-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13563108#comment-13563108
]
Robert Muir commented on LUCENE-4642:
-
My problem i guess with
[
https://issues.apache.org/jira/browse/SOLR-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13563129#comment-13563129
]
Hoss Man commented on SOLR-4225:
Well, 16 years of education at US schools has biased me in
Sure, here it is:
java.lang.NumberFormatException: For input string: 01.SZ
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:458)
at java.lang.Byte.parseByte(Byte.java:151)
at
Also, I made a mistake in my original post, the sort constructor used is
actually of type String as follows:
Sort sort = new Sort(new SortField(fieldName,SortField.Type.STRING));
All the rest of the code is correct.
Thanks.
--
View this message in context:
[
https://issues.apache.org/jira/browse/SOLR-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13563152#comment-13563152
]
Ahmet Arslan commented on SOLR-4362:
Thanks for that insight, Mike!
I don't think anybody is in disagreement with the need for the query parser
to present the full, white-space delimited pseudo-term sequence to analysis
in one step. My proposal from last September recognized that.
Is there a decent writeup on
[
https://issues.apache.org/jira/browse/LUCENE-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13563305#comment-13563305
]
Commit Tag Bot commented on LUCENE-1822:
[trunk commit] Koji Sekiguchi
[
https://issues.apache.org/jira/browse/LUCENE-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13563308#comment-13563308
]
Koji Sekiguchi commented on LUCENE-1822:
I committed the above note to trunk,
[
https://issues.apache.org/jira/browse/LUCENE-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13563312#comment-13563312
]
Commit Tag Bot commented on LUCENE-1822:
[branch_4x commit] Koji Sekiguchi
Hi,
this has nothing to do with PhraseQuery. The stack trace shows, that your code
seems to have passed SortField.BYTE, so maybe you have some logic error?
PhraseQuery by itself does not use the FieldCache, only the the result
collector is using the cache and this one is independent from the
98 matches
Mail list logo
