I spoke too soon, perhaps  (but it must be a simple I/O issue on startup,
no?)


C:\devel\apache-drill-1.4.0\bin>sqlline.bat -u "jdbc:drill:zk=local"
DRILL_ARGS - " -u jdbc:drill:zk=local"
HADOOP_HOME not detected...
HBASE_HOME not detected...
Calculating Drill classpath...
Dec 31, 2015 5:39:53 PM org.glassfish.jersey.server.ApplicationHandler
initialize
INFO: Initiating Jersey application, version Jersey: 2.8 2014-04-29
01:25:26...
apache drill 1.4.0
"just drill it"
0: jdbc:drill:zk=local> SELECT * FROM cp.`employee.json` LIMIT 3;
Dec 31, 2015 5:46:55 PM
org.apache.calcite.sql.validate.SqlValidatorException <init>
SEVERE: org.apache.calcite.sql.validate.SqlValidatorException: Table
'cp.employee.json' not found
Dec 31, 2015 5:46:55 PM org.apache.calcite.runtime.CalciteException <init>
SEVERE: org.apache.calcite.runtime.CalciteContextException: From line 1,
column 15 to line 1, column 16: Table 'cp.employee.json' not found
Error: VALIDATION ERROR: From line 1, column 15 to line 1, column 16: Table
'cp.employee.json' not found


[Error Id: 9d6af232-fc40-40ec-8a2a-8d082923b776 on Funky:31010]
(state=,code=0)

On Thu, Dec 31, 2015 at 5:34 PM, Peder Jakobsen | gmail <[email protected]
> wrote:

