Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-19651

CONNECT engine JDBC not adequately reporting error or exception in certain cases

    XMLWordPrintable

Details

    Description

      When using CONNECT JDBC and an error occurs while obtaining schema info (i.e. with CATFUNC=TABLES) you generally get a good and very usable error message something like the following:

      (conn=4121) Got error 174 'GetTables: XcoreXsalesforceX190X7062.fkd: [sf:INVALID_LOGIN] INVALID_LOGIN: Invalid username, password, security token; or user locked out. ' from CONNECT
      

      In the above case it appears to be passing up the error message from exception thrown by the JDBC driver. However, if you then create a connect JDBC table successfully but later do something like a SELECT * FROM MyConnectTable that generates an error from the remote system, the error is generic as follows:

      ERROR: (conn=4124) Got error 174 'Cannot get result size rc=-1' from CONNECT
      

      It would be very, very helpful if the error text (exception.getLocalizedMessage() ) was included in the CONNECT error message at all times.... just like it is when CATFUNC=TABLES is used.

      Attachments

        Activity

          People

            bertrandop Olivier Bertrand
            rdyas Robert Dyas
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.