On 26 September 2012 23:47, Billy Newman wrote:
> To be a little more specific, the error message I get is:
> "forEach cannot start with '//'"
>
> Cannot really find anything on this except for
> https://issues.apache.org/jira/browse/SOLR-1437. Which only talks
> about using '//' for the xpath at
To be a little more specific, the error message I get is:
"forEach cannot start with '//'"
Cannot really find anything on this except for
https://issues.apache.org/jira/browse/SOLR-1437. Which only talks
about using '//' for the xpath attribute in the field tag, nothing
about using '//' in a forE
Hello all,
I am running solr 4.0.0-BETA and I am running into an issue when
trying to import an XML document in which I want forEach to pull from
nested elements with the same element name.
doc example:
1
Item 1
2
Thanks Ill give that a try
On 8/26/11 9:54 AM, simon wrote:
It sounds as though you are optimizing the index after the delta import. If
you don't do that, then only new segments will be replicated and syncing
will be much faster.
On Fri, Aug 26, 2011 at 12:08 PM, Mark wrote:
We are currentl
It sounds as though you are optimizing the index after the delta import. If
you don't do that, then only new segments will be replicated and syncing
will be much faster.
On Fri, Aug 26, 2011 at 12:08 PM, Mark wrote:
> We are currently delta-importing using DIH after which all of our servers
> h
We are currently delta-importing using DIH after which all of our
servers have to download the full index (16G). This obviously puts quite
a strain on our slaves while they are syncing over the index. Is there
anyway not to sync over the whole index, but rather just the parts that
have changed?
Hi Kaushik,
If the field is being treated as blobs, you can try using the
FieldStreamDataSource mapping.
This handles the blob objects to extract contents from it.
This feature is available only after Solr 3.1, I suppose.
http://lucene.apache.org/solr/api/org/apache/solr/handler/dataimport/FieldS
On Wed, Mar 16, 2011 at 9:50 PM, Kaushik Chakraborty wrote:
> The query's there in the data-config.xml. And the query's fetching as
> expected from the database.
[...]
Doh! Sorry, had missed that somehow.
So, the relevant part is:
SELECT ... p.message as solr_post_message,
What is the field typ
The query's there in the data-config.xml. And the query's fetching as
expected from the database.
Thanks,
Kaushik
On Wed, Mar 16, 2011 at 9:21 PM, Gora Mohanty wrote:
> On Wed, Mar 16, 2011 at 2:29 PM, Stefan Matheis
> wrote:
> > Kaushik,
> >
> > i just remembered an ML-Post few weeks ago ..
On Wed, Mar 16, 2011 at 2:29 PM, Stefan Matheis
wrote:
> Kaushik,
>
> i just remembered an ML-Post few weeks ago .. same problem while
> importing geo-data
> (http://lucene.472066.n3.nabble.com/Solr-4-0-Spatial-Search-How-to-tp2245592p2254395.html)
> - the solution was:
>
>> CAST( CONCAT( lat, ','
Kaushik,
i just remembered an ML-Post few weeks ago .. same problem while
importing geo-data
(http://lucene.472066.n3.nabble.com/Solr-4-0-Spatial-Search-How-to-tp2245592p2254395.html)
- the solution was:
> CAST( CONCAT( lat, ',', lng ) AS CHAR )
at that time i search a little bit for the reason
I've a column for posts in MySQL of type `text`, I've tried corresponding
`field-type` for it in Solr `schema.xml` e.g. `string, text, text-ws`. But
whenever I'm importing it using the DIH, it's getting imported as a BLOB
object. I checked, this thing is happening only for columns of type `text`
an
12 matches
Mail list logo
