Version 1.6.0 of the Tensei-Data migration software was just released.
This time you get a lot of bugfixes, more robustness, the groundwork for
very interesting future features and a breaking change!
WARNING: Breaking changes! This release contains changes that will
render saved cookbooks invalid! Please see the migration section below.
Summary of changes
This is primary a release containing a lot of bugfixes and some major
refactoring and to our regret a breaking change in the cookbook format.
- Support for SQLite databases.
- Documentation of stop sign handling for windows machines added to
- Output of the current byte offset if a parser exception occurs.
- Documentation for manual installation outside of a virtual machine.
- Automatic cancellation of the current job if a writer dies.
- Refactoring of the whole processor architecture which allows more
robust error handling and will lead to parallel execution in a future
- Handling of element ids was problematic therefore it was replaced with
"element references" which leads to a breaking change in the cookbook
The serialised cookbook is in link:http://www.json.org[JSON] format.
There are 2 sections that need to be adapted to be able to load an old
Before an element was referenced simply by the id. From now own an
element reference is created that holds the id of the DFASDL and the id
of the element within the DFASDL.
If your cookbook contains atomic transformations then it will currently
look like this:
Old json format
The "elementId" part has to be renamed and changed to a reference like
New json format
"dfasdlId": "DFASDL-ID", //<1>
"elementId": "ELEMENT-ID" //<2>
<1> The id of the DFASDL that contains the element.
<2> The id of the element within the DFASDL.
The mappings hold now complete element references instead of simple ids.
Before they looked like this:
Old json format
"sourceIds": [ "S-ID1", "S-ID2" ],
"targetIds": [ "T-ID1", "T-ID2" ],
Please rename the attribute
sources and the attribute
targets. Their content has to be transformed to look
New json format
"dfasdlId": "SOURCE-DFASDL-ID", // The id of the source DFASDL that contains the element.
"dfasdlId": "TARGET-DFASDL-ID", // The id of the target DFASDL that contains the element.
- Consideration of a CSV header line for an auto generated DFASDL.
- Possible NullPointerException on invalid connection information URI.
- No automatic override of resources upon cookbook import.
- Wrong number of pages in log message pager.
- Parser exception when parsing CSV files with last column data
- Possibly wrong auto generated DFASDL from CSV files.
- Disable of profiling in production code.
- Recognition of source data encoding for auto generated DFASDL
- Too strong license limitations that prevented some users from
creating cookbooks and transformation configurations.
- Auto generated DFASDL elements from CSV files could contain invalid
- Display errors upon DFASDL elements with the same id in the cookbook
Get your free trial version
You can try the Tensei-Data system for free. Just request a free trial version and receive the download link and a 14 days free license.