[
https://issues.apache.org/jira/browse/LUCENE-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16233550#comment-16233550
]
Trejkaz commented on LUCENE-5905:
-
Adding one more case we found which seems to behave the same in
[
https://issues.apache.org/jira/browse/LUCENE-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trejkaz updated LUCENE-5905:
Affects Version/s: 6.6
> Different behaviour of JapaneseAnalyzer at indexing time vs. at search time
>
[
https://issues.apache.org/jira/browse/LUCENE-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16030636#comment-16030636
]
Trejkaz commented on LUCENE-6917:
-
Did this ever hit the dev list? Google can't seem to find it. I'm
[
https://issues.apache.org/jira/browse/LUCENE-7467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15967058#comment-15967058
]
Trejkaz commented on LUCENE-7467:
-
Saw the same thing on Lucene 5.5.2.
{code}
[
https://issues.apache.org/jira/browse/LUCENE-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868920#comment-15868920
]
Trejkaz commented on LUCENE-7260:
-
Lucene 6.3:
{noformat}
dt: 22307
dt: 21190
dt: 21004
dt: 20972
dt:
[
https://issues.apache.org/jira/browse/LUCENE-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trejkaz updated LUCENE-7260:
Affects Version/s: 5.5.2
6.3
> StandardQueryParser is over 100 times slower in v5
[
https://issues.apache.org/jira/browse/LUCENE-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15868916#comment-15868916
]
Trejkaz commented on LUCENE-7260:
-
Lucene 5.5 is an additional 50% slower.
{noformat}
dt: 28105
dt:
[
https://issues.apache.org/jira/browse/LUCENE-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15793976#comment-15793976
]
Trejkaz commented on LUCENE-998:
Won't fix? I was about to file this one.
I don't think this setting
[
https://issues.apache.org/jira/browse/LUCENE-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15793923#comment-15793923
]
Trejkaz commented on LUCENE-7616:
-
As an additional nasty point, sometimes this method is called from
Trejkaz created LUCENE-7616:
---
Summary: QueryNode#toQueryString says it produces a string in the
syntax understood by "the query parser", but cannot possibly know how
Key: LUCENE-7616
URL:
[
https://issues.apache.org/jira/browse/LUCENE-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469582#comment-15469582
]
Trejkaz edited comment on LUCENE-3371 at 9/7/16 5:17 AM:
-
To summarise some
[
https://issues.apache.org/jira/browse/LUCENE-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469582#comment-15469582
]
Trejkaz commented on LUCENE-3371:
-
To summarise some investigation I did towards using SpanNotNearQuery,
[
https://issues.apache.org/jira/browse/LUCENE-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469543#comment-15469543
]
Trejkaz commented on LUCENE-3370:
-
It does seem to give me what I wanted, so I think it's probably fine
[
https://issues.apache.org/jira/browse/LUCENE-7434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15469539#comment-15469539
]
Trejkaz commented on LUCENE-7434:
-
Dupe of LUCENE-3369?
> Add minNumberShouldMatch parameter to
[
https://issues.apache.org/jira/browse/LUCENE-7135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15278502#comment-15278502
]
Trejkaz commented on LUCENE-7135:
-
I see this when running our unit tests also. Evidently somewhere up
[
https://issues.apache.org/jira/browse/LUCENE-7266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trejkaz updated LUCENE-7266:
Affects Version/s: 5.4.1
> QueryNode#cloneTree produces a new tree where parents are not correctly set
>
Trejkaz created LUCENE-7266:
---
Summary: QueryNode#cloneTree produces a new tree where parents are
not correctly set
Key: LUCENE-7266
URL: https://issues.apache.org/jira/browse/LUCENE-7266
Project: Lucene -
[
https://issues.apache.org/jira/browse/LUCENE-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262648#comment-15262648
]
Trejkaz commented on LUCENE-7260:
-
Meanwhile I threw some hashCode() calls in on the query object, in
[
https://issues.apache.org/jira/browse/LUCENE-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trejkaz closed LUCENE-6865.
---
Resolution: Duplicate
Fix Version/s: 5.3
Verified as another duplicate of LUCENE-5805. Fixed by the
[
https://issues.apache.org/jira/browse/LUCENE-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15262522#comment-15262522
]
Trejkaz commented on LUCENE-7260:
-
Is there a faster way to do it? Keeping in mind that it has to be
[
https://issues.apache.org/jira/browse/LUCENE-7260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15261691#comment-15261691
]
Trejkaz commented on LUCENE-7260:
-
Well, this slowdown is also noticeable in our full application, where
Trejkaz created LUCENE-7260:
---
Summary: StandardQueryParser is over 100 times slower in v5
compared to v3
Key: LUCENE-7260
URL: https://issues.apache.org/jira/browse/LUCENE-7260
Project: Lucene - Core
[
https://issues.apache.org/jira/browse/LUCENE-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trejkaz updated LUCENE-5905:
Affects Version/s: 5.2.1
Description:
A document with the word 秋葉原 in the body, when analysed by
[
https://issues.apache.org/jira/browse/LUCENE-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trejkaz updated LUCENE-5905:
Summary: Different behaviour of JapaneseAnalyzer at indexing time vs. at
search time results in no matches
[
https://issues.apache.org/jira/browse/LUCENE-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14984702#comment-14984702
]
Trejkaz commented on LUCENE-6865:
-
Temporary workaround for now I guess. Override the process method to
[
https://issues.apache.org/jira/browse/LUCENE-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14984702#comment-14984702
]
Trejkaz edited comment on LUCENE-6865 at 11/2/15 3:44 AM:
--
Temporary workaround
[
https://issues.apache.org/jira/browse/LUCENE-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14984675#comment-14984675
]
Trejkaz commented on LUCENE-6865:
-
Tried updating to 5.3, looks like backwards compatibility was broken
[
https://issues.apache.org/jira/browse/LUCENE-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14981682#comment-14981682
]
Trejkaz commented on LUCENE-6865:
-
The underlying issue here seems like it might be LUCENE-6506 ... but
[
https://issues.apache.org/jira/browse/LUCENE-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14979684#comment-14979684
]
Trejkaz commented on LUCENE-6865:
-
These tests fail too. Note these don't even call set() - the tree gets
Trejkaz created LUCENE-6865:
---
Summary: BooleanQuery2ModifierNodeProcessor breaks the query node
hierarchy
Key: LUCENE-6865
URL: https://issues.apache.org/jira/browse/LUCENE-6865
Project: Lucene - Core
[
https://issues.apache.org/jira/browse/LUCENE-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14979537#comment-14979537
]
Trejkaz commented on LUCENE-6865:
-
Suspicious code #1. A call to processIteration which is not using the
Trejkaz created LUCENE-6864:
---
Summary: java.util.MissingResourceException: Can't find bundle for
base name org.apache.lucene.queryParser.messages.QueryParserMessages
Key: LUCENE-6864
URL:
[
https://issues.apache.org/jira/browse/LUCENE-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14979528#comment-14979528
]
Trejkaz commented on LUCENE-6865:
-
Standalone reproduction:
{code}
import java.util.Arrays;
import
[
https://issues.apache.org/jira/browse/LUCENE-6865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14979605#comment-14979605
]
Trejkaz commented on LUCENE-6865:
-
Another reproduction which doesn't use the processor, confirming my
Trejkaz created LUCENE-6851:
---
Summary: Allow using other implementations of Format with
NumericConfig
Key: LUCENE-6851
URL: https://issues.apache.org/jira/browse/LUCENE-6851
Project: Lucene - Core
[
https://issues.apache.org/jira/browse/LUCENE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trejkaz updated LUCENE-6826:
Attachment: Lucene6826.java
This test creates an index with one document which contains a value which does
[
https://issues.apache.org/jira/browse/LUCENE-6826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14944724#comment-14944724
]
Trejkaz commented on LUCENE-6826:
-
One of the fields, our test indexes all have the same value, which
Trejkaz created LUCENE-6826:
---
Summary: java.lang.ClassCastException:
org.apache.lucene.index.TermsEnum$2 cannot be cast to
org.apache.lucene.index.MultiTermsEnum when adding indexes
Key: LUCENE-6826
URL:
[
https://issues.apache.org/jira/browse/LUCENE-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14621838#comment-14621838
]
Trejkaz commented on LUCENE-5956:
-
The class loader approach is definitely turning out to
[
https://issues.apache.org/jira/browse/LUCENE-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14616117#comment-14616117
]
Trejkaz commented on LUCENE-6658:
-
What does work: making a forceCommit() method which
[
https://issues.apache.org/jira/browse/LUCENE-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14616111#comment-14616111
]
Trejkaz commented on LUCENE-6658:
-
This works when applied to my v4 and v5 here as well.
[
https://issues.apache.org/jira/browse/LUCENE-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14614606#comment-14614606
]
Trejkaz commented on LUCENE-5956:
-
how valuable is it to support older than N-1 indexes,
Trejkaz created LUCENE-6658:
---
Summary: IndexUpgrader doesn't upgrade an index if it has zero
segments
Key: LUCENE-6658
URL: https://issues.apache.org/jira/browse/LUCENE-6658
Project: Lucene - Core
Trejkaz created LUCENE-6655:
---
Summary: StandardTokenizerFactory constructor fails if the passed
in map is immutable
Key: LUCENE-6655
URL: https://issues.apache.org/jira/browse/LUCENE-6655
Project: Lucene -
Trejkaz created LUCENE-6656:
---
Summary: StandardTokenizer.close() can leave the object in an
uncloseable state
Key: LUCENE-6656
URL: https://issues.apache.org/jira/browse/LUCENE-6656
Project: Lucene - Core
[
https://issues.apache.org/jira/browse/LUCENE-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trejkaz updated LUCENE-6655:
Summary: All analysis factory constructors fail if the passed in map is
immutable (was:
[
https://issues.apache.org/jira/browse/LUCENE-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14603872#comment-14603872
]
Trejkaz commented on LUCENE-6542:
-
It works something like this:
{code:java}
import
[
https://issues.apache.org/jira/browse/LUCENE-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14592934#comment-14592934
]
Trejkaz commented on LUCENE-6584:
-
Trejkaz created LUCENE-6584:
---
Summary: Docs on StandardTokenizer don't mention the behaviour
change in Version.LUCENE_4_7_0
Key: LUCENE-6584
URL: https://issues.apache.org/jira/browse/LUCENE-6584
Project:
Trejkaz created LUCENE-6542:
---
Summary: FSDirectory throws AccessControlException unless you
grant write access to the index
Key: LUCENE-6542
URL: https://issues.apache.org/jira/browse/LUCENE-6542
Project:
[
https://issues.apache.org/jira/browse/LUCENE-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trejkaz updated LUCENE-6542:
Attachment: patch.txt
Patch guards the Files.createDirectories call with a Files.exists check.
Trejkaz created LUCENE-6503:
---
Summary: QueryWrapperFilter discards the IndexReaderContext when
delegating to the wrapped query
Key: LUCENE-6503
URL: https://issues.apache.org/jira/browse/LUCENE-6503
Trejkaz created LUCENE-6498:
---
Summary: RegexpQueryNode inconsistent treatment of begin and end
parameters
Key: LUCENE-6498
URL: https://issues.apache.org/jira/browse/LUCENE-6498
Project: Lucene - Core
Trejkaz created LUCENE-5905:
---
Summary: Different behaviour of JapaneseAnalyzer at indexing time
vs. at search time
Key: LUCENE-5905
URL: https://issues.apache.org/jira/browse/LUCENE-5905
Project: Lucene -
Trejkaz created LUCENE-5676:
---
Summary: QueryNodeImpl is too mutable
Key: LUCENE-5676
URL: https://issues.apache.org/jira/browse/LUCENE-5676
Project: Lucene - Core
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/LUCENE-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13956008#comment-13956008
]
Trejkaz commented on LUCENE-2327:
-
I have an almost identical stack trace from v3.6, but
[
https://issues.apache.org/jira/browse/LUCENE-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13878608#comment-13878608
]
Trejkaz commented on LUCENE-3565:
-
The expectation in the test case aside, what Lucene
[
https://issues.apache.org/jira/browse/LUCENE-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13878615#comment-13878615
]
Trejkaz commented on LUCENE-3565:
-
And actually, if you read my original comment from
[
https://issues.apache.org/jira/browse/LUCENE-3355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13879412#comment-13879412
]
Trejkaz commented on LUCENE-3355:
-
Looks like this has been fixed at some point between
[
https://issues.apache.org/jira/browse/LUCENE-3565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13877912#comment-13877912
]
Trejkaz commented on LUCENE-3565:
-
Seems to have been fixed in 3.6.2.
[
https://issues.apache.org/jira/browse/LUCENE-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trejkaz updated LUCENE-5186:
Attachment: LUCENE-5186.patch
Since it's pretty trivial. :)
Add
Trejkaz created LUCENE-5186:
---
Summary: Add CachingWrapperFilter.getFilter()
Key: LUCENE-5186
URL: https://issues.apache.org/jira/browse/LUCENE-5186
Project: Lucene - Core
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/LUCENE-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13591331#comment-13591331
]
Trejkaz commented on LUCENE-1206:
-
I think this would still be useful. The workaround of
[
https://issues.apache.org/jira/browse/LUCENE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trejkaz closed LUCENE-1245.
---
Resolution: Not A Problem
I guess this resolution is correct. We have stopped using the basic query
parser
Trejkaz created LUCENE-4073:
---
Summary: Lucene puts output of svnversion into a property even if
svnversion failed
Key: LUCENE-4073
URL: https://issues.apache.org/jira/browse/LUCENE-4073
Project: Lucene -
Support for a SpanNotNearQuery
Key: LUCENE-3370
URL: https://issues.apache.org/jira/browse/LUCENE-3370
Project: Lucene - Java
Issue Type: New Feature
Components: core/search
Reporter:
Support for a SpanAndQuery / SpanAllNearQuery
-
Key: LUCENE-3371
URL: https://issues.apache.org/jira/browse/LUCENE-3371
Project: Lucene - Java
Issue Type: New Feature
Components:
[
https://issues.apache.org/jira/browse/LUCENE-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082284#comment-13082284
]
Trejkaz commented on LUCENE-3371:
-
Yeah, it would provide a span much like a normal
[
https://issues.apache.org/jira/browse/LUCENE-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082708#comment-13082708
]
Trejkaz commented on LUCENE-3370:
-
That's not a bad idea.
Some care should be taken
[
https://issues.apache.org/jira/browse/LUCENE-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082710#comment-13082710
]
Trejkaz commented on LUCENE-3371:
-
That sounds about right.
I had another thought
GroupQueryNodeProcessor doesn't recursively process children of custom query
nodes
--
Key: LUCENE-3367
URL: https://issues.apache.org/jira/browse/LUCENE-3367
Project:
StandardTokenizer disposes of Hiragana combining mark dakuten instead of
attaching it to the character it belongs to
Key: LUCENE-3358
URL:
ParametricRangeQueryNodeProcessor support for time zones
Key: LUCENE-3352
URL: https://issues.apache.org/jira/browse/LUCENE-3352
Project: Lucene - Java
Issue Type: New Feature
ParametricRangeQueryNodeProcessor uses incorrect logic at the lower bound
-
Key: LUCENE-3353
URL: https://issues.apache.org/jira/browse/LUCENE-3353
Project: Lucene - Java
Incorrect behaviour of MultiFieldQueryNodeProcessor when default operator is
'AND'
--
Key: LUCENE-3355
URL: https://issues.apache.org/jira/browse/LUCENE-3355
Project:
MoreLikeThis reuses a reader after it has already closed it
---
Key: LUCENE-3326
URL: https://issues.apache.org/jira/browse/LUCENE-3326
Project: Lucene - Java
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LUCENE-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13033860#comment-13033860
]
Trejkaz commented on LUCENE-1149:
-
Is there an issue which this one is a true duplicate
I wish Lucene query explanations were easier to localise
Key: LUCENE-3013
URL: https://issues.apache.org/jira/browse/LUCENE-3013
Project: Lucene - Java
Issue Type: Wish
[
https://issues.apache.org/jira/browse/LUCENE-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12986848#action_12986848
]
Trejkaz commented on LUCENE-879:
The workaround of using an ID turns out to be very slow.
[
https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12935765#action_12935765
]
Trejkaz commented on LUCENE-2348:
-
That is exactly the workaround we performed for our own
[
https://issues.apache.org/jira/browse/LUCENE-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12935891#action_12935891
]
Trejkaz commented on LUCENE-2506:
-
bq. What if Filter.getDocIDSet also received the top
[
https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12935894#action_12935894
]
Trejkaz commented on LUCENE-2348:
-
It used to do the work in getDocIdSet() - it wasn't us
[
https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12934214#action_12934214
]
Trejkaz commented on LUCENE-2348:
-
Field collapsing has different semantics which don't
[
https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933659#action_12933659
]
Trejkaz commented on LUCENE-2348:
-
Another way of solving this particular issue would be
[
https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933222#action_12933222
]
Trejkaz commented on LUCENE-2348:
-
Finally got around to checking this out today, and it
IndexWriter.isLocked() fails on a read-only directory
-
Key: LUCENE-2607
URL: https://issues.apache.org/jira/browse/LUCENE-2607
Project: Lucene - Java
Issue Type: Bug
Affects Versions:
[
https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12881500#action_12881500
]
Trejkaz commented on LUCENE-2348:
-
That does solve the specific issue I resolved... I
[
https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12881500#action_12881500
]
Trejkaz edited comment on LUCENE-2348 at 6/22/10 9:01 PM:
--
That
[
https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12874841#action_12874841
]
Trejkaz commented on LUCENE-2348:
-
That change broke nearly all our own filters. We have
[
https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12874370#action_12874370
]
Trejkaz commented on LUCENE-2348:
-
What you describe is precisely the problem. It will
[
https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12874373#action_12874373
]
Trejkaz commented on LUCENE-2348:
-
I attempted to make a test but it fails with matching 0
DuplicateFilter incorrectly handles multiple calls to getDocIdSet for segment
readers
-
Key: LUCENE-2348
URL: https://issues.apache.org/jira/browse/LUCENE-2348
[
https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trejkaz updated LUCENE-2348:
Component/s: (was: Search)
contrib/*
Changing to contrib, only just realised it was
RegexQuery matches terms the input regex doesn't actually match
---
Key: LUCENE-1683
URL: https://issues.apache.org/jira/browse/LUCENE-1683
Project: Lucene - Java
Issue Type:
[
https://issues.apache.org/jira/browse/LUCENE-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718270#action_12718270
]
Trejkaz commented on LUCENE-1683:
-
I screwed up the formatting. Fixed version:
{code}
[
https://issues.apache.org/jira/browse/LUCENE-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12711850#action_12711850
]
Trejkaz commented on LUCENE-1646:
-
Our improvements are (so far) specific to our subclass
[
https://issues.apache.org/jira/browse/LUCENE-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12711412#action_12711412
]
Trejkaz commented on LUCENE-1646:
-
I guess that's true if you look at exceptions as a
QueryParser throws new exceptions even if custom parsing logic threw a better
one
-
Key: LUCENE-1646
URL: https://issues.apache.org/jira/browse/LUCENE-1646
Project:
[
https://issues.apache.org/jira/browse/LUCENE-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12676521#action_12676521
]
Trejkaz commented on LUCENE-893:
Someone else on my team did some benchmarks for a query
[
https://issues.apache.org/jira/browse/LUCENE-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604701#action_12604701
]
Trejkaz commented on LUCENE-1290:
-
To answer Doug's initial question, yes, we are using
1 - 100 of 118 matches
Mail list logo
