[
https://issues.apache.org/jira/browse/LUCENE-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12756432#action_12756432
]
Thomas Becker commented on LUCENE-1911:
---
Thanks for the patch. Issue can be closed I
[
https://issues.apache.org/jira/browse/LUCENE-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Becker updated LUCENE-1911:
--
Attachment: lucene_29_newapi_patched.png
HotSpots - lucene 2.9-RC4 patched
When using
[
https://issues.apache.org/jira/browse/LUCENE-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1911:
--
Attachment: LUCENE-1911.patch
Thanks Thomas!
Attached is a improved patch, that uses
[
https://issues.apache.org/jira/browse/LUCENE-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1912:
--
Assignee: Michael McCandless
FastVectorHighlighter: latter terms cannot be
[
https://issues.apache.org/jira/browse/LUCENE-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12756474#action_12756474
]
Michael McCandless commented on LUCENE-1912:
Changes look good; Mark is it OK
[
https://issues.apache.org/jira/browse/LUCENE-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12756490#action_12756490
]
Mark Miller commented on LUCENE-1912:
-
+1 on commit.
FastVectorHighlighter: latter
[
https://issues.apache.org/jira/browse/LUCENE-1912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-1912.
Resolution: Fixed
Thanks Koji!
FastVectorHighlighter: latter terms cannot be
[
https://issues.apache.org/jira/browse/LUCENE-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-1911.
---
Resolution: Fixed
Committed revision: 816154. Thanks Thomas for reporting this!
When
FastVectorHighlighter: AIOOBE occurs if one PhraseQuery is contained by another
PhraseQuery
---
Key: LUCENE-1913
URL: https://issues.apache.org/jira/browse/LUCENE-1913
[
https://issues.apache.org/jira/browse/LUCENE-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Sekiguchi updated LUCENE-1913:
---
Attachment: LUCENE-1913.patch
The fix and the test case, the test case produces AIOOBE if
[
https://issues.apache.org/jira/browse/LUCENE-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned LUCENE-1913:
---
Assignee: Mark Miller
Another one! Well, since your country produced Cowboy Bebop, I guess
mikemcc...@apache.org wrote:
+ * LUCENE-1912: Fix fast-vector-highlighter issue when two or more
+ terms are concatenated (Koji Sekiguchi via Mike McCandless)
+
New features
But it wasn't in a release yet ... man, you got me started on this
Changes stuff, and now your going to
Hi guys:
I am trying to figure how to add the ability to create custom segment
files. Hopefully it is possible to create a plugin framework where one can
provide some sort of callback to add to a segment given a doc and provide
some sort of merge logic. This is in light of the flexible
[
https://issues.apache.org/jira/browse/LUCENE-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved LUCENE-1913.
-
Resolution: Fixed
Lucene Fields: [New, Patch Available] (was: [New])
allow for custom segment files
--
Key: LUCENE-1914
URL: https://issues.apache.org/jira/browse/LUCENE-1914
Project: Lucene - Java
Issue Type: Improvement
Components: Index
Affects Versions: 2.9
Add static openInput(File,...) methods to all FSDirectory implementations
-
Key: LUCENE-1915
URL: https://issues.apache.org/jira/browse/LUCENE-1915
Project: Lucene - Java
I'm actively working on LUCENE-1458, to enable differenct codecs for
reading/writing the terms dict and doc/freq/prox/payload postings.
I'm working now towards getting PforDelta working...
However, that change doesn't [yet] do anything for norms, stored
fields nor term vectors.
Can you describe
[
https://issues.apache.org/jira/browse/LUCENE-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1916:
Attachment: LUCENE-1916.patch
smartcn HHMM doc translation
smartcn HHMM doc translation
Key: LUCENE-1916
URL: https://issues.apache.org/jira/browse/LUCENE-1916
Project: Lucene - Java
Issue Type: Task
Components: Javadocs
Reporter: Robert Muir
Mark Miller (JIRA) wrote:
whether we do an RC or not after this I don't know.
Technically, if we don't want to - its not required. All thats required is
that we get the 3 votes and no -1 votes with valid tech arguments.
Whoops - I was wrong - you can't veto a release. You just need 3
How do I sign all the maven artifacts?
Please tell me I dont have to sign every maven artificat individually.
Because that would be insane. What is the command to just sign them in
one shot?
Sign the release (see Step-By-Step Guide to Mirroring Releases for more
information). Also sign all Maven
I wrote a simple Python script to do it (attached).
You may have to tweak it a bit (eg change the CODE SIGNING KEY part to
match your key). It prompts for your passphrase the first time it
needs it... and also verifies sigs if they are already present.
Mike
On Thu, Sep 17, 2009 at 12:15 PM,
Hello,
I'm in the process of implementing a project using Lucene Spatial and I
had a couple (hopefully quick) questions:
1) Is anyone currently working on adding arbitrary geo shape handling,
or has done so in code that is not part of the contrib? I need to
implement functionality to
Don't get me started with spatial - they came, they dumped it, they left ;)
You will not fall out of sync in short order, especially if you work
with JIRA so others know what you are doing. The guys that originally
came in and added spatial apparently have it working for their needs and
havn't
Hi,
Started using it actively.
Soon realized that it was unsupported alpha code and didn't fit in the
high profile environment we have.
Now using my own code to do bounding box / proximity Lucene searches with
GeoHashes, faster, more efficient.
My advice, browse the code, get inspired, write
Wouter Heijke wrote:
My advice, browse the code, get inspired, write your own code only better.
Wouter
Evil dude - donate those improvements back!
--
- Mark
http://www.lucidimagination.com
-
To unsubscribe, e-mail:
Adding empty ParallelReader indexes to an IndexWriter may cause
ArrayIndexOutOfBoundsException or NoSuchElementException
Key: LUCENE-1918
[
https://issues.apache.org/jira/browse/LUCENE-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Kohlschütter updated LUCENE-1918:
---
Attachment: ParallelReaderWithEmptyIndex.patch
So in the section: Building the Release artifacts
bullet 8: Make sure that for each release file an md5 checksum file exists.
At this step in the process, the zip/tars do not have an md5 checksum
file that exists (at least not on *my* computer). The Maven artifacts do.
Kosher? Adequate?
Note, I also worked in some stuff into Solr, but it requires entering
passwords a bunch of times. Mike's script avoids that.
On Sep 17, 2009, at 9:21 AM, Michael McCandless wrote:
I wrote a simple Python script to do it (attached).
You may have to tweak it a bit (eg change the CODE SIGNING
On Sep 17, 2009, at 3:07 PM, Mark Miller wrote:
So in the section: Building the Release artifacts
bullet 8: Make sure that for each release file an md5 checksum file
exists.
At this step in the process, the zip/tars do not have an md5 checksum
file that exists (at least not on *my*
Grant Ingersoll wrote:
On Sep 17, 2009, at 3:07 PM, Mark Miller wrote:
So in the section: Building the Release artifacts
bullet 8: Make sure that for each release file an md5 checksum file
exists.
At this step in the process, the zip/tars do not have an md5 checksum
file that exists (at
On Thu, Sep 17, 2009 at 6:42 PM, Mark Miller markrmil...@gmail.com wrote:
Okay - I see the checksum stuff in build.xml - it just doesn't appear to
be working in my favor at the moment ...
You can just use md5sum from the command line too.
-Yonik
http://www.lucidimagination.com
Yonik Seeley wrote:
On Thu, Sep 17, 2009 at 6:42 PM, Mark Miller markrmil...@gmail.com wrote:
Okay - I see the checksum stuff in build.xml - it just doesn't appear to
be working in my favor at the moment ...
You can just use md5sum from the command line too.
-Yonik
Unfortunately it doesn't look like analysis is actually back compatible.
http://search.lucidimagination.com/search/document/26c044ecbce3ed29
Consider the following token filter snippet that used to work fine:
public Token next(Token target) throws IOException {
input.next(target);
Analysis back compat break
--
Key: LUCENE-1919
URL: https://issues.apache.org/jira/browse/LUCENE-1919
Project: Lucene - Java
Issue Type: Bug
Reporter: Yonik Seeley
Fix For: 2.9
Old and new
Sure.
A simple example:
Say you have a type of field with fixed length data per doc, e.g. a 8 bytes.
It might be good to store in a segment:
numdocsv1v2vn
so if you have 1000 docs, your seg file is 8k+4 bytes.
Merging would be rather trivial as well.
Doing this right now involves storing
[
https://issues.apache.org/jira/browse/LUCENE-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12756883#action_12756883
]
Mark Miller edited comment on LUCENE-1919 at 9/17/09 5:41 PM:
--
[
https://issues.apache.org/jira/browse/LUCENE-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1919:
Attachment: LUCENE-1919.patch
alternative patch, should not change performance.
Analysis back
I believe you could override the IW.flush and IW.mergeSuccess
methods. flush unfortunately doesn't expose the new SegmentInfo,
however it could be obtained via
IW.getReader().getSequentialSubReaders (by comparing the before
and after).
Adjacent segment files could then be maintained without
[
https://issues.apache.org/jira/browse/LUCENE-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1919:
Attachment: LUCENE-1919.patch
better patch with testcase for the issue.
really, its just that in
[
https://issues.apache.org/jira/browse/LUCENE-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12756898#action_12756898
]
Yonik Seeley commented on LUCENE-1919:
--
Robert, you would need to handle the
[
https://issues.apache.org/jira/browse/LUCENE-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12756898#action_12756898
]
Yonik Seeley edited comment on LUCENE-1919 at 9/17/09 6:38 PM:
[
https://issues.apache.org/jira/browse/LUCENE-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12756901#action_12756901
]
Mark Miller commented on LUCENE-1919:
-
Nice - thanks Robert!
Analysis back compat
[
https://issues.apache.org/jira/browse/LUCENE-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12756903#action_12756903
]
Jason Rutherglen commented on LUCENE-1919:
--
With SOLR-908 CommonGramsQueryFilter
[
https://issues.apache.org/jira/browse/LUCENE-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12756909#action_12756909
]
Robert Muir commented on LUCENE-1919:
-
{quote}
edit: collision w/ robert.
Still wonder
[
https://issues.apache.org/jira/browse/LUCENE-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12756924#action_12756924
]
Robert Muir commented on LUCENE-1919:
-
bq. Still wonder if it's safe to get rid of
[
https://issues.apache.org/jira/browse/LUCENE-1919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12756944#action_12756944
]
Robert Muir commented on LUCENE-1919:
-
{quote}
Is there any sort of shared state in
On Fri, Sep 18, 2009 at 08:14:24AM +0800, John Wang wrote:
Say you have a type of field with fixed length data per doc, e.g. a 8 bytes.
It might be good to store in a segment:
numdocsv1v2vn
Heh. You've just described this proof of concept class:
Yes, I guess you could branch the code? It probably doesn't need to
be final Mike?
On Thu, Sep 17, 2009 at 7:16 PM, John Wang john.w...@gmail.com wrote:
Hi Michael:
Is there a wiki or some sort of write up on LUCENE-1458? It looks
extremely cool!
Re: Jason: isn't flush final?
-John
Maybe we can bypass writing JNI and use JNA?
https://jna.dev.java.net/
Apparently it doesn't work on the Mac and it's LGPL, however it
would be great to be able to plugin madvise for the merges.
Where the issue is merges do not need to be read into the system
IO cache, however they are anyways.
51 matches
Mail list logo
