Community

Hello, from reading the documentation, I understand that there are node testing capabilities built-in within Coalesce. However, is it possible to test an entire pipeline (i.e., a group of notes), to perform end-to-end testing? I would like to be able to point the pipeline to 'dummy' data and publish the outputs of it to another test dataset, so that I can check they match my expected outputs. Thank you in advance, Kind regards, Hanae

https://docs.coalesce.io/docs/setup-requirements#warehouse-whitelisting This doc page only shows 2 IP addresses but I am experiencing issues due to another IP address coming up that hasn't been whitelisted. Is there a range of IPs that I should ask to be whitelisted now rather than just two specific IPs?

Hello We are doing a first investigation of Coalesce with free Trial. Trying to set up git using our GitLab environment It worked on first try after I created an alternate repo in the same way on GitHub. We suspect it might be because our GitLab is self hosted but it would be good to be able to confirm that. The error message came up truncated, cannot attach the screen capture here it seems but will share on request. I have searched for logs and logging in the documentation but cannot see to find information on where to find to non truncated error message ? Thanks,

currently the only option is type: textBox. I'd like to have a drop-down list of values that are pre-defined. context: UDN for Advanced filtering where you can specify the operator (=, <, >, LIKE, etc) for a column then another mapped column for the value and another mapped column for the condition grouping { AND, OR, (AND, (OR, AND), OR) }

According to the documentation... "Source nodes represent the tables or views where raw data is queried to be processed by subsequent nodes. They are not manually editable other than to change their location or add a description." However I don't see my external tables as available sources which I logically expect them to be, I don't want to have to put a table or a view on top of this object to be able to source from it. This could of course be because I've done something wrong in the unnecessarily complex Snowflake security setup but it would be great if you could confirm exactly which table/view types are supported for use as source nodes please? A quick update to the documentation would be hugely appreciated as well. Cheers, Paul.

Attempted to rename a node (after creating the table) and when I hit the Create button I was expecting either that the underlying table with the original name would be dropped and the newly named one created or that a rename command would be issued to rename the table. However when I looked at my database I had both objects in there. Have I done something wrong? or is this the expected behaviour? Cheers, Paul.

Is it possible for me to configure a .yml file for a new node outside of the interface, in VSCode for example, then push that up to my Git repo and resync in coalesce to have that new node available? I've had a look at the .yml files and there seem to be some system generated things in there that I'm not sure you can create outside of the tool itself. If the answer is RTFM then please tell me to RTFM! (Although a hint of where to look would be appreciated) Cheers, Paul.

Could be that I'm missing something having only started using coalesce this morning but I couldn't see an option for a DISTINCT select on the OOTB nodes. Is this something that I would be expected to configure a custom node for? Or is it there but I just haven't spotted it? Cheers, Paul.