To develop a working strategy for Talend open source and paid licenses, and to create a workflow
Discussion items
Item
Notes
How the team would work with mixed talend license?
We have not seen paid version. At the moment, it is 1 year test of paid license - to test whether talend enterprise meets our needs? if not, there might be a Possible outcome of RFP. This would have been timely discussion if we had got the license by now
In paid license, we have joblets. Joblets aren’t backward compatible. But it depends on what kind of jobs uses joblets and when we use joblets.
Bruce: Template that contains building blocks, joblets will create one template for all ETL jobs
Jeff: Standardized objects/code so bring in joblets that way no need to recreate the same jobs
Does Not have to code SFTP SCP other connections - all i have to do is change context file
Todd: Jeff creates any type of talned job without loading component- we need Talend enterprise license to add a joblet that has loading component.
Jeff: ability to include parallelization -- can only be done with paid version
Bruce: once you cut the talend jar file you no longer need java
Jeff: TAC
Todd: licenses are user accounts access and control TAC - have access to talend studio to interface
Bruce: do you need to have a studio to run in TAC? Iterative step
Figure out which one of those etl jobs has the opportunity to create joblets
Do we have a comparison of free and paid license? Vague comparison of talend paid and free license
Bruce: paid version include data mapper? No from rachel and todd - bruce did a data mapper webinar
Git integration with talend enterprise -- not positive. When we have hands on paid version - we need to look at the source control
Right now, we are looking at TOS which individual directories and file we need to check in - if we go through enterprise version and compare with TOS we may have a good feel for git practices and workflow. It will create more work on TOS or otherwise (we will never know until we get our hands on)
Bruce: if we are all working on same code, if we need to add joblets
Todd: Branches - production and non production context - will know more during this year of trial
Jeff has done staging job versioning - he moved to 1.0 from 0.1 and have not modified since anything
Bruce: keeping a version in talend, and running through git - git will handle changes?
Todd: code management can be done in 2 different ways - 1. Actual diffs betwen files themselves 2. Versioning within talend give you much larger monolithic kind of version (may have 12 git commits but end version is 1.0 or whatever). Rosemary can say she needs version 1.3 deployed and we can follow through and say that
Bruce: i stopped versioning in talend and cut releases in production
Pavan: git versions commits vs versions in Talend enterprise
Todd: Cutting a java release will 3rd way of code documentation. we need to figure out how to consistently maintain code. We are also 2 free licenses Talend Data Preparation and 2 free licenses Talend Data Stewardship
Rachel: i do not know
Bruce: data mapper
Talend data preparation may be similar to rapid insight's veera construct, a data prep tool
Talend studio’s components
Todd to let us know about Talend (when he gets to know more)
How are we going to work with talend development with combination of paid and open source versions?
What is the best path to incorporate/keep open source viable?
What would the work flow look like?
What are all the additional bells and whistles that Talend enterprise comes with when compared to open studio?
For example, what happens if we need to share the joblets, within team?
Various potential use cases with enterprise edition
Will a job from talend enterprise open and run in open studio? If yes, will the joblets and other enterprise level items open? How does it look like?
Action items
Identify various components of paid talend license and define what each of them do
TUG on Sept 19th?
Get free vs paid version comparison
We will know more about git and code management when we get our hands on with paid licenses
Need to decide on consistent code management practices: git commits, talend versioning, cutting java jobs
talend/ git workflow will be developed and will know more when we have talend enterprise