How to cope with tables that may have different numbers of columns?
I have some oracle views that i want to index.
The views can have different numbers of columns for each customer - basically custom attributes that can be configured differently for each customer.
I have my query as select * from .
However, all the columns need to be populated, and are filled in into the -dataset-config.xml file.
We want to be able to have a customer independent -dataset-config.xml file, as our deployment method consists of shipping the xml files, and then triggering remote index creation.
Is there anyway to support this?
e.g. leave out the columns from the xml file (i'll try this)