A very basic question.
I am reading data from a table, few of the columns are null for all records. On edge i can see these data being passed. However, on Attribute on datastore i donot see these attributes.
I just wanted to confirm, is it like clover will not load attributes for which the values are null for all records?
Hi, varkashy,
What is the difference between words “column” and “attribute” in your question? Do you consider them as the same thing? And what is “attribute on datastore”? Can you please rephrase your question? I am not sure I understand correctly.
If your problem is that some of the columns from input data are missing, this would be an odd behavior. Readers should not skip any columns if everythig is set properly. Can you please post an example graph and some sample of your input file? It would be very helpful here. Thanks in advance.
Best regards,
To clarify in to my question
I have a table in DB , with a column , lets say, supply_id. This is null for all rows.
When i load data from this table using clover ETL graph and lets say source this data to another table , will my final table will have a column as supply_id?
Or will this column will get dumped.
Your final table has to exist before the query in DBOutputTable is executed. You can create it externally (outside Designer) or right in Designer with “Create database table” function. But we do not support automatic table creation during the graph run (the process generally can not be fully automatized). So if we realize that the table has to exist before, everything else is just a matter of field mapping.
Best regards,
My question is not about table creation. But if that column which has all null value will be picked in ETL load or not?
Yes, if you have it in your metadata, it will be picked. Btw. there is Nullable property on the metadata field which if set to false and reader finds the null value, throws an error.
Best regards,
Hi,
The attribute which has null values for all of the rows will be dropped and not pumped into ur data store. Even we have noticed this.
But actually this behavior is unexpected and must be changed.
Thanks,
Swathi
Hi both,
seems to me, you both use Endeca/Oracle Data Integrator Server, right? By that was caused misunderstandings above, we thought you use plain CloverETL.
Please contact Oracle support, if you really use Data Integrator. They will help you better as they know all the details about CloverETL integration into their product.
Regarding this problem, CloverETL really reads all columns, including those filled only by null values. Question is how this columns are handled by Integrator Server.