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

Possible improvements to FAQ #488

Open
allipatev opened this issue Aug 17, 2023 · 0 comments
Open

Possible improvements to FAQ #488

allipatev opened this issue Aug 17, 2023 · 0 comments
Labels
documentation User guides, tutorials, specifications

Comments

@allipatev
Copy link

Please consider changing the following points for the Virtual Schemas FAQ:

There are also other ways to access the bucket: curl command or BucketFS Explorer

As project is archived, how about adding also bucketfs-python' or bucketfs-client` projects here?

The database uses the first suitable driver detected in the driver's list going through the list top-down. The driver that is higher in the list of JDBC Drivers will be used in this situation.

Formally, it's undefined behavior, to my knowledge. And in practice it's just not true for deployments with EXAOperation. For them we see that the last uploaded driver is being used.

com.exasol.adapter.dialects.PropertyValidationException: The dialect <DIALECT_NAME> does not support <PROPERTY_NAME> property. Please, do not set the BIGQUERY_ENABLE_IMPORT property.

Maybe for consistency don't mention the real property here at all?

Yes, you can use TABLE_FILTER = 'TABLE1','TABLE2',

Syntax doesn't look correct. My expectation is that it should be single string.

How many tables can contain a source schema?

How about mentioning Property MAX_TABLE_COUNT?

@kaklakariada kaklakariada added the documentation User guides, tutorials, specifications label Aug 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation User guides, tutorials, specifications
Projects
None yet
Development

No branches or pull requests

2 participants