[
https://issues.apache.org/jira/browse/LUCENE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798590#action_12798590
]
Steven Rowe commented on LUCENE-2181:
-
{quote}
Steven I also havent forgotten about yo
[
https://issues.apache.org/jira/browse/LUCENE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798589#action_12798589
]
Steven Rowe commented on LUCENE-2181:
-
I think NewCollationAnalyzerTask should be a li
[
https://issues.apache.org/jira/browse/LUCENE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798588#action_12798588
]
Steven Rowe commented on LUCENE-2181:
-
I just ran the contrib/benchmark tests, and I g
[
https://issues.apache.org/jira/browse/LUCENE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798584#action_12798584
]
Steven Rowe commented on LUCENE-2181:
-
Works for me:
JAVA:
java version "1.5.0_15"
Ja
Thanks for the clarification Chris. My key concern was that "tags" was
becoming too crowded as-is, and important data is getting lost in the crowd.
Looks like Uwe has a solution per
https://issues.apache.org/jira/browse/LUCENE-2193. If this won't do, I like
you suggestion of structuring "tags" p
[
https://issues.apache.org/jira/browse/LUCENE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2181:
Attachment: LUCENE-2181.patch
ok, somehow it completely bypassed my brain you are using ReadTokens
[
https://issues.apache.org/jira/browse/LUCENE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2181:
Attachment: LUCENE-2181.patch
fix a bug in testCollator/assertEqualCollation, so its actually test
[
https://issues.apache.org/jira/browse/LUCENE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2181:
Attachment: LUCENE-2181.patch
ok i think we might be close to something committable now:
* wrote t
Even if it's not strictly needed anymore, could it improve performance?
Right now I need to use commit() right after this dual operation to
make sure no reader is ever going to miss it, but if it was atomic I
could have avoided the commit and just trust that "at some time later"
it will be auto-com
[
https://issues.apache.org/jira/browse/LUCENE-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-2200.
-
Resolution: Fixed
Fix Version/s: 3.1
Thanks Steven!
> Several final classes have non-ove
I think there no particular demand...
But: why not just separately delete by query, then add?
Back when IW had autoCommit=true, it was compelling to have an atomic
update, but now with only autoCommit=false, the app has full control
over visibility to readers, so do we even need update-by-term an
[
https://issues.apache.org/jira/browse/LUCENE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798541#action_12798541
]
Philipp Nanz commented on LUCENE-2202:
--
Hello Robert, many thanks for your help and s
[
https://issues.apache.org/jira/browse/LUCENE-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-2199.
-
Resolution: Fixed
> ShingleFilter skips over trie-shingles if outputUnigram is set to false
> --
[
https://issues.apache.org/jira/browse/LUCENE-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-2200:
Attachment: LUCENE-2200.patch
bq. Robert, when you commit this make sure you mark the Attributes i
If the demand is the problem:
I would really love that: in most scenarios a single term is not
enough to identify a Document: I need at least two so I use usually
remove-by-query first and then add again.
This sometimes needs some application level lock to make the changes consistent.
Sanne
2010/
[
https://issues.apache.org/jira/browse/LUCENE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798527#action_12798527
]
Robert Muir commented on LUCENE-2181:
-
Steven I also havent forgotten about your other
Any reason we don't offer update doc by query along with term?
Its easy enough to implement in the same manner - is there some sort of
gotchya with this, or is it just because there has been no demand yet?
--
- Mark
http://www.lucidimagination.com
---
[
https://issues.apache.org/jira/browse/LUCENE-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2199:
Affects Version/s: (was: 2.4.1)
(was: 2.4)
Fix Version/s: 3.
[
https://issues.apache.org/jira/browse/LUCENE-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir reassigned LUCENE-2199:
---
Assignee: Robert Muir (was: Simon Willnauer)
> ShingleFilter skips over trie-shingles if ou
[
https://issues.apache.org/jira/browse/LUCENE-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798522#action_12798522
]
Simon Willnauer commented on LUCENE-2199:
-
I committed this in revision 897672
Rob
[
https://issues.apache.org/jira/browse/LUCENE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798520#action_12798520
]
Steven Rowe commented on LUCENE-2181:
-
bq. Steven, another idea: what if we simply add
[
https://issues.apache.org/jira/browse/LUCENE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798519#action_12798519
]
Steven Rowe edited comment on LUCENE-2181 at 1/10/10 5:56 PM:
--
[
https://issues.apache.org/jira/browse/LUCENE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798519#action_12798519
]
Steven Rowe commented on LUCENE-2181:
-
bq. What about this per-field thing, what if in
[
https://issues.apache.org/jira/browse/LUCENE-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798517#action_12798517
]
Simon Willnauer commented on LUCENE-2197:
-
Yonik, would you commit this issue plea
[
https://issues.apache.org/jira/browse/LUCENE-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798516#action_12798516
]
Simon Willnauer commented on LUCENE-2200:
-
Robert, when you commit this make sure
[
https://issues.apache.org/jira/browse/LUCENE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798514#action_12798514
]
Robert Muir edited comment on LUCENE-2181 at 1/10/10 5:35 PM:
--
[
https://issues.apache.org/jira/browse/LUCENE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798514#action_12798514
]
Robert Muir commented on LUCENE-2181:
-
Steven, another idea: what if we simply added t
[
https://issues.apache.org/jira/browse/LUCENE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798510#action_12798510
]
Robert Muir commented on LUCENE-2181:
-
Steve ahh i was wondering about the per-field a
[
https://issues.apache.org/jira/browse/LUCENE-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798508#action_12798508
]
Steven Rowe commented on LUCENE-2181:
-
Looks good. I like the way you've integrated i
[
https://issues.apache.org/jira/browse/LUCENE-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir reassigned LUCENE-2200:
---
Assignee: Robert Muir
> Several final classes have non-overriding protected members
> --
[
https://issues.apache.org/jira/browse/LUCENE-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798495#action_12798495
]
Robert Muir commented on LUCENE-2200:
-
all tests pass and patch looks good to me. will
[
https://issues.apache.org/jira/browse/LUCENE-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798478#action_12798478
]
Robert Muir commented on LUCENE-2201:
-
if no one objects I will commit this in a few d
[
https://issues.apache.org/jira/browse/LUCENE-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798474#action_12798474
]
Simon Willnauer commented on LUCENE-2199:
-
I plan to commit this in today or tomor
[
https://issues.apache.org/jira/browse/LUCENE-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798470#action_12798470
]
Robert Muir commented on LUCENE-2199:
-
simon, your fix makes sense to me... i think yo
[
https://issues.apache.org/jira/browse/LUCENE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-2202.
-
Resolution: Invalid
> PhraseQuery will not find hits containing stop words when StandardAnalyzer
[
https://issues.apache.org/jira/browse/LUCENE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798464#action_12798464
]
Robert Muir commented on LUCENE-2202:
-
Hello Philipp,
the tokenize() method in this t
[
https://issues.apache.org/jira/browse/LUCENE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Nanz updated LUCENE-2202:
-
Attachment: TestCase.java
Added Junit4 testcase that exhibits the problem.
> PhraseQuery will n
PhraseQuery will not find hits containing stop words when StandardAnalyzer with
2.9 or 3.0 semantics is used
Key: LUCENE-2202
URL: https://issues.apache.o
38 matches
Mail list logo
