-
Notifications
You must be signed in to change notification settings - Fork 0
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
Activate validation by verifying existence of file exasol-manifest.json #48
Labels
refactoring
Code improvement without behavior change
Comments
This was referenced Aug 13, 2024
ckunki
added a commit
that referenced
this issue
Aug 14, 2024
* Integrated ExtractValidator into LanguageContainerDeployer * Added file language_container_validator.py to provide backwards compatibility * Fix until manifest is deployed with standard SLCs see #48 * Fixed SQL syntax error * Fixed integration test * Fixed indention for UDF python script Co-authored-by: Torsten Kilias <tkilias@users.noreply.github.com>
tomuben
added a commit
that referenced
this issue
Sep 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ticket #42 requested to enhance the SLC Deployer, to optionally wait until SLC is deployed to all nodes in the database cluster. This is implemented by verifying the existence of file
exasol-manifest.json
, which was added to all SLCS in the scope of ticket exasol/script-languages-container-tool#221.It turned out that the integration tests of PEC failed, caused by using an SLC release not yet containing a manifest.
The developers decided to temporarily use the file
/exaudf/exaudfclient_py3
as a workaround. This doesn't make PEC worse than before but will not provide enhanced validation.The current ticket requests to replace the filename, again, as soon as the next release of script-languages-release is available, using an update version of SLCT to provide the file
exasol-manifest.json
.Another option would be to
ExtractValidator
Building the SLC is probably already implemented in a pytest fixture in the scope of ticket #45.
The text was updated successfully, but these errors were encountered: