-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot import DPU templates derived from another template #195
Comments
|
So probably it was not tested to import DPU template which is derived from another DPU template (3rd level DPU templates in the tree) |
As a consequence, we are not able to export/import sk datasets pipelines, because they use dpu templates based on t-sparql! So if we go for new release these days, this must be fixed there |
one can always create same templates manually
|
Well, if you have hundreds of SPARQL queries, it is not that useful. For sure, there are hundreds of queries within t-sparql template at cuni-test1 - that means at least one or two hours of work for import to one instance! I guess that what is needed is to add the following logic:
So it is about one boolean in the export to know which templates are second level templates (t-sparql) and which are third level (particular t-sparql with the particular configuration) |
related to #193 |
related to #177 |
How differs template in 2nd level from 3rd level template? |
1st level in the DPU tree - type of DPU template - 3 types - extractors, transformers, loaders Let's talk further about root DPU templates (2nd level) and dependant DPU templates (3rd level), which uses JAR file of its parent root template and overrides its configuration. |
When importing DPU template, which should be placed under an existing DPU template, the JAR file should not be loaded. This load makes sense for core DPU template (which introduces new JAR file) to test that new JAR file can be loaded. But in case of import of DPUs reusing existing JAR file, there is no sense in checking such JAR file (trying to load it). This will solve this issue. |
fix: 9759fc5 |
Result:
The text was updated successfully, but these errors were encountered: