Since we are bringing a feature parity between different stacks (mostly existing stacks and pay-as-you-go one), I think it might be beneficial to discuss the new features and publish a bit of a guide how to do the same (for testing/developing SQL query in workspaces. Lets have a look on SQL workspaces now:
A workspace serves several purposes and can be used as
- an interactive development environment (IDE) to create transformations.
- an analytical workspace where you can interactively perform experiments and modelling with live production data.
- an ephemeral workspace created on each run of a transformation to provide the staging area in which the transformation operates. Ephemeral transformation workspaces are not visible in the transformation UI, hence we won’t mention them further.
When a workspace is created, it enters the Active state and can be used.
- Database (Snowflake, Redshift, and Synapse) workspaces are billed by the runtime of queries executed in them. As such, we leave them in active state until you delete them.
|1 click setup||1 click setup|
|Single sandbox per user x project||Multiple private or shared Workspaces|
|No table unload||UI-based load/unload (user can also add new tables afterwards)|
|Scaling up via support ticket||UI-based scaling up (*some features may come later)|
|Has pre-set duration||Can be terminated, resumed & deleted|
How-to create workspace to develop and test SQL queries - you can create workspace by clicking on the button on the right:
then you can specify if the workspace should be shared:
once its up, you can click on the workspace detail:
you can see the input mapping has been correctly set (workspace created from transformation):
just click on credentials (link on the right) to get the same creds as you would be used to with "old" sandbox:
Let us know what is your experience working with Sandboxes and Workspaces, which features you miss and how can we improve it!
I have to say (as long-term user of old concept) that new setting is not working well for me when creating/updating transformations.
More workspaces is a good option. But there is not possibility to load data from transformation to existing workspace. This makes whole multi-workspace environment sort of one-off setting ... expecially when using DataGrip or other tool.
How others manage the transition?
I would be curious to see more feedback here - which would be very helpful for the product.
To answer your question, the advantage of workspace is that you can simply edit and add input mapping and load the new/refreshed data. But I understand, the time to add stuff in the mapping is a drawback of this flexibility.
that is true. I should use to start proces of creating of new transformation by creating workspace, not transformation ... something i was used to.
I would say, most of the issues around this will solve possibility to overwrite existing workspace from transformation component. So it will keep credentials but change input mapping (using one from transformation) and load new data.