Change datatypes dynamically of every column
Hello everybody,
Need help creating a pipeline. The data am working on looks like below:
Header
Datatype
Data
Data
Data
This is a CSV file so every column comes as a string. I want...
Forum Discussion
Thank you @tstack . This worked perfectly.
Can I ask a question on top of this.
I output of my mapper has correct datatypes,
I placed a Snowflake Bulk Load snap after the mapper with below configuration
This snap should create a table in the database if it is not already existing.
Pipeline ran successfully and the table was also created.
But when I see the datatypes in my database, all the columns are Varchar
Is there any specific reason for this. How can I ensure that the datatypes at the end of mapper to reflect in my database(snowflake)?
Thanks,
Sunil
Hello,
Can anyone look into this please. Is this an issue with Snowflake snaps?
I used Snowflake Bulk Load snap many times before to upload data. Usually, I create necessary tables using DDL statements before hand in snowflake and then use Bulk Load snap in my pipelines, but this is the first time am using ‘Create table if not present’.
Thanks,
Sunilscopes are specified in the
Token endpoint config, you add a new key/value with the key being “scope” and value being the space-delimited scopes you wish to request.Thank you for your reply, I did try this, and seems this solve the initial issue but now I get 400 Error
Just to update you that space-delimitated does not work so checking on this how I can specify 2 scopes
from my understanding of coupa, it needs to be specified on both sides, and from the snaplogic side, you’ll need to re-authorize when you make a change (if you just refresh, it won’t necessarily apply the update in scope). the coupa documentation states to space-delimit them (see screenshot below)
Here’s the link to their documentation for it - OAuth 2.0 Transition Guide | Coupa Unfortunately, I don’t see any specific endpoint configurations in their api documentation regarding the specific format expected, but I would suspect space separated is correct.
Coupa Documentation states:
With that access_token set in the Authorization header you can make GET, PUT or POST calls to the Client scopes you defined for that Connection.
In this case, to accomplish this, check the “Header Authenticated” checkbox in the account settings, and that should resolve the issue for you.
Thanks this solved the issue, I also follow the REST OAuth2 docs. Thank you very much
