[
https://issues.apache.org/jira/browse/LUCENE-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1406:
Attachment: arabic.zip
Attached is my implementation
> new Arabic Analyzer (Apache license)
> ---
new Arabic Analyzer (Apache license)
Key: LUCENE-1406
URL: https://issues.apache.org/jira/browse/LUCENE-1406
Project: Lucene - Java
Issue Type: New Feature
Components: Analysis
Repor
[
https://issues.apache.org/jira/browse/LUCENE-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Ingersoll reassigned LUCENE-1406:
---
Assignee: Grant Ingersoll
> new Arabic Analyzer (Apache license)
> -
[
https://issues.apache.org/jira/browse/LUCENE-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634838#action_12634838
]
Grant Ingersoll commented on LUCENE-1406:
-
Very cool. I've used a modified versio
Came across:
http://www.google.com/url?sa=t&source=web&ct=res&cd=1&url=http%3A%2F%2Fgroups.google.com%2Fgroup%2Fandroid-developers%2Fbrowse_thread%2Fthread%2F601329551a87e601%2Fcd0919ce891b4a26%3Flnk%3Dgst%26q%3Dlucene&ei=zNzcSPHCF4yI1ga61YiTBA&usg=AFQjCNECrBnNPBkxI4I0EbIzI-mNp3S4YA&sig2=4sDMmwa9
It should be easy to add java.rmi.Remote to the JAR file of the
application. Unless there is some sort of restriction on adding
java.* classes. Lucene is supposed to operate on JDK1.4? Moving to
JDK1.5?
On Fri, Sep 26, 2008 at 9:07 AM, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
> Came across:
>
Grant Ingersoll wrote:
Came across:
http://www.google.com/url?sa=t&source=web&ct=res&cd=1&url=http%3A%2F%2Fgroups.google.com%2Fgroup%2Fandroid-developers%2Fbrowse_thread%2Fthread%2F601329551a87e601%2Fcd0919ce891b4a26%3Flnk%3Dgst%26q%3Dlucene&ei=zNzcSPHCF4yI1ga61YiTBA&usg=AFQjCNECrBnNPBkxI4I0EbIzI
[
https://issues.apache.org/jira/browse/LUCENE-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1406:
Attachment: (was: arabic.zip)
> new Arabic Analyzer (Apache license)
> ---
[
https://issues.apache.org/jira/browse/LUCENE-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1406:
Attachment: LUCENE-1406.patch
attached is patch
> new Arabic Analyzer (Apache license)
>
Grant Ingersoll wrote:
Came across:
http://www.google.com/url?sa=t&source=web&ct=res&cd=1&url=http%3A%2F%2Fgroups.google.com%2Fgroup%2Fandroid-developers%2Fbrowse_thread%2Fthread%2F601329551a87e601%2Fcd0919ce891b4a26%3Flnk%3Dgst%26q%3Dlucene&ei=zNzcSPHCF4yI1ga61YiTBA&usg=AFQjCNECrBnNPBkxI4I0EbIzI
Right, I think we could mark the RMI stuff on Searchable as deprecated
and note that it will be moved in 3.0.
I will open a JIRA.
On Sep 26, 2008, at 11:57 AM, DM Smith wrote:
Grant Ingersoll wrote:
Came across:
http://www.google.com/url?sa=t&source=web&ct=res&cd=1&url=http%3A%2F%2Fgroups
What about the use of newer classes and methods in JDK1.5 that may not
work on Android as well? It may be difficult to preplan for these.
On Fri, Sep 26, 2008 at 11:57 AM, DM Smith <[EMAIL PROTECTED]> wrote:
> Grant Ingersoll wrote:
>>
>> Came across:
>> http://www.google.com/url?sa=t&source=web&
Refactor Searchable to not have RMI Remote dependency
-
Key: LUCENE-1407
URL: https://issues.apache.org/jira/browse/LUCENE-1407
Project: Lucene - Java
Issue Type: Improvement
Re
>>since not many people, I think, even use the RMI stuff
I certainly binned RMI in my distributed work.
It just would not reliably stop/restart cleanly in my experience - despite
following all the RMI guidelines for clean shutdowns.
I'd happily see all RMI dependencies banished from core.
Che
[
https://issues.apache.org/jira/browse/LUCENE-1406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634944#action_12634944
]
Robert Muir commented on LUCENE-1406:
-
Thought I would add the following comments:
I
I am baffled by the results of the following queries. Can it be something to
do with the boosting factor? All of these queries are performed in the same
environment with the same crawled index/data.
A. query1 = +(content:(Pepsi)) resulted in 228
hits.
B. query2 = +(co
I am using the RMI RemoteSearchable. I don't use a central RMI
registry for the cluster (it's not particularly beneficial to do so),
so I have had none of the problems described above. It just works out
of the box.
Why not work towards RemoteSearchable instead of Searchable extending
java.rmi.Rem
I think that would allow us to fix the multisearcher negative query
wildcard bug in none remote cases.
Anthony Urso wrote:
I am using the RMI RemoteSearchable. I don't use a central RMI
registry for the cluster (it's not particularly beneficial to do so),
so I have had none of the problems desc
On Sep 26, 2008, at 8:19 PM, Anthony Urso wrote:
I am using the RMI RemoteSearchable. I don't use a central RMI
registry for the cluster (it's not particularly beneficial to do so),
so I have had none of the problems described above. It just works out
of the box.
Why not work towards RemoteSe
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
20 matches
Mail list logo
