Skip to content
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

Wait for DB container to be extracted #66

Open
ckunki opened this issue Sep 12, 2023 · 2 comments
Open

Wait for DB container to be extracted #66

ckunki opened this issue Sep 12, 2023 · 2 comments
Labels
feature Product feature

Comments

@ckunki
Copy link
Collaborator

ckunki commented Sep 12, 2023

Currently ETAJ does not wait for the script language container contained in the Exasol database (< version 8) to be extracted.

This can take ~ 5 minutes, and hence ETC offers method waitUntilContainerStarted() in ExasolContainer line L530, but ETAJ does not call this method.

This led to problems while working on KCE issue #72.

Acceptance Criteria

ETAJ, ExasolTestcontainerTestSetup line 25 does not specify any services, e.g. UDF, BucketFS, ...
Therefore ETC would not wait for SLC to be extracted even when asked for.

Proposal:

  1. enhance ETAJ to require all services by default and call method waitUntilContainerStarted() unconditionally.

Note: As mentioned by @tkilias Docker Containers for Exasol DB version 8 and higher are probably not affected as these are using a container format with SLC contents already extracted, not requiring additional extraction.

@ckunki ckunki added the feature Product feature label Sep 12, 2023
@ckunki
Copy link
Collaborator Author

ckunki commented Sep 12, 2023

When looking at @pj-spoelders' log files we identified that SLC had already been extracted:
Log file /exa/logs/cored/bucketfsd.*.log contained a line matching regular expression "ScriptLanguages.*extracted$" as exasol-testcontainers / UdfContainerWaitStrategy searches for.

So currently we assume a different issue and propose to

  1. setup script logging
  2. run the SQL statements again, e.g. with an SQL client such as DBeaver
  3. inspect output of nc

@redcatbear
Copy link
Contributor

@ckunki is this ticket still valid? I read your last comment as a "no".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Product feature
Projects
None yet
Development

No branches or pull requests

3 participants