topic [2025-05] Snowflake keystore conflicts with API calls in same job in Talend Studio

[2025-05] Snowflake keystore conflicts with API calls in same job

PaSympa — Mon, 06 Oct 2025 09:19:21 GMT

Hello Community,

In Talend 2025-05 I am working with Snowflake and several API connections.

To connect to Snowflake we need to use a keystore, so we initialize it in the Prejob before creating the Snowflake connection. This works fine for Snowflake, but in the same job I also have different API calls.
For example:

retrieving or uploading files from Snowflake via API,
calling internal APIs to decrypt files, etc..

The issue is that the keystore initialization enters in conflict with these API calls, since they do not require a keystore.

My question:

Is there a way to specify that only some components should use the keystore while others should not?
Or alternatively, is there a way to deactivate the keystore before certain API calls?

At the moment, the only workaround I found is to put all Snowflake insertions in a separate subjob marked as independent. This works, but it blocks me for several implementations I am working on, because I would prefer to keep all the technical parts (Snowflake insertions + different API calls) in the same job.

Has anyone faced this situation, and is there another solution?

Thank you in advance for your support !

Screenshots attached for reference :

Re: [2025-05] Snowflake keystore conflicts with API calls in same job

marksouzacosta — Mon, 06 Oct 2025 13:10:18 GMT

Hi @PaSympa,

Can you please share a screen shot of your Job. I don't see how a KeyStore is affecting an API call.

Which block are you using to call the API?

Regards,

Mark Costa

Re: [2025-05] Snowflake keystore conflicts with API calls in same job

PaSympa — Wed, 08 Oct 2025 08:20:10 GMT

Hi @marksouzacosta,

Thanks for your reply!

After running several tests, I found that the issue seems resolved when using tHttpClient to download files. The conflict was specifically with tRest and tFileFetch, which we used in our previous version (Talend 2024-04). These components are now deprecated in Talend 2025-05.

We never had any issues with tRestClient, which continues to work fine even with the keystore initialized for Snowflake.

So it looks like the problem was tied to those deprecated components rather than the keystore itself.

Thanks again for your support!

Best regards,
Leandre