00 total rows in your visit,
study, and image tables anyway.
-- Jack Krupansky
-Original Message-
From: zbindigonzales
Sent: Monday, November 26, 2012 9:08 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr Near Realtime with denormalized Data
Hello again
The problem is that th
Hello again
The problem is that the software is used in different fields. The table
schema for hospital software is not the same as in the industrie sectors.
Customers usually create their own schema. The worst case scenary that we
know is that there are four tables connected.
Table patient -->
he two-part query so that data documents can be queried with patient ID.
-- Jack Krupansky
-Original Message-
From: zbindigonzales
Sent: Monday, November 26, 2012 6:56 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr Near Realtime with denormalized Data
Hello Erick
Thanks for your
Hello Erick
Thanks for your response.
The main problem we have, is that the data is denormalized. And this
increases the document to index exponentially.
Let's say we have the following two tables.
-- --
Table: Patient Table:Image
-
Why can't they be? I've seen indexing documents on the order of 6k/second.
Is the problem with getting the data out of the DB (i.e. how long does the
SQL take to execute) or on the Solr indexing side? If the former, you could
consider writing a SolrJ program that accessed the database and sent the
