Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-966

Phoenix needs to be on the main classpath of SQL tools

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.0, 4.0.0
    • Fix Version/s: 3.1.0, 4.1.0
    • Labels:
      None

      Description

      The Phoenix client jar currently needs to be put on the boot classpath of external SQL tools in order to function correctly, while most JDBC drivers do not have this requirement.

      For example, in SQuirreL there is an option to provide the path to the JDBC driver jar file when defining a JDBC driver. This approach doesn't work with Phoenix due to it dependence on loading classes and the hbase-default.xml file via the context classloader.

      For installations of external tools where users don't have the rights/abilities/knowledge necessary to add an external jar file to the boot classpath, this causes a genuine issue for using Phoenix.

        Attachments

        1. PHOENIX-966b-4.0.patch
          37 kB
          Gabriel Reid
        2. PHOENIX-966b-3.0.patch
          33 kB
          Gabriel Reid
        3. PHOENIX-966a.patch
          19 kB
          Gabriel Reid

          Activity

            People

            • Assignee:
              gabriel.reid Gabriel Reid
              Reporter:
              gabriel.reid Gabriel Reid
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: