Thank you Erick for your answer. I read your post and I found it very
interesting.
Unfortunately it is not suitable for my use case:
* security is not an issue, since the dbs will be fully replicated in
the same infrastructure.
* there are no bazillion of data (something like 300K html documents)
*
Maurizio:
DIH is great for its intended purpose, but when things get complex I generally
prefer writing something in SolrJ, it gives much finer-grained control
over "special circumstances". Plus, you can see everything that
happens. Here's a blog with a skeletal SolrJ program, you can just
pull ou
Ciao Davide,
Unfortunately changing the structure of the dbs is not an option for
me (there are many legacy dbs involved), otherwise I would have chosen
a /closure table/ instead of the /path enumeration/ you mentioned
before.
Furthermore, I'd need 2 PE fields: 1 for the values (ids) and 1 for
th
Hi Maurizio,
if you can manipulate your MySql db a simpler solution can be the following:
1 - Add a new field for your hierarchical data inside your table
MY_HIERARCHICAL_FIELD
2 - Populate directly in MySql this new field with a simple procedure*
3 - Import the data in your Solr index
*The MySql
