[
https://issues.apache.org/jira/browse/LUCENE-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12857107#action_12857107
]
Otis Gospodnetic commented on LUCENE-2393:
--
I think creating a small index
Uh, the IRC logs... Do people really think making those *searchable* would be
useful?
I think they'd be *extremely* noisy and hard to interpret without a person
really just sequentially reading them. Lots of people talking at the same
time, multiple topics, lots of very short intertwined messa
Subject: Re: Compound File Default
>
> Otis Gospodnetic wrote:
> > At the same time, seeing how some people benchmark systems without tuning
> > them
> and then publish their results, cfs may be safer.
> >
> >
> Though at the same time you get nailed with a 10-15%
John, you should have a look at Zoie. I just finished adding LinkedIn's case
study about Zoie to Lucene in Action 2, so this is fresh in my mind. :)
Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
- Original Message
> From: jchang
> To: java-dev@lucene.apache.org
John,
Yes, you should get 2.9.0 or 3.0.0, their indexing is faster. Still, even with
2.4.0 you shouldn't run into problems if you are really using just 1
IndexWriter. Still, I'd try upgrading first. Oh, and java-user is the place
to ask.
Otis
--
Sematext -- http://sematext.com/ -- Solr - Lu
I think what has changed is that a lot more people hit this problem, and a
number of people provided answers, so it's much easier now for a new person to
learn what to do when this limit is hit.
At the same time, seeing how some people benchmark systems without tuning them
and then publish thei
+1. I never liked having the compound format be the default, since increasing
the max # of open file handles is a well documented thing, at least in the UNIX
world.
Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
- Original Message
> From: Grant Ingersoll
> To: j
[
https://issues.apache.org/jira/browse/LUCENE-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797776#action_12797776
]
Otis Gospodnetic commented on LUCENE-2127:
--
+1 for Aaron's patch in a
[
https://issues.apache.org/jira/browse/LUCENE-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790889#action_12790889
]
Otis Gospodnetic commented on LUCENE-1910:
--
* I'll second Mark's
[
https://issues.apache.org/jira/browse/LUCENE-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785690#action_12785690
]
Otis Gospodnetic commented on LUCENE-2091:
--
Joaquin - could you please exp
[
https://issues.apache.org/jira/browse/LUCENE-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785473#action_12785473
]
Otis Gospodnetic commented on LUCENE-2091:
--
+1 for skipping BM25 and g
[
https://issues.apache.org/jira/browse/LUCENE-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783530#action_12783530
]
Otis Gospodnetic edited comment on LUCENE-2091 at 11/30/09 4:2
[
https://issues.apache.org/jira/browse/LUCENE-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783530#action_12783530
]
Otis Gospodnetic commented on LUCENE-2091:
--
Has anyone compared this partic
Hello,
The contrib/wordnet package contains an AnalyzerUtil class with a method that
extracts sentences from text/String. It is super-simplistic, so probably not
very accurate, but I am wondering if *conceptually* it would make sense to have
a Tokenizer that extracts sentences? I suppose that
Hello,
Regarding that monstrous term->idf map.
Is this something that one could use to adjust the scores in
http://wiki.apache.org/solr/DistributedSearch#Distributed_Searching_Limitations
scenario? Say a map like that was created periodically for each shard and
distributed to all other nodes (
I'm late to the thread, and although it looks like the discussion is over, I'll
inline a Q for Jake.
>I should add in my $0.02 on whether to just get rid of queryNorm() altogether:
>>>
>>> -1 from me, even though it's confusing, because having that call there
>>> (somewhere, at least) allows y
Hello,
Would it make sense and be possible to spread different index files over
multiple disks (without resorting to putting an index on a RAID)?
For example, what if the index files didn't live in a single index dir, but
were organized by their type in a snallow dir tree, like this:
/path/to/i
Not sure why, but this contrib's javadoc is missing:
http://lucene.apache.org/java/2_9_1/api/contrib-db/index.html
Also, the name "db" always bugged me a little. Would it make more sense to
call it contrib-bdb instead of contrib-db?
Otis
[
https://issues.apache.org/jira/browse/LUCENE-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic resolved LUCENE-1491.
--
Resolution: Fixed
Thanks Todd & Co.
SendingCHANGES.txt
Sen
Interesting, I never realized there was lucene-java-...@apache.org .
My thoughts are on
http://www.jroller.com/otis/entry/open_source_search_engine_benchmark (and in
several comments in the blog itself).
Otis
- Original Message
> From: Sean Owen
> To: lucene-java-...@apache.org
>
Me, too. I noticed Grant mentioned this in one of the long emails/threads,
too, a few weeks back, but I didn't want to pull out just that piece and
disturb the thread. And I bet people outside Lucene would love to have
search-independent set of chainable tokenizers, token filters, and such.
+1 for English as much as I like language variety.
Otis
- Original Message
> From: Grant Ingersoll
> To: java-dev@lucene.apache.org
> Sent: Friday, June 19, 2009 7:33:05 PM
> Subject: Re: javadoc language
>
> I think they should be in English. Keeping the Chinese would be fine as
[
https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720483#action_12720483
]
Otis Gospodnetic commented on LUCENE-1606:
--
Regarding the license - I thin
We have .
$ ff \*Info\*java
./src/java/org/apache/lucene/index/FieldInfo.java
./src/java/org/apache/lucene/index/TermVectorOffsetInfo.java
./src/java/org/apache/lucene/index/SegmentInfo.java
./src/java/org/apache/lucene/index/TermInfosWriter.java
./src/java/org/apache/lucene/index/TermInfo.jav
[
https://issues.apache.org/jira/browse/LUCENE-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716428#action_12716428
]
Otis Gospodnetic commented on LUCENE-1677:
--
In my cca 10 year history of b
[
https://issues.apache.org/jira/browse/LUCENE-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716053#action_12716053
]
Otis Gospodnetic commented on LUCENE-1491:
--
I'm getting convinced to
[
https://issues.apache.org/jira/browse/LUCENE-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715780#action_12715780
]
Otis Gospodnetic commented on LUCENE-1377:
--
Could we make this even more gen
[
https://issues.apache.org/jira/browse/LUCENE-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715763#action_12715763
]
Otis Gospodnetic commented on LUCENE-1491:
--
Karl - LUCENE-1306 - I agre
[
https://issues.apache.org/jira/browse/LUCENE-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715661#action_12715661
]
Otis Gospodnetic commented on LUCENE-1491:
--
I'm not 100% sure - I&#x
[
https://issues.apache.org/jira/browse/LUCENE-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715578#action_12715578
]
Otis Gospodnetic commented on LUCENE-1378:
--
I think a bunch of that xdocs s
Hi,
Anyone knows that that stuff under src/jsp is? Looks like an ancient demo
webapp but web.xml is empty, which makes me think that stuff doesn't work
anyway? svn rm src/jsp ?
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
--
[
https://issues.apache.org/jira/browse/LUCENE-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1271#action_1271
]
Otis Gospodnetic commented on LUCENE-1272:
--
Jonathan, would it be possible
[
https://issues.apache.org/jira/browse/LUCENE-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715551#action_12715551
]
Otis Gospodnetic commented on LUCENE-1491:
--
I agree this is an improvement,
[
https://issues.apache.org/jira/browse/LUCENE-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic resolved LUCENE-898.
-
Resolution: Fixed
Done.
D javascript/queryEscaper/luceneQueryEscaper.js
D
[
https://issues.apache.org/jira/browse/LUCENE-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic resolved LUCENE-1378.
--
Resolution: Fixed
Done. Thank you Paul.
Sendingsrc/java/org/apache/lucene
Hi,
I just stumbled upon:
http://repo1.maven.org/maven2/org/apache/lucene/lucene-similarity/
Nothing since 2.2.0?!
Well, it looks like there really is nothing in contrib/similarity (the
SweetSpotSimilarity is in contrib/miscellaneous):
similarity
|-- README.txt
|-- build.xml
|-- pom.xml.temp
[
https://issues.apache.org/jira/browse/LUCENE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714586#action_12714586
]
Otis Gospodnetic commented on LUCENE-1629:
--
Hm, my Japanese is a little weak
[
https://issues.apache.org/jira/browse/LUCENE-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714285#action_12714285
]
Otis Gospodnetic commented on LUCENE-1629:
--
I just got to look at this code
Me like!
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: Michael McCandless
> To: java-dev@lucene.apache.org
> Sent: Monday, May 18, 2009 5:06:39 PM
> Subject: Lucene's default settings & back compatibility
>
> As we all know, Lucene's ba
Hi,
Is that "Copyright 2009 www.imdict.net" allowed to be in there?
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: "mikemcc...@apache.org"
> To: java-comm...@lucene.apache.org
> Sent: Thursday, May 14, 2009 6:09:24 AM
> Subject: svn comm
[
https://issues.apache.org/jira/browse/LUCENE-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702192#action_12702192
]
Otis Gospodnetic commented on LUCENE-1284:
--
Hm, I feel that because of t
This would be a great contribution.
I took a quick look at the ZIP file and noticed it depends on, say,
net.imdict.wordsegment.WordSegmenter, but I didn't see that class anywhere. I
assume you will patch and polish things, but I thought I'd point this out.
Thanks!
Otis
--
Sematext -- http://se
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
From: Gao Pinker
To: java-dev@lucene.apache.org
Sent: Thursday, April 16, 2009 9:58:51 AM
Subject: I wanna contribute a Chinese analyzer to lucene
Hi All!
I wrote a Analyzer for apache lucene for
[
https://issues.apache.org/jira/browse/LUCENE-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697952#action_12697952
]
Otis Gospodnetic commented on LUCENE-1284:
--
Hi Felipe,
OK, I looked at
[
https://issues.apache.org/jira/browse/LUCENE-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697208#action_12697208
]
Otis Gospodnetic commented on LUCENE-1284:
--
One more for Felipe.
Is there a
[
https://issues.apache.org/jira/browse/LUCENE-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697185#action_12697185
]
Otis Gospodnetic commented on LUCENE-1284:
--
Felipe:
I took another look at
[
https://issues.apache.org/jira/browse/LUCENE-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688385#action_12688385
]
Otis Gospodnetic commented on LUCENE-1561:
--
Might be good to keep a consis
I haven't looked at that code in a while, but I bet it could use some
comment/explanation love. Consider doing that if you'll be going through that
"corner" of the code base.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: Michael McCand
Hi,
Has anyone noticed http://ir.dcs.gla.ac.uk/terrier/issues/browse/TR-9 ?
Interesting?
Hm, a GSoC project candidate and something that could take the student to CLEF
2009 to present his/her work?
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
gt; > database) that has heavy usage of bitmap indexes (a variation of them are
> > called LF - low-fast indexes there).
> >
> > Uwe
> >
> > -
> > Uwe Schindler
> > H.-H.-Meier-Allee 63, D-28213 Bremen
> > http://www.thetaphi.de
> > eM
gt;
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
> > -Original Message-
> > From: Otis Gospodnetic [mailto:otis_gospodne...@yahoo.com]
> > Sent: Friday, February 27, 2009 9:33 PM
> &
Hi,
I've had http://en.wikipedia.org/wiki/Bitmap_index open in my browser for
weeks, thinking I'd bring it up here -- would a bitmap index make sense
anywhere in Lucene (or perhaps Solr)?
Otis
-
To unsubscribe, e-mail: java-d
[
https://issues.apache.org/jira/browse/LUCENE-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675604#action_12675604
]
Otis Gospodnetic commented on LUCENE-1284:
--
Felipe - I'll have a loo
I think Erik put it well. I'd agree with that thinking even if I were not the
co-author. Listing LIA2 on the Wiki is good (and done), but my fear is that
only some people will find it there. I think showing LIA2 on the main page and
making it a bit stickier than a regular news item is a way
Hello,
Would it be OK to put the book cover and link to LIA2 some place on
lucene.apache.org/java, say below the navigation elements on the left side of
the page? I/we (authors) think it makes sense to do this -- the book is for
the Lucene community after all, but wanted to check with the res
I think lots of people here will find this interesting:
http://lingpipe-blog.com/2009/01/21/lucenes-missing-termfield-query-structure/
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
-
To unsubscribe, e-mail
ject: Solr
> > Issue Type: Improvement
> > Components: documentation
> >Affects Versions: 1.3
> > Environment: Tomcat 6, Java 6
> >Reporter: Kay Kay
> >Assignee: Otis Gospodnetic
> >Priority
[
https://issues.apache.org/jira/browse/LUCENE-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663633#action_12663633
]
Otis Gospodnetic commented on LUCENE-1519:
--
Deepak - could you please bring
[
https://issues.apache.org/jira/browse/LUCENE-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661302#action_12661302
]
Otis Gospodnetic commented on LUCENE-1513:
--
I feel like I missed some Fa
[
https://issues.apache.org/jira/browse/LUCENE-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661286#action_12661286
]
Otis Gospodnetic commented on LUCENE-1513:
--
References provided by Glen Ne
[
https://issues.apache.org/jira/browse/LUCENE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12660808#action_12660808
]
Otis Gospodnetic commented on LUCENE-1511:
--
Perhaps this should have been br
Hello,
I'm late looking into Uwe's Trie contrib (nice work!), but while looking at the
code/docs for it I wondered why the
following API (TrieUtils):
// add some numerical fields:
double fvalue = 1.057E17;
TrieUtils.VARIANT_8BIT.addDoubleTrieCodedDocumentField(doc,
"exam
Similar thoughts here. I don't have ML thread pointers nor JIRA issue
pointers, but there has been discussion in this area before, and I believe the
thinking was that what's needed is a general interface/abstraction/API for
storing and loading field data to an external component, be that a BDB,
[
https://issues.apache.org/jira/browse/LUCENE-1491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated LUCENE-1491:
-
Lucene Fields: [New, Patch Available] (was: [New])
Fix Version/s: 2.9
[
https://issues.apache.org/jira/browse/LUCENE-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655525#action_12655525
]
Otis Gospodnetic commented on LUCENE-1026:
--
My impression was that this di
[
https://issues.apache.org/jira/browse/LUCENE-1380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated LUCENE-1380:
-
Lucene Fields: [New, Patch Available] (was: [Patch Available, New])
Fix Version/s
[
https://issues.apache.org/jira/browse/LUCENE-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655517#action_12655517
]
Otis Gospodnetic commented on LUCENE-1487:
--
Would it be possible to reforma
[
https://issues.apache.org/jira/browse/LUCENE-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated LUCENE-1487:
-
Component/s: Search
Lucene Fields: [New, Patch Available] (was: [New
[
https://issues.apache.org/jira/browse/LUCENE-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653900#action_12653900
]
Otis Gospodnetic commented on LUCENE-855:
-
Hi Matt! :)
Tim, want to benchmark
[
https://issues.apache.org/jira/browse/LUCENE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653361#action_12653361
]
Otis Gospodnetic commented on LUCENE-1461:
--
Is this related to LUCENE-855?
[
https://issues.apache.org/jira/browse/LUCENE-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic reopened LUCENE-1378:
--
Lucene Fields: [New, Patch Available] (was: [Patch Available, New])
> Rem
[
https://issues.apache.org/jira/browse/LUCENE-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic reassigned LUCENE-689:
---
Assignee: Otis Gospodnetic (was: Steven Parkes)
> NullPointerException thrown
[
https://issues.apache.org/jira/browse/LUCENE-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647672#action_12647672
]
Otis Gospodnetic commented on LUCENE-1439:
--
Wiki may be more suitable for
[
https://issues.apache.org/jira/browse/LUCENE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647181#action_12647181
]
otis edited comment on LUCENE-524 at 11/13/08 7:06 AM:
---
B
[
https://issues.apache.org/jira/browse/LUCENE-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated LUCENE-1272:
-
Priority: Minor (was: Major)
Lucene Fields: [New, Patch Available] (was
[
https://issues.apache.org/jira/browse/LUCENE-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic resolved LUCENE-896.
-
Resolution: Fixed
Lucene Fields: [New, Patch Available] (was: [Patch Available
[
https://issues.apache.org/jira/browse/LUCENE-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic resolved LUCENE-1180.
--
Resolution: Fixed
It looks like Mike fixed this 2 months ago:
r694222 | mikemccand
[
https://issues.apache.org/jira/browse/LUCENE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647185#action_12647185
]
Otis Gospodnetic commented on LUCENE-38:
This thing is 6+ years old and I d
[
https://issues.apache.org/jira/browse/LUCENE-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647185#action_12647185
]
Otis Gospodnetic commented on LUCENE-38:
This thing is 6+ years old and I d
[
https://issues.apache.org/jira/browse/LUCENE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647181#action_12647181
]
Otis Gospodnetic commented on LUCENE-524:
-
Based on the description, yes. Doe
[
https://issues.apache.org/jira/browse/LUCENE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic resolved LUCENE-711.
-
Resolution: Fixed
Assignee: Otis Gospodnetic
Sendingsrc/java/org/apache
[
https://issues.apache.org/jira/browse/LUCENE-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic resolved LUCENE-548.
-
Resolution: Won't Fix
I agree, doesn't seem worth fixing. Explicit
[
https://issues.apache.org/jira/browse/LUCENE-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646971#action_12646971
]
Otis Gospodnetic commented on LUCENE-1306:
--
Could/should this not be folded
[
https://issues.apache.org/jira/browse/LUCENE-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated LUCENE-1413:
-
Lucene Fields: [New, Patch Available] (was: [Patch Available, New])
Fix Version/s
[
https://issues.apache.org/jira/browse/LUCENE-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic resolved LUCENE-518.
-
Resolution: Fixed
I think LUCENE-1420 fixed this.
> document field lengths co
[
https://issues.apache.org/jira/browse/LUCENE-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated LUCENE-1296:
-
Lucene Fields: [New, Patch Available] (was: [Patch Available, New])
Fix Version/s
[
https://issues.apache.org/jira/browse/LUCENE-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated LUCENE-1417:
-
Priority: Minor (was: Major)
I agree with Grant. I like that we not have pluggable
[
https://issues.apache.org/jira/browse/LUCENE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otis Gospodnetic updated LUCENE-1424:
-
Summary: Change all multi-term querys so that they extend MultiTermQuery
and allow for
[
https://issues.apache.org/jira/browse/LUCENE-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636686#action_12636686
]
Otis Gospodnetic commented on LUCENE-1410:
--
For people not intimately fami
[
https://issues.apache.org/jira/browse/LUCENE-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636068#action_12636068
]
Otis Gospodnetic commented on LUCENE-1409:
--
Since Lucene 2.4 is about t
Oh, and a note on GPL. It's fine to make use of GPL data, it's just that ASF
cannot distribute it. So the code could come with (java)docs that point out
that things would be better if the analyzer could use the GPL data that can be
downloaded from X and it could be written to make use of the G
Yeah, there is interest in Hebrew. People ask for it occasionally and I know
one vry large news organization that will be looking Lucene/Solr Hebrew
support in the coming weeks/months.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: Ro
Looks good to me!
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: Michael McCandless <[EMAIL PROTECTED]>
> To: java-dev@lucene.apache.org
> Sent: Monday, September 29, 2008 3:00:17 PM
> Subject: draft 2.4 announcement
>
>
> Here's my curr
However
> it is true that the comparison is apples to oranges. Are you
> suggesting removing the references to GData and GBase? I don't mind,
> I thought it would help to show people that realtime is in widespread
> usage somewhere.
>
> On Sat, Sep 27, 2008 at 9:46 AM, Ot
witter's Summize with I found out about
> later). The service Google provides through the GData protocol seems
> to also be referred to as GData, but could simply be called the
> "infrastructure supporting Google's realtime search web services".
>
> Jason
&
Hi,
Here is one thing that's been confusing me.
http://wiki.apache.org/lucene-java/OceanRealtimeSearch?highlight=(GData) often
mentions GData and relates it to real-time search (to Ocean), as if it is GData
that provides real-time search functionality. But isn't GData simply a
communication
ause of the hundreds
> of open and unreviewed issues that one would have to update in the
> tracker between each release.
>
> 23 sep 2008 kl. 21.33 skrev Otis Gospodnetic:
>
> > Hi,
> >
> > When people add new issues to JIRA they most often don't set the
Hi,
When people add new issues to JIRA they most often don't set the "Fix Version"
field. Would it not be better to have a default value for that field, so that
new entries don't get forgotten when we filter by "Fix Version" looking for
issues to fix for the next release? If every issue had "
[
https://issues.apache.org/jira/browse/LUCENE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632833#action_12632833
]
Otis Gospodnetic commented on LUCENE-427:
-
Jay, does the attached patch solve
[
https://issues.apache.org/jira/browse/LUCENE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632833#action_12632833
]
Otis Gospodnetic commented on LUCENE-427:
-
Jay, does the attached patch solve
1 - 100 of 711 matches
Mail list logo
