[
https://issues.apache.org/jira/browse/LUCENE-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184792#comment-13184792
]
Joe Cabrera commented on LUCENE-2172:
-
The build.xml builds correctly with ant. Is th
[
https://issues.apache.org/jira/browse/LUCENE-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera resolved LUCENE-3686.
Resolution: Fixed
Fix Version/s: 4.0
3.6
Patch looks good (many formatti
[
https://issues.apache.org/jira/browse/LUCENE-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-3690:
Attachment: LUCENE-3690.patch
Added a {{}} section test, and fixed the CDATA section
handling.
[
https://issues.apache.org/jira/browse/LUCENE-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184750#comment-13184750
]
Steven Rowe edited comment on LUCENE-2208 at 1/12/12 6:23 AM:
-
[
https://issues.apache.org/jira/browse/LUCENE-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184750#comment-13184750
]
Steven Rowe commented on LUCENE-2208:
-
The JFlex-based HTMLStripCharFilter replacemen
[
https://issues.apache.org/jira/browse/LUCENE-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184749#comment-13184749
]
Steven Rowe commented on LUCENE-3690:
-
One other thing left to do: I added javadocs t
[
https://issues.apache.org/jira/browse/LUCENE-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184745#comment-13184745
]
Steven Rowe commented on LUCENE-3690:
-
Left to do:
# Accept supplementary characters
[
https://issues.apache.org/jira/browse/LUCENE-3690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-3690:
Attachment: LUCENE-3690.patch
Patch implementing the idea.
This patch just creates a new class na
JFlex-based HTMLStripCharFilter replacement
---
Key: LUCENE-3690
URL: https://issues.apache.org/jira/browse/LUCENE-3690
Project: Lucene - Java
Issue Type: New Feature
Components: modules/anal
[
https://issues.apache.org/jira/browse/SOLR-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184684#comment-13184684
]
Mark Miller commented on SOLR-2191:
---
bq. Logging last means your missing context for extr
On Jan 11, 2012, at 12:03, Robert Muir wrote:
> On Wed, Jan 11, 2012 at 2:57 PM, Yonik Seeley
> wrote:
>
>> If someone does want to work on a large 5.0 feature *right now* as
>> opposed to working on 4.0, then they can create a branch and merge
>> that later.
>>
>
> No, they can commit it to
[
https://issues.apache.org/jira/browse/SOLR-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184657#comment-13184657
]
Yonik Seeley commented on SOLR-2191:
bq. I think it's more of a project level problem -
[
https://issues.apache.org/jira/browse/SOLR-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184645#comment-13184645
]
Erick Erickson commented on SOLR-3032:
--
Should the deprecations be back-ported to 3.x?
[
https://issues.apache.org/jira/browse/SOLR-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson reassigned SOLR-2124:
Assignee: Erick Erickson
> SEVERE exceptions are being logged for expected PingRequestHa
Deprecate logOnce from SolrException
Key: SOLR-3032
URL: https://issues.apache.org/jira/browse/SOLR-3032
Project: Solr
Issue Type: Improvement
Reporter: Erick Erickson
Assignee: Er
[
https://issues.apache.org/jira/browse/SOLR-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184632#comment-13184632
]
Erick Erickson commented on SOLR-3022:
--
James:
I wasn't advocating going through and
[
https://issues.apache.org/jira/browse/SOLR-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184621#comment-13184621
]
Mark Miller commented on SOLR-2358:
---
I've made the above change in the branch.
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/12099/
1 tests failed.
REGRESSION: org.apache.lucene.index.TestOmitNorms.testOmitNormsCombos
Error Message:
actual array was null
Stack Trace:
junit.framework.AssertionFailedError: actual array was null
at
org.apache.luc
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/1489/
1 tests failed.
REGRESSION: org.apache.lucene.index.TestOmitNorms.testOmitNormsCombos
Error Message:
actual array was null
Stack Trace:
junit.framework.AssertionFailedError: actual array was null
at
org.apach
[
https://issues.apache.org/jira/browse/SOLR-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184559#comment-13184559
]
Mark Miller commented on SOLR-2880:
---
bq. I'm seeing OverseerTest fail quite often now:
I
[
https://issues.apache.org/jira/browse/SOLR-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184537#comment-13184537
]
Mark Miller commented on SOLR-2358:
---
Came up with a conversation with a user in #solr IRC
[
https://issues.apache.org/jira/browse/SOLR-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184471#comment-13184471
]
Antony Stubbs commented on SOLR-2667:
-
It seems the ui for dataimporthandler doesn't pa
On Jan 11, 2012, at 3:07 PM, Michael McCandless wrote:
> I'd think we could cut a 4.0 alpha today, after branching.
I'm hoping we can commit the rest of the SolrCloud stuff by next week. We have
been marching strong towards that goal for a month
now when I first mentioned those intentions in t
[
https://issues.apache.org/jira/browse/SOLR-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1318#comment-1318
]
Mark Miller commented on SOLR-2191:
---
bq. personal problem that should be dealt with on a
[
https://issues.apache.org/jira/browse/SOLR-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184441#comment-13184441
]
Antony Stubbs commented on SOLR-1277:
-
What happened in regards to multicore support an
[
https://issues.apache.org/jira/browse/SOLR-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184417#comment-13184417
]
Erick Erickson commented on SOLR-2191:
--
What does "remove logOnce" mean in this case?
[
https://issues.apache.org/jira/browse/LUCENE-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184412#comment-13184412
]
Steven Rowe commented on LUCENE-3167:
-
The way forward, as I see it:
# Make a new p
[
https://issues.apache.org/jira/browse/SOLR-3030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Monica Skidmore updated SOLR-3030:
--
Attachment: SOLR-3030.patch
> StopTermTypesFilter and Factory allows filtering based on the
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-3.x-java7/1506/
1 tests failed.
REGRESSION:
org.apache.solr.client.solrj.embedded.LargeVolumeJettyTest.testMultiThreaded
Error Message:
java.lang.AssertionError: Some threads threw uncaught exceptions!
Stack Trace:
java.lang.RuntimeEx
[
https://issues.apache.org/jira/browse/SOLR-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson reassigned SOLR-2191:
Assignee: Erick Erickson (was: Mark Miller)
> Change SolrException cstrs that take Thro
[
https://issues.apache.org/jira/browse/LUCENE-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184397#comment-13184397
]
Steven Rowe commented on LUCENE-3167:
-
bq. Is [#comment-13113588] still the only prob
[
https://issues.apache.org/jira/browse/SOLR-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated SOLR-3022:
-
Attachment: SOLR-3022.patch
Here's a patch that changes both of the "problem constructors" by leaving
"al
[
https://issues.apache.org/jira/browse/LUCENE-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184387#comment-13184387
]
Robert Muir commented on LUCENE-3689:
-
I'm not sure we should rename finish to flush.
I am trying to extract anything that is a field "IsStored" for use in
filtering lists
e.g. When you access an ecommerce site and you get the filter lists down
the left hand side, I wanted to store anything that I wanted filtering
and when I performed a search I wanted to create a lookup list f
[
https://issues.apache.org/jira/browse/LUCENE-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184382#comment-13184382
]
Ryan Hill commented on LUCENE-3167:
---
Is [#comment-13113588] still the only problem with
[
https://issues.apache.org/jira/browse/SOLR-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184359#comment-13184359
]
Erick Erickson edited comment on SOLR-3022 at 1/11/12 8:49 PM:
--
[
https://issues.apache.org/jira/browse/SOLR-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184359#comment-13184359
]
Erick Erickson commented on SOLR-3022:
--
Mark:
You're right, this is totally related.
Having some interest in this issue, may I suggest setting a branch date? On
the agreed-upon date, a branch is made. After that date, commits go to trunk
and (maybe) are pulled up into the 4.0 branch. If the date is oh, say, 1 week
away, people can plan accordingly to yield a relatively stable
[
https://issues.apache.org/jira/browse/LUCENE-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184346#comment-13184346
]
Robert Muir commented on LUCENE-3687:
-
I havent done a full review but with the typo
On Wed, Jan 11, 2012 at 3:07 PM, Michael McCandless
wrote:
>
> I'd think we could cut a 4.0 alpha today, after branching.
>
How? the packaging for modules is totally hosed for example: how would
we even package such a thing?
Also when we push out alpha/beta/etc shouldn't we at the minimum say
'a
On Wed, Jan 11, 2012 at 2:41 PM, Yonik Seeley
wrote:
> From the other comments in this thread, it feels like an actual 4.0
> would be months off.
I'd think we could cut a 4.0 alpha today, after branching.
Sure it'd have caveats (certain issues are in progress, APIs may
change, etc.), but that's
On Wed, Jan 11, 2012 at 2:57 PM, Yonik Seeley
wrote:
> If someone does want to work on a large 5.0 feature *right now* as
> opposed to working on 4.0, then they can create a branch and merge
> that later.
>
No, they can commit it to trunk.
If we want 4.x to be stabilized, then we need to branch
On Wed, Jan 11, 2012 at 2:51 PM, Simon Willnauer
wrote:
> On Wed, Jan 11, 2012 at 8:41 PM, Yonik Seeley
>> Branching so soon would just cause that much more merging work, which
>> would quickly get difficult if people made meaningful changes to 5x.
>> Are there really any large 5x changes that peo
On Wed, Jan 11, 2012 at 8:41 PM, Yonik Seeley
wrote:
> On Wed, Jan 11, 2012 at 2:31 PM, Simon Willnauer
> wrote:
>> On Sun, Jan 8, 2012 at 8:05 PM, Robert Muir wrote:
>>> 2. copy trunk to branch_4x and call it our 'stable branch' (even
>>> though it isn't, not yet).
>>
>> +1 I think we should ac
On Wed, Jan 11, 2012 at 2:31 PM, Simon Willnauer
wrote:
> On Sun, Jan 8, 2012 at 8:05 PM, Robert Muir wrote:
>> 2. copy trunk to branch_4x and call it our 'stable branch' (even
>> though it isn't, not yet).
>
> +1 I think we should actually do that soonish, is there anything which
> keeps us from
+1 to getting 4.0 alpha out asap for user feedback. We have
incredible (but largely unused) new features in 4.0.
I like the plan to cut branch for 4.0, and trunk becomes future 5.0,
and 3.6.x becomes bugfix only, as an atomic event :)
Then we should try to focus on prepping/iterating on the 4.0
Allow disabling of leading wildcards in ExtendedDismaxQParser (edismax)
---
Key: SOLR-3031
URL: https://issues.apache.org/jira/browse/SOLR-3031
Project: Solr
Issue Type: New
StopTermTypesFilter and Factory allows filtering based on the TermTypeAttribute
---
Key: SOLR-3030
URL: https://issues.apache.org/jira/browse/SOLR-3030
Project: Solr
On Sun, Jan 8, 2012 at 8:05 PM, Robert Muir wrote:
> On Sun, Jan 8, 2012 at 1:36 PM, Simon Willnauer
> wrote:
>>>
>>> From the tests/bugfixing perspective, on trunk its not hard to dig
>>> into stuff here and there and find lots of really horrible bugs that
>>> exist in trunk-only. This is a sign
[
https://issues.apache.org/jira/browse/SOLR-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184305#comment-13184305
]
Mark Miller commented on SOLR-2880:
---
I'm seeing OverseerTest fail quite often now:
{nofo
[
https://issues.apache.org/jira/browse/SOLR-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184299#comment-13184299
]
Mark Miller commented on SOLR-2191:
---
The issue needs to be updated. I think the right app
[
https://issues.apache.org/jira/browse/LUCENE-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184300#comment-13184300
]
Simon Willnauer commented on LUCENE-3687:
-
what a typo... s/omit/emit in the patc
Hi, this is my first post in this forum! :-)
I'm Italian and sorry for my bad english :-(
I developing a search engine in java with lucene in eclipse.
I've a problem: I run a search for a terms, after I want know the first five
keywords in order by frequency on subset of document resulting from
[
https://issues.apache.org/jira/browse/SOLR-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Dyer updated SOLR-3022:
-
Attachment: SOLR-3022.patch
I had noticed that problem constructor in SolrException also. I think it need
[
https://issues.apache.org/jira/browse/SOLR-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184262#comment-13184262
]
Erick Erickson commented on SOLR-3022:
--
Looking at this a bit more, there are a couple
[
https://issues.apache.org/jira/browse/SOLR-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184256#comment-13184256
]
Michael Dodsworth commented on SOLR-3017:
-
all reviews welcome (sorry to pester)
[
https://issues.apache.org/jira/browse/LUCENE-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184243#comment-13184243
]
Robert Muir commented on LUCENE-3305:
-
{quote}
The middle dot ・ seems to have been re
[
https://issues.apache.org/jira/browse/SOLR-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antony Stubbs updated SOLR-3029:
Issue Type: Bug (was: Improvement)
> Poor json formatting of spelling collation info
>
[
https://issues.apache.org/jira/browse/SOLR-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184238#comment-13184238
]
Antony Stubbs commented on SOLR-3029:
-
I imagine this will also be in 3.5?
[
https://issues.apache.org/jira/browse/SOLR-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antony Stubbs updated SOLR-3029:
Summary: Poor json formatting of spelling collation info (was: Poor json
formatting of spelling col
Some early feedback for those who are curious
We went live on Jan 7, so Jan 8 is first official full day. lucene.a.o,
lucene.a.o/java and lucene.a.o/solr all have analytics tracking codes. Wiki
pages do not. Pylucene and Open Relevance also do not. Nor do specific Lucene
release documentati
[
https://issues.apache.org/jira/browse/LUCENE-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184206#comment-13184206
]
Christian Moen commented on LUCENE-3305:
The middle dot character (nakaguro) is t
On Wed, Jan 11, 2012 at 9:31 AM, Simon Willnauer
wrote:
> On Wed, Jan 11, 2012 at 1:10 PM, Michael McCandless
> wrote:
>> Thanks Simon!
>>
>> Can you also fixup that confusing comment in DocValuesConsumer.merge?
>> Ie if an exception is thrown, how are we ensuring finish/abort/close
>> called...?
[
https://issues.apache.org/jira/browse/SOLR-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184197#comment-13184197
]
Yonik Seeley commented on SOLR-3029:
Looks like someone accidentally used a NamedList (
[
https://issues.apache.org/jira/browse/LUCENE-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-3453:
--
Assignee: Michael McCandless (was: Chris Male)
> remove IndexDocValuesFie
[
https://issues.apache.org/jira/browse/LUCENE-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184191#comment-13184191
]
Michael McCandless commented on LUCENE-3602:
Looking great! I think we are g
[
https://issues.apache.org/jira/browse/LUCENE-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184186#comment-13184186
]
Robert Muir commented on LUCENE-3305:
-
Thank you for fixing that bug!
By the way, I'
[
https://issues.apache.org/jira/browse/LUCENE-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-3453:
---
Attachment: LUCENE-3453.patch
I'm taking a stab at this one... here's an initial rou
[
https://issues.apache.org/jira/browse/SOLR-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184183#comment-13184183
]
Mark Miller commented on SOLR-2880:
---
I wonder if it makes sense for the overseer to chang
Poor json formatting of spelling collatoin info
---
Key: SOLR-3029
URL: https://issues.apache.org/jira/browse/SOLR-3029
Project: Solr
Issue Type: Improvement
Components: spellchecker
[
https://issues.apache.org/jira/browse/SOLR-2667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184173#comment-13184173
]
Mark Miller commented on SOLR-2667:
---
One thing missing from the old UI for the ZooKeeper
[
https://issues.apache.org/jira/browse/SOLR-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antony Stubbs closed SOLR-3025.
---
Resolution: Duplicate
Duplicate of SOLR-2555
Thanks James.
> spellcheck.onlyMorePopu
I know that problem, this is why I responded (I did accidentally commit this
in the past, too). Maybe we should have a param passed to the
common-compile-javac task, to override the Solr compilation.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetap
I dont have the ability to remove and test it at the moment, but you could
probably remove it.
As a side note there are some cls compliant issues with lucene.net - many
variables share names with methods only differing by case - which in vb could
cause problems. It'll work just take care to rea
[
https://issues.apache.org/jira/browse/SOLR-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184128#comment-13184128
]
James Dyer commented on SOLR-3025:
--
This appears to be a duplicate of SOLR-2555. Also see
Heh - I always have to apply that locally to find compilation errors
(otherwise they are buried in warnings).
Always end up committing it accidentally once in a while.
I should try to figure out if it can be overridden just for solr.
-Yonik
http://www.lucidimagination.com
On Wed, Jan 11, 2012 at
LOL!
> --- lucene/dev/branches/solrcloud/lucene/common-build.xml (original)
> +++ lucene/dev/branches/solrcloud/lucene/common-build.xml Wed Jan 11
> +++ 14:48:23 2012
> @@ -818,8 +818,6 @@
>
>
> -
> -
>
>
>
Uwe
-
[
https://issues.apache.org/jira/browse/LUCENE-3689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-3689:
Attachment: LUCENE-3689.patch
here is a patch that adds closeable to DocValuesConsumer and
On Wed, Jan 11, 2012 at 1:10 PM, Michael McCandless
wrote:
> Thanks Simon!
>
> Can you also fixup that confusing comment in DocValuesConsumer.merge?
> Ie if an exception is thrown, how are we ensuring finish/abort/close
> called...? Thanks.
I opened https://issues.apache.org/jira/browse/LUCENE-3
DocValuesConsumer should implement closeable and release resource in close
instead of during finish / flush
---
Key: LUCENE-3689
URL: https://issues.apache.org
Call for Submission Berlin Buzzwords 2012 - Search, Store, Scale --
June 4 / 5. 2012
The event will comprise presentations on scalable data processing. We
invite you to submit talks on the topics:
* IR / Search - Lucene, Solr, katta, ElasticSearch or comparable solutions
* NoSQL - like CouchDB,
[
https://issues.apache.org/jira/browse/LUCENE-3688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sivan Yogev updated LUCENE-3688:
Attachment: LUCENE-association-buckets.patch
> Bucketing of association value of a certain cat
Bucketing of association value of a certain category
Key: LUCENE-3688
URL: https://issues.apache.org/jira/browse/LUCENE-3688
Project: Lucene - Java
Issue Type: Improvement
Compon
Thanks, Erik, this is not ideal but it will work for my purposes. But it seems
a shame that the whole SolrCoreAware setup as it was designed turned out to be
so problematic.
Karl
-Original Message-
From: ext Erik Hatcher [mailto:erik.hatc...@gmail.com]
Sent: Wednesday, January 11, 201
Thanks Simon!
Can you also fixup that confusing comment in DocValuesConsumer.merge?
Ie if an exception is thrown, how are we ensuring finish/abort/close
called...? Thanks.
Mike McCandless
http://blog.mikemccandless.com
On Wed, Jan 11, 2012 at 4:12 AM, Simon Willnauer
wrote:
> I committed a fi
[
https://issues.apache.org/jira/browse/LUCENE-3687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-3687:
Attachment: LUCENE-3687.patch
here is a first patch allowing similarity be more flexible w
Allow similarity to encode norms other than a single byte
-
Key: LUCENE-3687
URL: https://issues.apache.org/jira/browse/LUCENE-3687
Project: Lucene - Java
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/LUCENE-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183961#comment-13183961
]
Uwe Schindler commented on LUCENE-3305:
---
Committed development branch revision: 122
[
https://issues.apache.org/jira/browse/LUCENE-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183958#comment-13183958
]
Uwe Schindler commented on LUCENE-3305:
---
Hi Christian,
thanks for the fix. I will a
Hello,
I can't build the "Contrib.FastVectorHighlighter" project from the
current lucene 2.9.4 package. My main project is a Visual Basic .NET
Winforms application. This application has a direct "project reference"
to the "Contrib.FastVectorHighlighter" project. Unfortunaly the
"Contrib.FastV
[
https://issues.apache.org/jira/browse/LUCENE-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn van Groningen updated LUCENE-3602:
--
Fix Version/s: 4.0
3.6
> Add join query to Lucene
> ---
[
https://issues.apache.org/jira/browse/LUCENE-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Moen updated LUCENE-3305:
---
Attachment: wordid0.patch
Patch to fix zero wordid issue. Backport of fix from kuromoji 0.7
[
https://issues.apache.org/jira/browse/LUCENE-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera reassigned LUCENE-3686:
--
Assignee: Shai Erera
> EnhancementsPayloadIterator.getCategoryData(CategoryEnhancement) pr
I committed a fix for this. Seems this was a simple text problem.
simon
On Tue, Jan 10, 2012 at 6:27 PM, Michael McCandless
wrote:
> I think we must be missing a try/finally somewhere... the test is
> pretty evil (throws random exceptions up during indexing).
>
> Hmm I see this comment in DocVa
[
https://issues.apache.org/jira/browse/LUCENE-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sivan Yogev updated LUCENE-3686:
Lucene Fields: New,Patch Available (was: New)
> EnhancementsPayloadIterator.getCategoryData(C
[
https://issues.apache.org/jira/browse/LUCENE-3686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sivan Yogev updated LUCENE-3686:
Attachment: LUCENE-3686.patch
My first Lucene patch :)
> EnhancementsPayloadItera
EnhancementsPayloadIterator.getCategoryData(CategoryEnhancement) problematic
usage of Object.equals()
-
Key: LUCENE-3686
URL: https://issues.apache.org/jira/browse
Karl - you can get the core from SolrQueryRequest#getCore(), with
SolrQueryRequest being passed into QParserPlugin#createParser.
Erik
On Jan 11, 2012, at 01:29 ,
wrote:
> "SolrCoreAware" and "CloseHook" are related in that you need a SolrCore
> object in order to call SolrCore.addC
"SolrCoreAware" and "CloseHook" are related in that you need a SolrCore object
in order to call SolrCore.addCloseHook(). Indeed, the javadoc for the
CloseHook interface states that the expected way you are supposed to use this
in a plugin is via something like this:
public void inform(SolrCore
99 matches
Mail list logo
