[
https://issues.apache.org/jira/browse/LUCENE-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13012895#comment-13012895
]
Michael McCandless commented on LUCENE-3001:
{quote}
The current ptoblem with
[
https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson reassigned SOLR-2399:
Assignee: (was: Erick Erickson)
Sorry, hit the assign button by mistake
Solr
[
https://issues.apache.org/jira/browse/SOLR-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson reassigned SOLR-2399:
Assignee: Erick Erickson
Solr Admin Interface, reworked
--
(Long post, please bear with me and please read!)
Now that we have the release done (I'm working through the publication process
now), I want to start the process of thinking about how we can improve the
release process. As I see it, building the artifacts and checking the legal
items are now
I'll also add:
We need to figure out a better approach for CHANGES.txt. Step 4 of the
Publishing process is a PITA.
On Mar 30, 2011, at 8:22 AM, Grant Ingersoll wrote:
(Long post, please bear with me and please read!)
Now that we have the release done (I'm working through the publication
Hi Grant,
This is a great post.
I'm not a committer for Lucene or Solr, but I'm seriously thinking that much of
what Lucene/Solr does right should be considered by the project I AM a
committer for: ManifoldCF.
Key things I would add based on experience with commercial software development:
[
https://issues.apache.org/jira/browse/LUCENE-2994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-2994.
---
Resolution: Fixed
Committed 3.x revisions 1086941, 1086942
When 3.1 is released, update
[
https://issues.apache.org/jira/browse/LUCENE-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-3002:
---
Attachment: LUCENE-3002.patch
Patch (3x) adds 'tests.iter.min' which allows stop iterating if at
On Wed, Mar 30, 2011 at 8:22 AM, Grant Ingersoll gsing...@apache.org wrote:
(Long post, please bear with me and please read!)
Now that we have the release done (I'm working through the publication
process now), I want to start the process of thinking about how we can
improve the release
[
https://issues.apache.org/jira/browse/SOLR-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13012949#comment-13012949
]
Robert Muir commented on SOLR-2002:
---
I think we had a really good start here at one
[
https://issues.apache.org/jira/browse/LUCENE-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13012953#comment-13012953
]
Simon Willnauer commented on LUCENE-2573:
-
Today I merged with trunk and updated
[
https://issues.apache.org/jira/browse/LUCENE-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-2881.
-
Resolution: Fixed
merged to docvalues and realtime branch.
Track FieldInfo per
[
https://issues.apache.org/jira/browse/SOLR-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13012971#comment-13012971
]
Chris Male commented on SOLR-2002:
--
Hey Robert, I'd like to chip in here where I can.
[
https://issues.apache.org/jira/browse/SOLR-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13012981#comment-13012981
]
Robert Muir commented on SOLR-2002:
---
Hi Chris, so mainly i want to start with the patch
[
https://issues.apache.org/jira/browse/SOLR-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13012984#comment-13012984
]
Chris Male commented on SOLR-2002:
--
bq. once everything is using a single common-build
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-Maven-trunk/74/
1 tests failed.
FAILED:
org.apache.solr.schema.TestICUCollationField.org.apache.solr.schema.TestICUCollationField
Error Message:
Cannot find resource: solr-analysis-extras/conf/solrconfig-icucollate.xml
Stack Trace:
MoreLikeThis query could optionnaly output the original document in the MLT
result itself
-
Key: SOLR-2447
URL: https://issues.apache.org/jira/browse/SOLR-2447
[
https://issues.apache.org/jira/browse/LUCENE-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13012996#comment-13012996
]
Robert Muir commented on LUCENE-2959:
-
Hi David, to try to help get things moving, I
[
https://issues.apache.org/jira/browse/SOLR-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013005#comment-13013005
]
Robert Muir commented on SOLR-2002:
---
definitely in the common-build. this way you
[
https://issues.apache.org/jira/browse/LUCENE-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013019#comment-13013019
]
Robert Muir commented on LUCENE-3002:
-
I took a glance, looks good to me!
Add
FYI: release bits are propagating through the ASF mirrors. I will send the
official announcement, based off what is in
https://svn.apache.org/repos/asf/lucene/dev/misc/announcements tomorrow AM.
Thanks again for everyone's help!
On Mar 29, 2011, at 3:38 PM, Simon Willnauer wrote:
+1
I
[
https://issues.apache.org/jira/browse/LUCENE-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013519#comment-13013519
]
Grant Ingersoll commented on LUCENE-3000:
-
Yeah, I don't think we need to name
On Mar 30, 2011, at 9:19 AM, Robert Muir wrote:
On Wed, Mar 30, 2011 at 8:22 AM, Grant Ingersoll gsing...@apache.org wrote:
(Long post, please bear with me and please read!)
Now that we have the release done (I'm working through the publication
process now), I want to start the process of
Define Test Plan for 3.2
Key: LUCENE-3004
URL: https://issues.apache.org/jira/browse/LUCENE-3004
Project: Lucene - Java
Issue Type: Test
Reporter: Grant Ingersoll
Priority: Blocker
Before
Define Test Plan for 4.0
Key: LUCENE-3005
URL: https://issues.apache.org/jira/browse/LUCENE-3005
Project: Lucene - Java
Issue Type: Test
Affects Versions: 4.0
Reporter: Grant Ingersoll
[
https://issues.apache.org/jira/browse/LUCENE-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013530#comment-13013530
]
Michael McCandless commented on LUCENE-3006:
+1
Javadocs warnings should
I have a test framework that extends LuceneTestCase and tests a bunch
of spatial indexing strategies.
One strategy writes binary tokens (eventually this should be CSF) and
i'm getting an error when it hits the preflex codec.
Is there a way to avoid this?
yes, the collation tests work the same way, as they use pure binary tokens.
so their tests look like this:
@Override
public void setUp() throws Exception {
super.setUp();
assumeFalse(preflex format only supports UTF-8 encoded bytes,
[
https://issues.apache.org/jira/browse/LUCENE-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013540#comment-13013540
]
Yonik Seeley commented on LUCENE-3006:
--
One nit - javadocs for solr are not nearly
[
https://issues.apache.org/jira/browse/LUCENE-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013544#comment-13013544
]
Steven Rowe commented on LUCENE-3006:
-
Doron Cohen briefly enabled
[
https://issues.apache.org/jira/browse/SOLR-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013547#comment-13013547
]
Stanislaw Osinski commented on SOLR-2448:
-
Oh, is there any way to assign this
[
https://issues.apache.org/jira/browse/LUCENE-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013548#comment-13013548
]
Yonik Seeley commented on LUCENE-3006:
--
bq. We should fail the build when there are
Loading of Carrot2 resources from Solr config directory
---
Key: SOLR-2449
URL: https://issues.apache.org/jira/browse/SOLR-2449
Project: Solr
Issue Type: Improvement
Components:
Carrot2 clustering should use both its own and Solr's stop words
Key: SOLR-2450
URL: https://issues.apache.org/jira/browse/SOLR-2450
Project: Solr
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SOLR-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013555#comment-13013555
]
Robert Muir commented on SOLR-2448:
---
Hi, i tried to give you access (i think Grant tried
[
https://issues.apache.org/jira/browse/SOLR-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013556#comment-13013556
]
Robert Muir commented on SOLR-2448:
---
Stanislaw: can you try now and see if you can assign
[
https://issues.apache.org/jira/browse/SOLR-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanislaw Osinski reassigned SOLR-2450:
---
Assignee: Stanislaw Osinski
Carrot2 clustering should use both its own and Solr's
[
https://issues.apache.org/jira/browse/LUCENE-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013559#comment-13013559
]
Michael Busch commented on LUCENE-2573:
---
Thanks Simon!
I'll work on LUCENE-2956
[
https://issues.apache.org/jira/browse/SOLR-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanislaw Osinski updated SOLR-2448:
Assignee: Stanislaw Osinski
Yes, thanks!
Upgrade Carrot2 to version 3.5.0
[
https://issues.apache.org/jira/browse/LUCENE-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera resolved LUCENE-3002.
Resolution: Fixed
Committed revision 1087033 (3x).
Committed revision 1087036 (trunk).
Add
[
https://issues.apache.org/jira/browse/LUCENE-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-3006:
Attachment: LUCENE-3006.patch
Build hook in to javadoc. Doesn't fix the warnings, which
Fast vector highlighter: Allow access to start/end offsets
--
Key: LUCENE-3007
URL: https://issues.apache.org/jira/browse/LUCENE-3007
Project: Lucene - Java
Issue Type: Improvement
NumberFormatException: For input string:
gen.before_restore_2011-03-21_07.15.36.372112
Key: LUCENE-3008
URL: https://issues.apache.org/jira/browse/LUCENE-3008
[
https://issues.apache.org/jira/browse/SOLR-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013611#comment-13013611
]
Hoss Man commented on SOLR-2449:
i'm not really up on how you configure carrot, but can we
[
https://issues.apache.org/jira/browse/SOLR-2449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013614#comment-13013614
]
Stanislaw Osinski commented on SOLR-2449:
-
This is exactly how I implemented it.
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/6535/
1 tests failed.
REGRESSION: org.apache.lucene.collation.TestCollationKeyAnalyzer.testThreadSafe
Error Message:
Java heap space
Stack Trace:
java.lang.OutOfMemoryError: Java heap space
at
[
https://issues.apache.org/jira/browse/SOLR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013618#comment-13013618
]
Hoss Man commented on SOLR-2338:
i was confused by some of roberts comments, and clarified
thanks -- I also see it failing on SimpleText. Is that expected?
On Wed, Mar 30, 2011 at 12:27 PM, Robert Muir rcm...@gmail.com wrote:
yes, the collation tests work the same way, as they use pure binary tokens.
so their tests look like this:
@Override
public void setUp() throws
On Wed, Mar 30, 2011 at 4:15 PM, Ryan McKinley ryan...@gmail.com wrote:
thanks -- I also see it failing on SimpleText. Is that expected?
I don't think that is expected? The collation keys use binary terms in
their tests and pass with simpletext, though that doesn't mean their
isn't a
I also see it with:
test params are: codec=RandomCodecProvider:
{id=MockFixedIntBlock(blockSize=1821), geo=SimpleText, name=MockSep},
locale=no_NO_NY, timezone=Europe/Chisinau
IIUC, that picks a random provider for each field? and geo got SimpleText.
The actual error I see is with code I have
[
https://issues.apache.org/jira/browse/SOLR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013626#comment-13013626
]
Yonik Seeley commented on SOLR-2338:
bq. similarity/ should probably not be advertised
[
https://issues.apache.org/jira/browse/LUCENENET-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013628#comment-13013628
]
Amanuel Workneh commented on LUCENENET-391:
---
A 2.9.2-version of Pasha's code
[
https://issues.apache.org/jira/browse/SOLR-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013629#comment-13013629
]
Robert Muir commented on SOLR-2450:
---
just to extend on hossman's point, there are a
On Wed, Mar 30, 2011 at 4:22 PM, Ryan McKinley ryan...@gmail.com wrote:
int off = ref.offset;
...
if (off + buf.length ref.length) {
throw new InvalidShapeException(Asking for too many bytes);
this check looks like it might be wrong (backwards logic)
[
https://issues.apache.org/jira/browse/SOLR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013633#comment-13013633
]
Hoss Man commented on SOLR-2338:
bq. Do you mean the expert-level SimilarityProvider,
no
dooh -- yes, logic was backwards.
Thank you random testing! (and Robert -- of course)
On Wed, Mar 30, 2011 at 4:32 PM, Robert Muir rcm...@gmail.com wrote:
On Wed, Mar 30, 2011 at 4:22 PM, Ryan McKinley ryan...@gmail.com wrote:
int off = ref.offset;
...
if (off +
I would like to be able to use the Lucene Benchmark code with Solr to run some
indexing tests. It would be nice if Lucene Benchmark to could read Solr
configuration rather than having to translate my filter chain and other
parameters into Lucene. Would it be appropriate to open a JIRA issue
[
https://issues.apache.org/jira/browse/SOLR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013652#comment-13013652
]
Robert Muir commented on SOLR-2338:
---
I agree with your order, i think to keep the example
[
https://issues.apache.org/jira/browse/LUCENE-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated LUCENE-3006:
Attachment: LUCENE-3006.patch
Adds a property to only fail if failonjavadocwarning is
[
https://issues.apache.org/jira/browse/LUCENE-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013678#comment-13013678
]
Grant Ingersoll commented on LUCENE-3006:
-
I think this is ready to go, but still
[
https://issues.apache.org/jira/browse/SOLR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013686#comment-13013686
]
Yonik Seeley commented on SOLR-2338:
I dunno - it seems much more likely that someone
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-3.x/6539/
1 tests failed.
REGRESSION: org.apache.lucene.collation.TestCollationKeyAnalyzer.testThreadSafe
Error Message:
Java heap space
Stack Trace:
java.lang.OutOfMemoryError: Java heap space
at
[
https://issues.apache.org/jira/browse/SOLR-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated SOLR-2338:
--
Attachment: SOLR-2338.patch
attached is the modifications:
* default similarity/ is used as a fallback
[
https://issues.apache.org/jira/browse/LUCENE-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-3003:
---
Attachment: LUCENE-3003.patch
New patch, fixing all the nocommits, adding test case
[
https://issues.apache.org/jira/browse/LUCENE-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013731#comment-13013731
]
Yonik Seeley commented on LUCENE-3003:
--
bq. I'd guess that pulsing should be 'good
[
https://issues.apache.org/jira/browse/LUCENE-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013731#comment-13013731
]
Yonik Seeley edited comment on LUCENE-3003 at 3/30/11 11:36 PM:
binary packaging: lucene modules/contribs that depend on jars are confusing
Key: LUCENE-3009
URL: https://issues.apache.org/jira/browse/LUCENE-3009
Project: Lucene - Java
On Wed, Mar 30, 2011 at 4:49 PM, Burton-West, Tom tburt...@umich.edu wrote:
I would like to be able to use the Lucene Benchmark code with Solr to run
some indexing tests. It would be nice if Lucene Benchmark to could read
Solr configuration rather than having to translate my filter chain and
[
https://issues.apache.org/jira/browse/LUCENE-3003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013747#comment-13013747
]
Yonik Seeley commented on LUCENE-3003:
--
bq. The first-pass that allocates lots of
[
https://issues.apache.org/jira/browse/LUCENE-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013753#comment-13013753
]
Steven Rowe commented on LUCENE-3006:
-
I'm working on cleaning up javadoc warnings on
On Mar 30, 2011, at 7:56 PM, Robert Muir wrote:
On Wed, Mar 30, 2011 at 4:49 PM, Burton-West, Tom tburt...@umich.edu wrote:
I would like to be able to use the Lucene Benchmark code with Solr to run
some indexing tests. It would be nice if Lucene Benchmark to could read
Solr configuration
[
https://issues.apache.org/jira/browse/LUCENE-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-3006:
Attachment: LUCENE-3006-javadoc-warning-cleanup.patch
This patch eliminates javadoc warnings on
[
https://issues.apache.org/jira/browse/LUCENE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013788#comment-13013788
]
Robert Muir commented on LUCENE-3009:
-
I checked some older lucene binary releases
[
https://issues.apache.org/jira/browse/SOLR-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13013790#comment-13013790
]
Lance Norskog commented on SOLR-1485:
-
Julien Noche posted last August that he had to
74 matches
Mail list logo
