[
https://issues.apache.org/jira/browse/LUCENE-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12967121#action_12967121
]
Uwe Schindler commented on LUCENE-2235:
---
To come back to the original issue:
bq.
[
https://issues.apache.org/jira/browse/SOLR-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12967125#action_12967125
]
JohnWu commented on SOLR-1395:
--
Tomliu:
so in proxy , not in sub-proxy, katta startNode
[
https://issues.apache.org/jira/browse/LUCENE-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12967127#action_12967127
]
Shai Erera commented on LUCENE-2790:
bq. How Lucene manages the index files is
I've hit another backwards tests problem.
Over in LUCENE-2790 we've changed LogMergePolicy.useCompoundFile's behavior
to factor in the newly added noCFSRatio. After some discussion we decided
that even though it breaks back-compat's runtime behavior, it's ok in this
case because how Lucene
SearchBlox is pleased to announce the availability of SearchBlox Search
Software as a completely FREE product. The product is now available with no
limitations in terms of number of documents indexed and no restrictions in
product functionality. SearchBlox will support the free product with a
Build: https://hudson.apache.org/hudson/job/Lucene-trunk/1384/
All tests passed
Build Log (for compile errors):
[...truncated 18318 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional
getOffsetGap should not be called for non-anaylyzed fields
--
Key: LUCENE-2801
URL: https://issues.apache.org/jira/browse/LUCENE-2801
Project: Lucene - Java
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LUCENE-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12967148#action_12967148
]
Nick Pellow commented on LUCENE-2235:
-
Thanks for the clarification, Uwe. I wasn't
[
https://issues.apache.org/jira/browse/LUCENE-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12967151#action_12967151
]
Uwe Schindler commented on LUCENE-2235:
---
Thanks, Nick!
implement
[
https://issues.apache.org/jira/browse/LUCENE-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-2790:
---
Attachment: LUCENE-2790-3x.patch
Backport to 3x. Note the reflection hack I had to use to make the
[
https://issues.apache.org/jira/browse/LUCENE-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12967183#action_12967183
]
Uwe Schindler commented on LUCENE-2790:
---
I would supply disable the tests.
Using query function in bf parameter in the DisMaxQParser forces the use of
parameter dereferencing
---
Key: SOLR-2267
URL:
[
https://issues.apache.org/jira/browse/SOLR-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12967184#action_12967184
]
Eric Pugh commented on SOLR-1395:
-
Tom, John,
Just wanted to comment that having your
DirectoryReader ignores NRT SegmentInfos in #isOptimized()
--
Key: LUCENE-2802
URL: https://issues.apache.org/jira/browse/LUCENE-2802
Project: Lucene - Java
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LUCENE-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12967208#action_12967208
]
Shai Erera commented on LUCENE-2790:
I don't mind disabling the tests, but I think we
CHANGES file:
LUCENE-2658: Exceptions while processing term vectors enabled for
multiple fields could lead to invalid ArrayIndexOutOfBoundsExceptions.
JIRA description:
LUCENE-2658: TestIndexWriterExceptions random failure: AIOOBE in
ByteBlockPool.allocSlice
So you see the story, i hit
Would you mind naming these Apache projects? I'd like to take a look.
Tika, Nutch, OODT.
Cheers,
Chris
++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B,
[
https://issues.apache.org/jira/browse/LUCENE-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12967210#action_12967210
]
Shai Erera commented on LUCENE-2471:
bq. I think the problem actually wasn't
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12967211#action_12967211
]
Jan Høydahl commented on SOLR-1979:
---
@Grant: I dropped the outputField setting and a
On Mon, Dec 6, 2010 at 9:56 AM, Mattmann, Chris A (388J)
chris.a.mattm...@jpl.nasa.gov wrote:
What's the difference between Mike going and writing up a more informative
CHANGES.txt entry than say updating JIRA with the information from that entry
to have a more descriptive title?
Well, you
[
https://issues.apache.org/jira/browse/LUCENE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12967213#action_12967213
]
Michael McCandless commented on LUCENE-2802:
Nice catch Simon! This is also a
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12967214#action_12967214
]
Grant Ingersoll commented on SOLR-1979:
---
bq. There should be a way to output the
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll updated SOLR-1979:
--
Attachment: SOLR-1979.patch
Removes mentions of ISO 639.
Create
On Dec 6, 2010, at 9:58 AM, Mattmann, Chris A (388J) wrote:
Would you mind naming these Apache projects? I'd like to take a look.
Tika, Nutch, OODT.
Add in Mahout. I believe Hadoop does too.
-
To unsubscribe, e-mail:
FieldCache should not pay attention to deleted docs when creating entries
-
Key: LUCENE-2803
URL: https://issues.apache.org/jira/browse/LUCENE-2803
Project: Lucene - Java
[
https://issues.apache.org/jira/browse/LUCENE-2763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-2763:
Attachment: LUCENE-2763.patch
Updated patch to fix {{solr/CHANGES.txt}}, {{lucene/CHANGES.txt}},
On Dec 5, 2010, at 12:18 PM, Robert Muir wrote:
On Sun, Dec 5, 2010 at 12:08 PM, Mattmann, Chris A (388J)
chris.a.mattm...@jpl.nasa.gov wrote:
Hi Mark,
RE: the credit system. JIRA provides a contribution report here, like this
one that I generated for Lucene 3.1:
My concern with
[
https://issues.apache.org/jira/browse/LUCENE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12967227#action_12967227
]
Simon Willnauer commented on LUCENE-2802:
-
bq. Nice catch Simon! This is also a
check all tests that use FSDirectory.open
-
Key: LUCENE-2804
URL: https://issues.apache.org/jira/browse/LUCENE-2804
Project: Lucene - Java
Issue Type: Test
Reporter: Robert Muir
In
[
https://issues.apache.org/jira/browse/LUCENE-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12967183#action_12967183
]
Uwe Schindler edited comment on LUCENE-2790 at 12/6/10 10:54 AM:
[
https://issues.apache.org/jira/browse/LUCENENET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968383#action_12968383
]
Digy commented on LUCENENET-383:
Hi Chaitanya,
Even tought it seems to be a Lucene.Net
Hey Yonik.
Thanks for clarifying.
The reason I went rolling my own way - I asked previously is there's any
plan to back-port the field collapse to solr 1.4 and
I understood that its not at all straight forward.
If you think it'll be fairly easy to look at the new code in Solr 4.0 trunk
and use
On Mon, Dec 6, 2010 at 3:24 PM, Adam H. jimmoe...@gmail.com wrote:
Hey Yonik.
Thanks for clarifying.
The reason I went rolling my own way - I asked previously is there's any
plan to back-port the field collapse to solr 1.4 and
I understood that its not at all straight forward.
Ahhh... I'd
Fair enough - I might give it a shot if most functionality is compatible to
solr 1.4.1 to your mind? and is fairly stable?
One last Q regarding correct usage of per-segment FieldCache in Solr
components -
since this is something I might also have issues with elsewhere, and I
suspect other people
On Mon, Dec 6, 2010 at 3:41 PM, Adam H. jimmoe...@gmail.com wrote:
Fair enough - I might give it a shot if most functionality is compatible to
solr 1.4.1 to your mind? and is fairly stable?
Yes, the external APIs are very compatible.
The internal APIs - not so much.
You should reindex also.
[
https://issues.apache.org/jira/browse/LUCENE-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968416#action_12968416
]
Simon Willnauer commented on LUCENE-2186:
-
bq. Whew... this interface is more
[
https://issues.apache.org/jira/browse/LUCENE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968418#action_12968418
]
Simon Willnauer commented on LUCENE-2802:
-
I changed DirectoryReader to use the
On Mon, Dec 6, 2010 at 4:02 PM, Yonik Seeley yo...@lucidimagination.com wrote:
On Mon, Dec 6, 2010 at 3:41 PM, Adam H. jimmoe...@gmail.com wrote:
Fair enough - I might give it a shot if most functionality is compatible to
solr 1.4.1 to your mind? and is fairly stable?
Yes, the external APIs
[
https://issues.apache.org/jira/browse/SOLR-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968439#action_12968439
]
Grant Ingersoll commented on SOLR-2186:
---
Lance, can you update this patch and add a
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968445#action_12968445
]
Yonik Seeley commented on SOLR-1979:
bq. In skimming the current patch, it looks like
[
https://issues.apache.org/jira/browse/LUCENE-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968451#action_12968451
]
Yonik Seeley commented on LUCENE-2649:
--
For the sort-missing-last type of
Lucene has this method to set the maximum size of a segment when merging:
LogByteSizeMergePolicy.setMaxMergeMB
(http://lucene.apache.org/java/3_0_2/api/all/org/apache/lucene/index/LogByteSizeMergePolicy.html#setMaxMergeMB%28double%29
)
I would like to be able to set this in my
[
https://issues.apache.org/jira/browse/LUCENE-2649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968458#action_12968458
]
Ryan McKinley commented on LUCENE-2649:
---
looks good to me
bq. we instantiate
So,
summing up all the information i now have, and the fact I have some
additional custom components that use fieldcache,
such that the specific answer for field collapsing by migrating to solr 4.0
is not a complete solution to my problems,
it seems to me more and more like I might have to
On Mon, Dec 6, 2010 at 5:48 PM, Adam H. jimmoe...@gmail.com wrote:
In other words, using a per-segment fieldcache collection as a
post-processing step (e.g after QueryComponent did its collection) does not
seem at all trivial, if at all possible ( is it possible? )
Sure, it's possible, and not
[
https://issues.apache.org/jira/browse/LUCENE-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated LUCENE-2803:
-
Attachment: LUCENE-2803.patch
Here's the patch... pretty simple, so I plan on committing
ah! so just so I can get cracking on this - Can you be alittle more
specific? e.g
in my component implementation that runs in the request handling after the
normal QueryComponent,
How would I access the specific field value for the documents that were
retrieved?
i.e how would it fit in a code
[
https://issues.apache.org/jira/browse/LUCENE-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968488#action_12968488
]
Ryan McKinley commented on LUCENE-2803:
---
if checkMatchAllBits always has a null
[
https://issues.apache.org/jira/browse/LUCENE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer reassigned LUCENE-2802:
---
Assignee: Simon Willnauer
DirectoryReader ignores NRT SegmentInfos in
[
https://issues.apache.org/jira/browse/LUCENE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-2802:
Attachment: LUCENE-2802.patch
here is a patch that removes the mutable state from
This is out of thread, but I realized that some entries for DIH are in
solr/CHANGES.txt. These should go solr/contrib/dataimporthandler/CHANGES.txt
(Some of them are my fault). I also found that solr/contrib/*/CHANGES.txt
have 1.5-dev title. These should be 4.0-dev or 3.1-dev.
I'll open a
[
https://issues.apache.org/jira/browse/LUCENE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-2802:
Affects Version/s: 3.1
we need to backport to 3.x too
DirectoryReader ignores NRT
[
https://issues.apache.org/jira/browse/LUCENE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968503#action_12968503
]
Earwin Burrfoot commented on LUCENE-2802:
-
Patch looks cool.
DirectoryReader
One more comment/question -
Having looked at the Solr stats panel, I do not see detailed memory usage
for the field i'm collapsing on in the lucene FieldCache entries listings.
As I understand ( after having looked through this ticket:
https://issues.apache.org/jira/browse/SOLR-1292 ), this means
SegmentInfos shouldn't blindly increment version on commit
--
Key: LUCENE-2805
URL: https://issues.apache.org/jira/browse/LUCENE-2805
Project: Lucene - Java
Issue Type: Bug
contrib entries in solr/CHANGES.txt should go solr/contrib/*/CHANGES.txt
Key: SOLR-2269
URL: https://issues.apache.org/jira/browse/SOLR-2269
Project: Solr
Issue Type:
[
https://issues.apache.org/jira/browse/LUCENE-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968521#action_12968521
]
Michael McCandless commented on LUCENE-2805:
Duh, make that LUCENE-2802.
[
https://issues.apache.org/jira/browse/LUCENE-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2805:
---
Attachment: LUCENE-2805.patch
Attached first cut patch, just moving the .version++
[
https://issues.apache.org/jira/browse/SOLR-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968528#action_12968528
]
Grant Ingersoll commented on SOLR-1979:
---
bq. So for all unmapped languages, you may
[
https://issues.apache.org/jira/browse/SOLR-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi updated SOLR-1721:
-
Affects Version/s: 1.3
1.4
Fix Version/s: 4.0
[
https://issues.apache.org/jira/browse/SOLR-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968545#action_12968545
]
Grant Ingersoll commented on SOLR-2268:
---
This is a work in progress. Here are a few
[
https://issues.apache.org/jira/browse/SOLR-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968553#action_12968553
]
Lance Norskog commented on SOLR-2268:
-
2 tricks for speeding up document holds polygons,
Build: https://hudson.apache.org/hudson/job/Lucene-trunk/1385/
All tests passed
Build Log (for compile errors):
[...truncated 18318 lines...]
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional
I have not tried this, but some parts of the solrconfig elements
support setters for sub-elements. So, this might work but probably
won't.
mergePolicyorg.apache.lucene.index.LogByteSizeMergePolicy
maxMergeMB1024/maxMergeMB
/mergePolicy
On Mon, Dec 6, 2010 at 2:34 PM, Burton-West, Tom
[
https://issues.apache.org/jira/browse/SOLR-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968553#action_12968553
]
Lance Norskog edited comment on SOLR-2268 at 12/6/10 10:08 PM:
---
[
https://issues.apache.org/jira/browse/SOLR-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12968556#action_12968556
]
Lance Norskog commented on SOLR-2268:
-
A second variation: a multiValued field of vertex
Build: https://hudson.apache.org/hudson/job/Lucene-Solr-tests-only-trunk/2255/
15 tests failed.
REGRESSION: org.apache.solr.cloud.CloudStateUpdateTest.testCoreRegistration
Error Message:
null
Stack Trace:
org.apache.solr.common.cloud.ZooKeeperException:
at
[
https://issues.apache.org/jira/browse/LUCENE-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-2805:
Attachment: LUCENE-2805.patch
here is a slightly updated patch that removes the blind
Jumping in late to this thread, though I've read most of it.
As a user and committer, I find the current CHANGES very convenient!
It's very easy for me to read what has changed in 3.0, and very easy
for me to put a CHANGES entry whenever I work on something that
warrants such entry.
And if an
69 matches
Mail list logo