> OUCH that hurts.  Sometimes you get lucky when you jump in a haystack and
> get pricked by the missing needle right away.
>
> So I copied hive.sys.drill from my tmp folder in linux to windows, and
> wow, now it seems to work.   Would you allow me the honour to fix this bug
> and commit the changes even though I have not programmed in Java since 2003
> ?   ;)  I can't imagine that I/O in java has changed all that much.
>
> Peder :)
>
>
>
> On Thu, Dec 31, 2015 at 5:30 PM, Peder Jakobsen | gmail <
> [email protected]> wrote:
>
>> No.  I've tried this many times.
>>
>> So at startup, it's supposed to create these files which it needs?
>>
>> It seems to do so in my linux install.   I will try to copy those files
>> over and see if I get another error.  Needle in a haystack debugging.  :)
>>
>> P.
>>
>> On Thu, Dec 31, 2015 at 5:27 PM, Nathan Griffith <[email protected]>
>> wrote:
>>
>>> Ah! Okay. I remember it making temporary stuff *somewhere* within
>>> windows.
>>>
>>> If I recall correctly, a bad set of temporary files once gave me the
>>> exact same issue, which was fixed by deleting them. But apparently
>>> this is isnt helping with your case?
>>>
>>> On Thu, Dec 31, 2015 at 2:22 PM, Peder Jakobsen | gmail
>>> <[email protected]> wrote:
>>> > OK, at startup, Drill creates an empty  file called hive.sys.drill
>>> that's
>>> > located in C:\tmp\drill\sys.storage_plugins
>>> >
>>> > Perhaps it's not surprising that we get "Unable to deserialize
>>> > "/tmp/drill/sys.storage_plugins/hive.sys.drill" (state=,code=0)"
>>> > considering that this file appears to be empty.
>>> >
>>> > On Linux, lots of stuff is included in this drill path:  profiles,
>>> > sys.options & sys.storage_plugins
>>> >
>>> > Hope this helps
>>> >
>>> > P.
>>> >
>>> > On Thu, Dec 31, 2015 at 5:13 PM, Peder Jakobsen | gmail <
>>> [email protected]
>>> >> wrote:
>>> >
>>> >> I deleted everything in  C:\Windows\Temp.  Note, when I start drill
>>> >> again, nothing gets created in there.   I will now try to search the
>>> >> machine for any files that may have been created at the time of
>>> startup.
>>> >> Standy by..
>>> >>
>>> >> On Thu, Dec 31, 2015 at 5:10 PM, Nathan Griffith <
>>> [email protected]>
>>> >> wrote:
>>> >>
>>> >>> Hey Peder,
>>> >>>
>>> >>> What's in your C:\Windows\Temp directory? Is there something that
>>> >>> looks like it's from Drill? If there is, try deleting it and running
>>> >>> again.
>>> >>>
>>> >>> --Nathan
>>> >>>
>>> >>> On Thu, Dec 31, 2015 at 1:53 PM, Peder Jakobsen | gmail
>>> >>> <[email protected]> wrote:
>>> >>> > Hi Tomer and Jacques,
>>> >>> >
>>> >>> > I tried those instructions to the letter.   I still get the same
>>> java
>>> >>> > Runtime Exception "Uable to deserialize
>>> >>> > "/tmp/drill/sys.storage_plugins/hive.sys.drill"
>>> >>> >
>>> >>> > Let me know if you need the full stack trace, although this should
>>> be
>>> >>> easy
>>> >>> > to replicate.  I simply installed a clean version of Windows 7 on
>>> >>> > VirtualBox, and followed all instructions from Drill documentation
>>> and
>>> >>> > Tomers suggestions.   I can't imagine why it would work on any
>>> other
>>> >>> > windows OS unless some other tweak is done somewhere.
>>> >>> >
>>> >>> > P.
>>> >>> >
>>> >>> >
>>> >>> > On Thu, Dec 31, 2015 at 1:22 PM, Jacques Nadeau <
>>> [email protected]>
>>> >>> wrote:
>>> >>> >
>>> >>> >> Just to clarify, Drill doesn't require Hadoop to be installed.
>>> Drill
>>> >>> does
>>> >>> >> include some Hadoop code since it uses some Hadoop functionality
>>> under
>>> >>> the
>>> >>> >> hood as a library (even in non-hadoop installs). Drill should be
>>> >>> including
>>> >>> >> the required windows executables/dlls in the distribution folder
>>> (for
>>> >>> using
>>> >>> >> hadoop as a library) and this should be transparent to you. Let
>>> us know
>>> >>> >> what happens when you follow the link that Tomer suggested.
>>> >>> >>
>>> >>> >> --
>>> >>> >> Jacques Nadeau
>>> >>> >> CTO and Co-Founder, Dremio
>>> >>> >>
>>> >>> >> On Thu, Dec 31, 2015 at 10:14 AM, Tomer Shiran <
>>> [email protected]>
>>> >>> wrote:
>>> >>> >>
>>> >>> >> > No. Drill does not depend on Hadoop
>>> >>> >> >
>>> >>> >> > Can you try these instructions and see if they work:
>>> >>> >> >
>>> >>> >> >
>>> >>>
>>> http://www.dremio.com/blog/installing-apache-drill-on-microsoft-windows/
>>> >>> >> >
>>> >>> >> >
>>> >>> >> > > On Dec 31, 2015, at 11:32 AM, Peder Jakobsen | gmail <
>>> >>> >> > [email protected]> wrote:
>>> >>> >> > >
>>> >>> >> > > Hi, does hadoop have to be installed in order to run apache
>>> drill
>>> >>> on
>>> >>> >> > > windows?
>>> >>> >> > >
>>> >>> >> > > So far, I'm 3 hours into "Run Apache Drill in 10 Minutes", and
>>> >>> still no
>>> >>> >> > > luck.  Once I figure it out, I will update the documentation
>>> for
>>> >>> >> windows
>>> >>> >> > if
>>> >>> >> > > you like.
>>> >>> >> > >
>>> >>> >> > > Thanks,
>>> >>> >> > >
>>> >>> >> > > Peder J.
>>> >>> >> >
>>> >>> >>
>>> >>>
>>> >>
>>> >>
>>>
>>
>>
>

Reply via email to