Also, in case you want to apply a patch as Tim suggested, here is how you go for it: Assuming the patch file to be present at: */path/to/file/mypatch.patch*
$ cd incubator-drill > $ git apply --check /path/to/file/mypatch.patch If there are no errors use any one of below to apply patch: > $ git apply /path/to/file/mypatch.patch > OR, > $ git am --signoff < /path/to/file/mypatch.patch This should apply the new patch for you. You can then re-build drill with the steps mentioned above and pick up the new tarball. On Thu, Jun 19, 2014 at 12:18 AM, Yash Sharma <[email protected]> wrote: > Terry, > Would you like to build Drill from source. It would be having each of the > latest changes. > > Here are the steps: > > $ git clone https://github.com/apache/incubator-drill >> $ cd incubator-drill >> $ mvn clean install -DskipTests > > > The binary tar can then be picked from : > >> >> >> /incubator-drill/distribution/target/apache-drill-1.0.0-m2-incubating-SNAPSHOT-binary-release.tar.gz > > > Let us know if it helps. > > Peace, > Yash > > > On Thu, Jun 19, 2014 at 12:08 AM, Terry Healy <[email protected]> wrote: > >> Thanks Tim, but I don't know how to do that, so I'll wait until in makes >> in further down the food chain. >> >> >> >> >> On 06/18/2014 02:35 PM, Timothy Chen wrote: >> >>> Hi Terry, >>> >>> It might not have been committed to the code base yet, as probably just >>> mean it has been pushed to some internal repo. >>> >>> The fastest way is probably just grab the patch file and apply it >>> yourself for now. >>> >>> Tim >>> >>> Sent from my iPhone >>> >>> On Jun 18, 2014, at 10:45 AM, Terry Healy <[email protected]> wrote: >>>> >>>> I checked the bug today and it says "REsolved". so I downloaded the >>>> nightly build and installed it over the old install, minus the /conf >>>> directory. >>>> >>>> It still fails for me in the same way. Did I misunderstand? >>>> >>>> -Terry >>>> >>>> On 06/17/2014 02:43 PM, Ramana Inukonda wrote: >>>>> Hey Terry, >>>>> >>>>> I think you are hitting >>>>> https://issues.apache.org/jira/browse/DRILL-995 >>>>> I believe there is a patch available and there should be a merge >>>>> happening >>>>> soon. Please try after that and see if you hit the same issue. >>>>> >>>>> Regards >>>>> Ramana >>>>> >>>>> >>>>> >>>>> On Tue, Jun 17, 2014 at 6:47 AM, Terry Healy <[email protected]> wrote: >>>>>> >>>>>> Hello- >>>>>> >>>>>> I'm trying to get Drill running on 6 of my (MapR / M3 / 3.1) nodes. >>>>>> Following the instructions (https://cwiki.apache.org/ >>>>>> confluence/display/DRILL/Connecting+Apache+Drill+to+Data+Sources) >>>>>> >>>>>> I get as far as attempting to configure dfs: and/or hdfs: from the >>>>>> Storage >>>>>> tab. When I select "Update" for dfs, it times out at the web browser >>>>>> with >>>>>> these errors in the log: >>>>>> >>>>>> 2014-06-17 09:31:21,756 [qtp204632028-62] INFO o.a.d.e.server.rest. >>>>>> StorageResources >>>>>> - Failure while trying to access storage config: dfs >>>>>> org.apache.drill.common.exceptions.ExecutionSetupException: Failure >>>>>> setting up file system plugin. >>>>>> at org.apache.drill.exec.store.dfs.FileSystemPlugin.<init>( >>>>>> FileSystemPlugin.java:98) >>>>>> ~[drill-java-exec-1.0.0-m2-incubating-SNAPSHOT-rebuffed. >>>>>> jar:1.0.0-m2-incubating-SNAPSHOT] >>>>>> at sun.reflect.NativeConstructorAccessorImpl. >>>>>> newInstance0(Native >>>>>> Method) ~[na:1.7.0_51] >>>>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance( >>>>>> NativeConstructorAccessorImpl.java:57) ~[na:1.7.0_51] >>>>>> >>>>>> Similarly, when I attempt to create a new storage configuration >>>>>> "hdfs", it >>>>>> times out and the log reports this: >>>>>> >>>>>> 2014-06-17 09:37:06,562 [qtp204632028-72] INFO o.a.d.e.server.rest. >>>>>> StorageResources >>>>>> - Failure while trying to access storage config: hdfs >>>>>> java.lang.RuntimeException: Failure while accessing Zookeeper >>>>>> at org.apache.drill.exec.store.sys.zk.ZkPStore.get(ZkPStore. >>>>>> java:82) >>>>>> ~[drill-java-exec-1.0.0-m2-incubating-SNAPSHOT-rebuffed. >>>>>> jar:1.0.0-m2-incubating-SNAPSHOT] >>>>>> at org.apache.drill.exec.store.StoragePluginRegistry. >>>>>> getPlugin( >>>>>> StoragePluginRegistry.java:217) ~[drill-java-exec-1.0.0-m2- >>>>>> incubating-SNAPSHOT-rebuffed.jar:1.0.0-m2-incubating-SNAPSHOT] >>>>>> at org.apache.drill.exec.server.rest.StorageResources. >>>>>> findConfig(StorageResources.java:116) [drill-java-exec-1.0.0-m2- >>>>>> incubating-SNAPSHOT-rebuffed.jar:1.0.0-m2-incubating-SNAPSHOT] >>>>>> >>>>>> >>>>>> Caused by: org.apache.zookeeper.KeeperException$NoNodeException: >>>>>> KeeperErrorCode = NoNode for /drill/sys.storage_plugins/hdfs >>>>>> at org.apache.zookeeper.KeeperException.create( >>>>>> KeeperException.java:111) >>>>>> ~[zookeeper-3.4.6.jar:3.4.6-1569965] >>>>>> at org.apache.zookeeper.KeeperException.create( >>>>>> KeeperException.java:51) >>>>>> ~[zookeeper-3.4.6.jar:3.4.6-1569965] >>>>>> at org.apache.zookeeper.ZooKeeper.getData(ZooKeeper. >>>>>> java:1155) >>>>>> ~[zookeeper-3.4.6.jar:3.4.6-1569965] >>>>>> at org.apache.curator.framework.imps.GetDataBuilderImpl$4. >>>>>> call(GetDataBuilderImpl.java:302) ~[curator-f >>>>>> >>>>>> service mapr-zookeeper qstatus shows that all 4 zookeeper nodes are >>>>>> running. >>>>>> >>>>>> Any suggestions? >>>>>> >>>>>> Thanks >>>>>> >>>>> >>>>> >
