Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      The test case is commented out because not everyone has splunk on his/her network, but fails regardless of the presence of splunk:

      testSelect(net.hydromatic.optiq.test.SplunkAdapterTest) Time elapsed: 0.002 sec <<< ERROR!
      java.lang.UnsupportedOperationException: null
      at net.hydromatic.avatica.AvaticaConnection.createMeta(AvaticaConnection.java:75)
      at net.hydromatic.avatica.AvaticaConnection.<init>(AvaticaConnection.java:69)
      at net.hydromatic.avatica.AvaticaJdbc41Factory$AvaticaJdbc41Connection.<init>(AvaticaJdbc41Factory.java:112)
      at net.hydromatic.avatica.AvaticaJdbc41Factory.newConnection(AvaticaJdbc41Factory.java:60)
      at net.hydromatic.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:126)
      at net.hydromatic.optiq.impl.splunk.SplunkDriver.connect(SplunkDriver.java:58)
      at java.sql.DriverManager.getConnection(DriverManager.java:571)
      at java.sql.DriverManager.getConnection(DriverManager.java:187)
      at net.hydromatic.optiq.test.SplunkAdapterTest.checkSql(SplunkAdapterTest.java:205)
      at net.hydromatic.optiq.test.SplunkAdapterTest.testSelect(SplunkAdapterTest.java:169)

      While I concur with the fact that the test shouldn't depend on splunk being present, perhaps we could do with an in-memory jdbc database for such a test.

      ---------------- Imported from GitHub ----------------
      Url: https://github.com/julianhyde/optiq/issues/242
      Created by: karel1980
      Labels: bug,
      Created at: Wed Apr 09 14:10:41 CEST 2014
      State: closed

        Activity

        Hide
        github-import GitHub Import added a comment -

        [Date: Wed Apr 16 20:34:16 CEST 2014, Author: julianhyde]

        True. I'll fix it next time I'm editing the pom.

        Show
        github-import GitHub Import added a comment - [Date: Wed Apr 16 20:34:16 CEST 2014, Author: julianhyde ] True. I'll fix it next time I'm editing the pom.
        Hide
        github-import GitHub Import added a comment -

        [Date: Wed Apr 16 09:35:26 CEST 2014, Author: karel1980]

        Cool stuff.
        The explicit <include> is not needed in the pom because the test matches the default includes.

        Show
        github-import GitHub Import added a comment - [Date: Wed Apr 16 09:35:26 CEST 2014, Author: karel1980 ] Cool stuff. The explicit <include> is not needed in the pom because the test matches the default includes.

          People

          • Assignee:
            Unassigned
            Reporter:
            github-import GitHub Import
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development