pache/solr/handler/dataimport/DIHCacheSupport.html
There doesn't seem to be a lot of documentation or examples for using cacheKey
and SQLEntityProcessor around.
Regards,Kevin
On Thursday, February 4, 2016 9:31 PM, Alexandre Rafalovitch
wrote:
Where did cachePrimaryKey
-start.com/
On 5 February 2016 at 02:53, Kevin Colgan wrote:
> Hi everyone,
>
> Is it possible to use SqlEntityProcessor in cached mode to repeat a query for
> a nested child element? I'd like to use the entity query once to consolidate
> information from the children to the par
Hi everyone,
Is it possible to use SqlEntityProcessor in cached mode to repeat a query for a
nested child element? I'd like to use the entity query once to consolidate
information from the children to the parent, then another to actually index the
entities as children.
Here's an
Hello
I've been trying to index IMDB data from MySQL with no success yet. The
problem was with the data import handler. When I specify using of
"SqlEntityProcessor", DIH either totally skipped the row, or didn't start
importing at all, or the results are not searchable.
I've heard of a user adding a separate section to the end of their
data-config.xml with a SqlEntityProcessor and an UPDATE statement. It would
run after your main section. I have not tried it myself, and surely
DIH was not designed to do this, but it might work.
A better solution mig
Custom UpdateRequestProcessor that collects the IDs of submitted
documents and updates the database on commit.
DataImportHandler itself is strictly one-way read operation. But you
can add URP chain after it.
Regards,
Alex.
Personal: http://www.outerthoughts.com/ and @arafalov
Solr resources an
Hi folks,
i am searching for a way to update a certain column in the rdbms for
each
item as soon as the item was indexed by solr.
The column will be the indicator in the delta-query to select un-indexed
items.
We don't want to use the timestamp based mechanism that is default.
Any ideas how we c
n Entity and a
> number
> of attributes. For a small subset of the Data - about 300 MB, I can do the
> import with 3 GB memory. Now with the entire 4 GB Dataset, I find I cannot
> do the import with 9 GB of memory.
> I am using the SqlEntityProcessor as below:
>
>
>
rt with 9 GB of memory.
> I am using the SqlEntityProcessor as below:
>
>
> url="jdbc:sqlserver://localhost\MSSQLSERVER;databaseName=SolrDB;user=solrusr;password=solrusr;"/>
Upgrade your JDBC driver to 1.2 or later, or turn on response buffering.
The following U
I have a Data Schema which is Hierarchical i.e. I have an Entity and a number
of attributes. For a small subset of the Data - about 300 MB, I can do the
import with 3 GB memory. Now with the entire 4 GB Dataset, I find I cannot
do the import with 9 GB of memory.
I am using the SqlEntityProcessor
Hi;
Good to hear that I could help you.
Thanks;
Furkan KAMACI
11 Aralık 2013 Çarşamba tarihinde O. Olson adlı
kullanıcı şöyle yazdı:
> Thank you very much Furkan for the detailed explanation. I simply set the
> processor to SqlEntityProcessor and cacheImpl to SortedMapBackedCache, an
Thank you very much Furkan for the detailed explanation. I simply set the
processor to SqlEntityProcessor and cacheImpl to SortedMapBackedCache, and
it worked for me i.e. from my original post I had/did:
Thanks again
eImpl" with any
EntityProcessor, not just*
*SqlEntityProcessor. So you can join child entities that come from XML,
flat files, etc. *
*CachedSqlEntityProcessor is technically deprecated as using it is the same
as SqlEntityProcessor with*
*cacheImpl="SortedMapBackedCache" specified. This does
Hi,
I am
looking to replace the Deprecated CachedSqlEntityProcessor with
SqlEntityProcessor
with a cacheImpl parameter but I cannot find documentation.
The Deprecated note at the top of
http://lucene.apache.org/solr/3_6_0/org/apache/solr/handler/dataimport
, the SqlEntityProcessor does not recognize the attribute's
value -- i.e., in case an SQL exception is thrown somewhere inside the
constructor of ResultSetIterators (which is an inner class of
JdbcDataSource), Solr's import exits immediately, even though onError is set
to continue or skip
On Mon, Nov 9, 2009 at 4:24 PM, Sascha Szott wrote:
> Hi all,
>
> as stated in the Solr-WIKI, Solr 1.4 allows it to specify an onError
> attribute for *each* entity listed in the data config file (it is considered
> as one of the default attributes).
>
> Unfortunately, the Sq
Hi all,
as stated in the Solr-WIKI, Solr 1.4 allows it to specify an onError
attribute for *each* entity listed in the data config file (it is
considered as one of the default attributes).
Unfortunately, the SqlEntityProcessor does not recognize the attribute's
value -- i.e., in case a
17 matches
Mail list logo
