I think it fails when using defType dismax with more than one field.
In the default Solr example doesn't work eighter. I have added the default
.xml files with docs and using standard requestHandler it works. It doesn't
when using the dismax requestHandler
Marc Sturlese wrote:
&
IGHT ON CREEKTREE
LANE, Square Footage: Square footage information in the MLS is sometimes
inaccurate. Therefore we do not display this on the web site. Instead please
inquire with your sales associate regarding more specific details of
properties you are interested in
Koji Sekiguchi-2 wrote:
>
&
it. Can you open a JIRA issue?
>
> Thank you,
>
> Koji
>
> --
> http://www.rondhuit.com/en/
>
>
> Marc Sturlese wrote:
>> I am having some trouble to make it work. I am debuging the code and I
>> see
>> when de FastVectorHighlighter constructor
[
https://issues.apache.org/jira/browse/SOLR-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805841#action_12805841
]
Marc Sturlese commented on SOLR-1268:
-
I have noticed an exception is thrown when u
(wich in normal
highlight returns the whole field highlighted) gives an error.
Koji Sekiguchi-2 wrote:
>
> Marc Sturlese wrote:
>> How do I activate FastVectorHighlighter in trunk? Wich of those params
>> sets
>> it up?
>>
>>> class="org
How do I activate FastVectorHighlighter in trunk? Wich of those params sets
it up?
Thanks in advance.
--
View this message in context:
http://old.nabble.com/configure-FastVectorHihglighter-in-trunk-tp27319976p27319976.html
Sent from the Solr - Dev mailing list archive at N
Hey there,
I just have started using hadoop to create Lucene/Solr indexes. Have couple
of questions.
I have seen there's a hadoop contrib to build a lucene index
(org.apache.hadoop.contrib.index). That contrib has a Partitioner to decide
for every map output wich reducer to go. It uses key.hashcod
[
https://issues.apache.org/jira/browse/SOLR-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793283#action_12793283
]
Marc Sturlese commented on SOLR-1632:
-
Wich should be the value of the param
e tests tests successful?
>
> 2009/12/7 Marc Sturlese :
>>
>> The request I am sending is:
>> http://localhost:8983/solr/select/?q=aaa&version=2.2&start=0&rows=20&indent=on&collapse.field=col&collapse.includeCollapsedDocs.fl=*&collapse.type=adjacent
> There are a number of tests that test the Field collapse functionality.
>
> Martijn
>
>
> 2009/12/7 Marc Sturlese :
>>
>>>
>>> cat
>>>
>>>
>>> hard
>>&g
lapse head ids. Everything that falls under the
> collapse head belongs to that collapse group and thus adding document
> head id to the field value is unnecessary. In the above example
> document with id 009 is the document head of document with id 008.
> Document with id 009 should b
Hey there, I have beeb testing the last patch and I think or I am missing
something or the way to show the collapsed documents when adjacent collapse
can be sometimes confusing:
I am using the patch replacing queryComponent for collapseComponent (not
using both at same time):
What I have notice
[
https://issues.apache.org/jira/browse/SOLR-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759489#action_12759489
]
Marc Sturlese commented on SOLR-1311:
-
Well, the thing is my patch is very goo
You should open a new thread asking for it.
Asish Kumar Mohanty wrote:
>
> Hi,
>
> I just want to write a Solr API for full-import. Can anybody please help
> me
> out???
>
> It's very urgent.
>
> Regards
> Asish
>
>
>
>
--
View this message in context:
http://www.nabble.com/-jira--Crea
ically.
>
>> pseudo-field-collapsing
>> ---
>>
>> Key: SOLR-1311
>> URL: https://issues.apache.org/jira/browse/SOLR-1311
>> Project: Solr
>> Issue Type: New Feature
>> Components
[
https://issues.apache.org/jira/browse/SOLR-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Sturlese updated SOLR-1311:
Attachment: (was: SOLR-1311-pseudo-field-collapsing.patch)
> pseudo-field-collaps
[
https://issues.apache.org/jira/browse/SOLR-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Sturlese updated SOLR-1311:
Comment: was deleted
(was: Sorry, there was a mistake in the other patch)
> pseudo-fi
[
https://issues.apache.org/jira/browse/SOLR-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Sturlese updated SOLR-1311:
Attachment: SOLR-1311-pseudo-field-collapsing.patch
Sorry, there was a mistake in the other patch
[
https://issues.apache.org/jira/browse/SOLR-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Sturlese updated SOLR-1311:
Comment: was deleted
(was: Patch that implements what i have explained.)
> pseudo-field-collaps
[
https://issues.apache.org/jira/browse/SOLR-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Sturlese updated SOLR-1311:
Attachment: SOLR-1311-pseudo-field-collapsing.patch
Patch that implements what i have explained
pseudo-field-collapsing
---
Key: SOLR-1311
URL: https://issues.apache.org/jira/browse/SOLR-1311
Project: Solr
Issue Type: New Feature
Components: search
Affects Versions: 1.4
Reporter: Marc
[
https://issues.apache.org/jira/browse/SOLR-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Sturlese updated SOLR-1070:
Comment: was deleted
(was: It was actually not a bug, just a bad use of the Context of a
[
https://issues.apache.org/jira/browse/SOLR-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Sturlese closed SOLR-1070.
---
Resolution: Fixed
It was actually not a bug, just a bad use of the Context of a Transformer of
[
https://issues.apache.org/jira/browse/SOLR-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683383#action_12683383
]
Marc Sturlese commented on SOLR-1070:
-
Hi Noble, I think you show me the light.
S
[
https://issues.apache.org/jira/browse/SOLR-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683191#action_12683191
]
Marc Sturlese commented on SOLR-1070:
-
Yes, I saw it uses CommitUpdateCommand,
Components: clients - java
Affects Versions: 1.4
Environment: Debian 2.6.26-1-xen-amd64
Tomcat 5.5
Reporter: Marc Sturlese
Fix For: 1.4
What I have noticed is afecting to the nightly build using multicore. I am
using tomcat 5.5 server and Debian 2.6.26-1-xen-amd64
I am doing some research about creating lucene/solr index using hadoop but
there's not so much info around, would be great to see some code!!! (I am
experiencing problems specially in duplication detection)
Thanks
Shalin Shekhar Mangar wrote:
>
> On Mon, Mar 2, 2009 at 11:24 PM, Ning Li wrote:
>>
>> Key: SOLR-1004
>> URL: https://issues.apache.org/jira/browse/SOLR-1004
>> Project: Solr
>> Issue Type: Improvement
>> Components: contrib - DataImportHandler
>>Affects Version
- DataImportHandler
Affects Versions: 1.3
Environment: Java - Lucene - Solr - DataImportHandler
Reporter: Marc Sturlese
Priority: Minor
Fix For: 1.3.1, 1.4
I have seen that when abort command is called in a deltaImport, in
DocBuilder.java, at doDelta functions
Hey there,
I experienced the problem and sort it with the patch. But... in case I would
have 500 of rows to modify the outofmemory problem would appear again?
Would be a good solution to run the query with limit 10?. And keep doing
it until no more docs would have to be updated? Every ti
30 matches
Mail list logo
