I think you need to synchronize your file.
The first time you run the interface, ODI creates the tables based on your XSD and populates them with the data. If you change the data in the XML file, then you need to synchronize the file for the changes to be picked up. See B.4.9 SYNCHRONIZE in the XML driver documentation:
Thanks for the reply.
I have got the solution.
Synchronization is not needed over here.
If we configure the Data Server in the following manner, any update or delete in CSV file will reflect in the target.
Here dod means drop on disc. It automatically drops the schema when we close the JDBC connection.
Here's what you can do to handle CSV files using HSQL.
Say the CSV file contains order data. Each order record contains data about a particular order like order number, product code, quantity, ordered by, date etc. Now lets take a hypothetical requirement which says, the user needs to know how many orders were ordered per product.
Option 1] At the basic level, read the order file, parse each line and write the logic to get count of orders per product.
Option 2] Load this CSV file into a database like MySQL and write database queries to get the orders per product.
So where does this leave us? Have we run out of options? I am sure we would have tried & used the above two options . But I wanted a different approach. Following questions were lingering in my mind:
1] Why can’t I write SQL queries against the CSV file itself. After all it’s like any RDBMS table.
2] Why should I load the CSV file into some database before I query it?
3] Why can’t I create a database table & attach the CSV file to it?
Continue Reading Here: Handling CSV Files