Skip to main content

Hello! Is there a way to push multiple timeseries in CDF timeseries within one single query in the DB extractor config.yml file? Or do we need multiple queries?

Also, if my incremental field is a timestamp datetime format, is it working or not as I'm receving an error related to it. 

Regards,

Raluca

Hi @Raluca Bala,

Just a quick reminder to take a look at our documentation. To help you with the issue, could you please share the following details?

- Extractor version

- Error message

- Configuration file


Hi @Dilini Fernando , thanks for replying to to this. I’ve gone through the documentation. I’ve managed to create a query to account for multiple timeseries at once and used this conversion within the query for the incremental field chosen as datetime (timestamp):  CAST({incremental-field} AS DATETIME2) >= '{start-at}' . Otherwise it cannot compare the timestamp with a state stored value as string.

 

Raluca


@Dilini Fernando , I have another question/issue: I haven't figure it out how can I retrieve also string/text columns in a separate query with the DB extractor. Tried to put them separately in 2 queries, one for numeric/float columns and one for string/text column but the extractor apparently runs only the second/last query listed in the config.yml file. I also managed to extract all numeric and string/text columns in one query but they are pushed in CDF timeseries as string types.


Hi @Raluca Bala,

I've created a support ticket for this, and the team will investigate and provide you with an update.


Hi @Raluca Bala,

I hope now you are able to execute multiple queries after adding "-" to the config file as per the below example.

queries: 
- name: my_name_1 
database: my_database 
query: first_query 

- name: my_name_2 
database: my_database 
query: second_query

As of now, I will be closing this thread. If you have any questions please feel free to create a post in hub 


Thank you, @Dilini Fernando , I've managed to solve it with the above solution from Cognite support team.


Reply