the locateTableInNamespace method parameters extractionContext.getJdbcEnvironment().getCurrentCatalog() and extractionContext.getJdbcEnvironment().getCurrentSchema() are wrong
Activity
Show:
Former userAugust 15, 2016 at 9:31 PM
, if this cannot be reproduced by a test case, then it sounds like the code is not reachable if the schema or catalog default is non-null. If that's the case, then please remove 5.0.11 and 5.1.2 as fix versions.
the locateTableInNamespace method parameters extractionContext.getJdbcEnvironment().getCurrentCatalog() and extractionContext.getJdbcEnvironment().getCurrentSchema() are wrong