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

Don't allow create virtual schemas when a source schema has more than 1000 tables #75

Closed
AnastasiiaSergienko opened this issue Dec 16, 2020 · 0 comments · Fixed by #76
Closed
Assignees

Comments

@AnastasiiaSergienko
Copy link
Contributor

Problem

We want to warn users that it's not a common use case to create Virtual Schemas for s source schema that contains more than 1000 tables. The users should use the TABLE_FILTER property to specify tables.

Solution

Throw an exception when the source schema contains more than 1000 tables and ask users to add TABLE_FILTER.

We can also add a property that ignores this check in the future.

@AnastasiiaSergienko AnastasiiaSergienko self-assigned this Dec 16, 2020
@AnastasiiaSergienko AnastasiiaSergienko transferred this issue from exasol/virtual-schema-common-java Dec 16, 2020
AnastasiiaSergienko added a commit that referenced this issue Dec 17, 2020
AnastasiiaSergienko added a commit that referenced this issue Dec 17, 2020
…0. (#76)

* #75: Restricted amount of mapped tables in a remote schema to 1000.

Co-authored-by: Sebastian Bär <sebastian.baer@exasol.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant