Hi,
I just stumbled across an issue with Lucene's QueryParser. Perhaps you already
discussed this here, but googling for it didn't bring me to a solution.
I realized that lucene is obviously not able to exclude fields, right? E.g.
something like
-url:com
always delivers 0 results. Is this beh
> I realized that lucene is obviously not able to exclude fields, right? E.g.
> something like
>
> -url:com
>
> always delivers 0 results. Is this behaviour deliberate? Is there any
> rationale
> for it?
Ok, RTFM... :-)
http://lucene.apache.org/java/docs/queryparsersyntax.html
says that one
Is there any work/project to include LSI in Lucene?
There are some questions in the mailing lists, but they are older than a year.
Something happened since then?
Cheers,
Christoph
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For a
29 jan 2007 kl. 16.46 skrev Christoph Pächter:
Is there any work/project to include LSI in Lucene?
There are some questions in the mailing lists, but they are older
than a year.
Something happened since then?
As far as I know, no. But there are many other projects that does it
for you. C
I also research the use of LSA.
My interest is simply cluster the information. I found that LSA is a way,
but I'm not convinved is the better (also, is very high in CPU and RAM
consumption).
--
Mario Alejandro Montoya
MCP
www.paradondevamos.com
!El mejor sitio de restaurantes y entretenimiento d
It all depends for what you need it for. BTW, Latent Semantic Analysis
(LSA) is a super set of LSI. LSI concentrates on just how to index and
search documents in a reduced dimensional (latent) space whether LSA
includes a range of possible analysis that can be done on
representations in this space
Thank you for your answers.
I have no particular need.
I just thought that there is the fuzzysearch for syntactical proximity search,
there may be some implementation (in Lucene or external, easy to include) for a
semantical proximity search (LSI or something similar).
Just wanted to test it on so
[
https://issues.apache.org/jira/browse/LUCENE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468371
]
Yonik Seeley commented on LUCENE-565:
-
I just reviewed this, and it looks good to me.
I like how you managed to e
[
https://issues.apache.org/jira/browse/LUCENE-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Naber updated LUCENE-781:
Attachment: multireader.diff
updated patch
> NPE in MultiReader.isCurrent() and getVersion()
> ---
[
https://issues.apache.org/jira/browse/LUCENE-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Naber updated LUCENE-781:
Attachment: multireader_test.diff
updated patch
> NPE in MultiReader.isCurrent() and getVersion()
[
https://issues.apache.org/jira/browse/LUCENE-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468424
]
Daniel Naber commented on LUCENE-781:
-
I've attached an updated patch that now throws an exception for isCurrent(
Custom similarity is ignored when using MultiSearcher
-
Key: LUCENE-789
URL: https://issues.apache.org/jira/browse/LUCENE-789
Project: Lucene - Java
Issue Type: Bug
Components: Se
[
https://issues.apache.org/jira/browse/LUCENE-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12468436
]
Hoss Man commented on LUCENE-781:
-
comments based on cursory read of latest patch(es)...
1) I still think the IndexR
[
https://issues.apache.org/jira/browse/LUCENE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wettin updated LUCENE-626:
---
Attachment: (was: spellcheck_0.0.1.tar.gz)
> Adaptive, user query session analyzing spell checker
[
https://issues.apache.org/jira/browse/LUCENE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wettin updated LUCENE-626:
---
Attachment: (was: spellcheck_20060725.tar.gz)
> Adaptive, user query session analyzing spell chec
[
https://issues.apache.org/jira/browse/LUCENE-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wettin updated LUCENE-626:
---
Attachment: (was: spellcheck_20060804.tar.gz)
> Adaptive, user query session analyzing spell chec
I'm curious, Mark, what you think about the XMLQueryParser being
morphed into a JSON query parser. Is it possible to introduce a new
serialization format without rewriting the whole parser? Or is it
intimately tied to XML throughout?
Solr could really benefit from allowing queries to be p
17 matches
Mail list logo
