Apache Drill
  1. Apache Drill
  2. DRILL-223

Update source readme.txt to note protobuf requirement and common error resolution.

    Details

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

      Description

      If you have no protoc, you'll get the following error:

      Doing "mvn test" or "mvn install", etc. yields:
      [ERROR] Failed to execute goal com.github.igor-petruk.protobuf:protobuf-maven-plugin:0.6.3:run (default) on project common: Cannot execute 'protoc': Cannot run program "protoc": error=2, No such file or directory -> [Help 1]

      Tell people what to do if they have this problem

      Also note what happens if you have the wrong protoc.

        Issue Links

          Activity

          Hide
          Jacques Nadeau added a comment -

          Resolved through changeset c7daa9e~8

          Show
          Jacques Nadeau added a comment - Resolved through changeset c7daa9e~8
          Hide
          Aditya Kishore added a comment -

          If no one has any objection, I will take this up as per my previous comment.

          Show
          Aditya Kishore added a comment - If no one has any objection, I will take this up as per my previous comment.
          Hide
          Ted Dunning added a comment -

          +1 to not requiring protoc for simple dev use cases.

          Show
          Ted Dunning added a comment - +1 to not requiring protoc for simple dev use cases.
          Hide
          Aditya Kishore added a comment -

          If the proto schema is not evolving very frequently, may I suggest that we exclude compiling "*.proto" files as part of default build and check-in the generated Java sources.

          I understand that it is not ideal but cuts down on one requirement on "getting started with Drill".

          Show
          Aditya Kishore added a comment - If the proto schema is not evolving very frequently, may I suggest that we exclude compiling "*.proto" files as part of default build and check-in the generated Java sources. I understand that it is not ideal but cuts down on one requirement on "getting started with Drill".
          Hide
          Jack Weaver added a comment -

          Some food for thought...

          The How To Demo page on the wiki (https://cwiki.apache.org/confluence/display/DRILL/Demo+HowTo) has Ubuntu use apt-get to install the protobuf, but if you are on 12.04 (LTS) this puts version 2.4.x on your machine.

          That means you'll want to do the install by hand (the recommended install for CentOS/OEL/RHEL, etc). Following that install step gets the correct version, but on Ubuntu (12.04 again), you'll also want to run "ldconfig" ($ sudo ldconfig) right after installation. This is due to a stale ld.so.cache (sometimes the .so isn't found right after the install. See the comment thread here: https://code.google.com/p/protobuf/issues/detail?id=213).

          In this ticket, the [ERROR] result of maven might have been something I ran across earlier, but we would want the debug output ($ mvn clean install -X) to see what the issue was. If it was a missing .so, but the right version was installed, and the user is on a ubuntu distro, running ldconfig might help.

          Show
          Jack Weaver added a comment - Some food for thought... The How To Demo page on the wiki ( https://cwiki.apache.org/confluence/display/DRILL/Demo+HowTo ) has Ubuntu use apt-get to install the protobuf, but if you are on 12.04 (LTS) this puts version 2.4.x on your machine. That means you'll want to do the install by hand (the recommended install for CentOS/OEL/RHEL, etc). Following that install step gets the correct version, but on Ubuntu (12.04 again), you'll also want to run "ldconfig" ($ sudo ldconfig) right after installation. This is due to a stale ld.so.cache (sometimes the .so isn't found right after the install. See the comment thread here: https://code.google.com/p/protobuf/issues/detail?id=213 ). In this ticket, the [ERROR] result of maven might have been something I ran across earlier, but we would want the debug output ($ mvn clean install -X) to see what the issue was. If it was a missing .so, but the right version was installed, and the user is on a ubuntu distro, running ldconfig might help.

            People

            • Assignee:
              Aditya Kishore
              Reporter:
              Jacques Nadeau
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development