Jason,
I was able to build the PR with -Denforcer.skip=true option. However, I can no
longer repro the bug. I was able to drop the table without an error.
Thanks
Kumiko
From: Kumiko Yada
Sent: Thursday, January 28, 2016 6:32 PM
To: 'Jason Altekruse' <altekruseja...@gmail.com>
Subject: RE: DATA_WRITE ERROR: Failed to drop table
When I build the drill today, I’m getting the following build errors:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce
(enforce-jdbc-jar-compactness) on project drill-jdbc-all: Some Enforcer rules
have failed. Look above for specific messages explaining why the rule failed.
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce
(enforce-jdbc-jar-compactness) on project drill-jdbc-all: Some Enforcer rules
have failed. Look above for specific messages explaining why the rule failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Some Enforcer rules
have failed. Look above for specific messages explaining why the rule failed.
at
org.apache.maven.plugins.enforcer.EnforceMojo.execute(EnforceMojo.java:209)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
-Kumiko
From: Jason Altekruse [mailto:altekruseja...@gmail.com]
Sent: Thursday, January 28, 2016 2:48 PM
To: Kumiko Yada <kumiko.y...@ds-iq.com<mailto:kumiko.y...@ds-iq.com>>
Cc: Kevin Verhoeven
<kevin.verhoe...@ds-iq.com<mailto:kevin.verhoe...@ds-iq.com>>; Ki Kang
<ki.k...@ds-iq.com<mailto:ki.k...@ds-iq.com>>; user
<user@drill.apache.org<mailto:user@drill.apache.org>>
Subject: Re: DATA_WRITE ERROR: Failed to drop table
The patch was small and received a review quickly, so I merged it. You can just
build the tip of master.
On Thu, Jan 28, 2016 at 11:27 AM, Jason Altekruse
<altekruseja...@gmail.com<mailto:altekruseja...@gmail.com>> wrote:
Hi Kumiko,
I have created a JIRA for this and posted a patch, please try building the
branch in the PR linked here. [1]
[1] - https://issues.apache.org/jira/browse/DRILL-4322
On Tue, Jan 26, 2016 at 12:56 PM, Kumiko Yada
<kumiko.y...@ds-iq.com<mailto:kumiko.y...@ds-iq.com>> wrote:
Jason,
I setup the environment, and I'm able to build/deploy the drill.
I run "git clone https://git-wip-us.apache.org/repos/asf/drill.git"; today, and
the attached is the pom.xml. It shows "drill 1.5.0-SNAPSHOT". Let me know
when you are ready to share the branch.
Thanks
Kumiko
-----Original Message-----
From: Kumiko Yada
Sent: Friday, January 22, 2016 4:44 PM
To: 'altekruseja...@gmail.com<mailto:altekruseja...@gmail.com>'
<altekruseja...@gmail.com<mailto:altekruseja...@gmail.com>>
Cc: Kevin Verhoeven
<kevin.verhoe...@ds-iq.com<mailto:kevin.verhoe...@ds-iq.com>>; Ki Kang
<ki.k...@ds-iq.com<mailto:ki.k...@ds-iq.com>>
Subject: RE: DATA_WRITE ERROR: Failed to drop table
Jason,
I'm using the drill 1.4. I can try to build/deploy it, but I might need some
help and take a time to setup the environment. And also, is there any
additional info needed for the hbase row count issue? Since I need to build
the drill with some changes, I can test/provide more info if it's needed.
Thanks
Kumiko
-----Original Message-----
From: Jason Altekruse
[mailto:altekruseja...@gmail.com<mailto:altekruseja...@gmail.com>]
Sent: Friday, January 22, 2016 4:31 PM
To: user <user@drill.apache.org<mailto:user@drill.apache.org>>
Cc: Kevin Verhoeven
<kevin.verhoe...@ds-iq.com<mailto:kevin.verhoe...@ds-iq.com>>; Ki Kang
<ki.k...@ds-iq.com<mailto:ki.k...@ds-iq.com>>
Subject: Re: DATA_WRITE ERROR: Failed to drop table
Took a look back at it the code and the construction of the exception object is
actually eating the underlying exception.
If I shared a branch fixing the error message creation could you build/deploy
it and try to re-run your query? What version of Drill are you using? I can
base the small change on a commit near whatever release you are on.
- Jason
On Fri, Jan 22, 2016 at 4:19 PM, Kumiko Yada
<kumiko.y...@ds-iq.com<mailto:kumiko.y...@ds-iq.com>> wrote:
> No, either of these were followed by a "Caused by" section with
> another stacktrace.
>
> -Kumiko
>
> -----Original Message-----
> From: Jason Altekruse
> [mailto:altekruseja...@gmail.com<mailto:altekruseja...@gmail.com>]
> Sent: Friday, January 22, 2016 4:13 PM
> To: user <user@drill.apache.org<mailto:user@drill.apache.org>>
> Cc: Kevin Verhoeven
> <kevin.verhoe...@ds-iq.com<mailto:kevin.verhoe...@ds-iq.com>>; Ki Kang <
> ki.k...@ds-iq.com<mailto:ki.k...@ds-iq.com>>
> Subject: Re: DATA_WRITE ERROR: Failed to drop table
>
> Looks like this is just another instance of the same stacktrace, but
> the error ID is different, so it may have been a different time you
> ran a query that resulted in an error. Are either of these followed by a
> "Caused by"
> section with another stacktrace?
>
> On Fri, Jan 22, 2016 at 4:03 PM, Kumiko Yada
> <kumiko.y...@ds-iq.com<mailto:kumiko.y...@ds-iq.com>>
> wrote:
>
> > Yes.
> >
> > org.apache.drill.common.exceptions.UserRemoteException: DATA_WRITE ERROR:
> > Failed to drop table
> >
> >
> > [Error Id: 3a099358-537d-47fd-8cc0-5994c6ffca88 on
> > blvkydevbfd01.ds-iq.corp:31010]
> > at
> > org.apache.drill.exec.rpc.user.QueryResultHandler.resultArrived(Quer
> > yR
> > esultHandler.java:119)
> > ~[drill-java-exec-1.4.0.jar:1.4.0]
> > at
> > org.apache.drill.exec.rpc.user.UserClient.handleReponse(UserClient.j
> > av
> > a:113)
> > ~[drill-java-exec-1.4.0.jar:1.4.0]
> > at
> > org.apache.drill.exec.rpc.BasicClientWithConnection.handle(BasicClie
> > nt
> > WithConnection.java:46)
> > ~[drill-rpc-1.4.0.jar:1.4.0]
> > at
> > org.apache.drill.exec.rpc.BasicClientWithConnection.handle(BasicClie
> > nt
> > WithConnection.java:31)
> > ~[drill-rpc-1.4.0.jar:1.4.0]
> > at org.apache.drill.exec.rpc.RpcBus.handle(RpcBus.java:69)
> > ~[drill-rpc-1.4.0.jar:1.4.0]
> > at
> > org.apache.drill.exec.rpc.RpcBus$RequestEvent.run(RpcBus.java:400)
> > ~[drill-rpc-1.4.0.jar:1.4.0]
> > at
> > org.apache.drill.common.SerializedExecutor$RunnableProcessor.run(Ser
> > ia
> > lizedExecutor.java:105)
> > ~[drill-rpc-1.4.0.jar:1.4.0]
> > at
> > org.apache.drill.exec.rpc.RpcBus$SameExecutor.execute(RpcBus.java:26
> > 4)
> > ~[drill-rpc-1.4.0.jar:1.4.0]
> > at
> > org.apache.drill.common.SerializedExecutor.execute(SerializedExecutor.
> > java:142)
> > ~[drill-rpc-1.4.0.jar:1.4.0]
> > at
> > org.apache.drill.exec.rpc.RpcBus$InboundHandler.decode(RpcBus.java:2
> > 98
> > )
> > ~[drill-rpc-1.4.0.jar:1.4.0]
> > at
> > org.apache.drill.exec.rpc.RpcBus$InboundHandler.decode(RpcBus.java:2
> > 69
> > )
> > ~[drill-rpc-1.4.0.jar:1.4.0]
> > at
> > io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageTo
> > Me
> > ssageDecoder.java:89) ~[netty-codec-4.0.27.Final.jar:4.0.27.Final]
> > at
> > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abs
> > tr
> > actChannelHandlerContext.java:339)
> > ~[netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > at
> > io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(Abstr
> > ac
> > tChannelHandlerContext.java:324)
> > ~[netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > at
> > io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHandl
> > er
> > .java:254) ~[netty-handler-4.0.27.Final.jar:4.0.27.Final]
> > at
> > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abs
> > tr
> > actChannelHandlerContext.java:339)
> > ~[netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > at
> > io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(Abstr
> > ac
> > tChannelHandlerContext.java:324)
> > ~[netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > at
> > io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageTo
> > Me
> > ssageDecoder.java:103) ~[netty-codec-4.0.27.Final.jar:4.0.27.Final]
> > at
> > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abs
> > tr
> > actChannelHandlerContext.java:339)
> > ~[netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > at
> > io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(Abstr
> > ac
> > tChannelHandlerContext.java:324)
> > ~[netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > at
> > io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessag
> > eD
> > ecoder.java:242) ~[netty-codec-4.0.27.Final.jar:4.0.27.Final]
> > at
> > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abs
> > tr
> > actChannelHandlerContext.java:339)
> > ~[netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > at
> > io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(Abstr
> > ac
> > tChannelHandlerContext.java:324)
> > ~[netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > at
> > io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInb
> > ou
> > ndHandlerAdapter.java:86)
> > ~[netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > at
> > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(Abs
> > tr
> > actChannelHandlerContext.java:339)
> > ~[netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > at
> > io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(Abstr
> > ac
> > tChannelHandlerContext.java:324)
> > ~[netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > at
> > io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChann
> > el
> > Pipeline.java:847) ~[netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > at
> > io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.
> > ep
> > ollInReady(AbstractEpollStreamChannel.java:618)
> > ~[netty-transport-native-epoll-4.0.27.Final-linux-x86_64.jar:na]
> > at
> > io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.ja
> > va
> > :329) ~[netty-transport-native-epoll-4.0.27.Final-linux-x86_64.jar:na]
> > at
> > io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:250)
> > ~[netty-transport-native-epoll-4.0.27.Final-linux-x86_64.jar:na]
> > at
> > io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThrea
> > dE
> > ventExecutor.java:111) ~[netty-common-4.0.27.Final.jar:4.0.27.Final]
> > at java.lang.Thread.run(Thread.java:745) ~[na:1.7.0_71]
> >
> > -----Original Message-----
> > From: Jason Altekruse
> > [mailto:altekruseja...@gmail.com<mailto:altekruseja...@gmail.com>]
> > Sent: Friday, January 22, 2016 4:02 PM
> > To: user <user@drill.apache.org<mailto:user@drill.apache.org>>
> > Cc: Kevin Verhoeven
> > <kevin.verhoe...@ds-iq.com<mailto:kevin.verhoe...@ds-iq.com>>; Ki Kang <
> > ki.k...@ds-iq.com<mailto:ki.k...@ds-iq.com>>
> > Subject: Re: DATA_WRITE ERROR: Failed to drop table
> >
> > Is there another stack trace after this line? This stack trace is
> > actually very generic in Drill, it's just the codepath taken when a
> > client receives a message. I was looking for an error from the
> filesystem itself.
> >
> > On Fri, Jan 22, 2016 at 3:57 PM, Kumiko Yada
> > <kumiko.y...@ds-iq.com<mailto:kumiko.y...@ds-iq.com>>
> > wrote:
> >
> > > Jason,
> > >
> > > Here is the callstack:
> > >
> > > [Error Id: 12e9ba22-271f-4b73-897e-186bf320f9d3 on
> > > blvkydevbfd01.ds-iq.corp:31010]
> > > at
> > > org.apache.drill.exec.rpc.user.QueryResultHandler.resultArrived(Qu
> > > er
> > > yR
> > > esultHandler.java:119)
> > > [drill-java-exec-1.4.0.jar:1.4.0]
> > > at
> > > org.apache.drill.exec.rpc.user.UserClient.handleReponse(UserClient
> > > .j
> > > av
> > > a:113)
> > > [drill-java-exec-1.4.0.jar:1.4.0]
> > > at
> > > org.apache.drill.exec.rpc.BasicClientWithConnection.handle(BasicCl
> > > ie
> > > nt
> > > WithConnection.java:46)
> > > [drill-rpc-1.4.0.jar:1.4.0]
> > > at
> > > org.apache.drill.exec.rpc.BasicClientWithConnection.handle(BasicCl
> > > ie
> > > nt
> > > WithConnection.java:31)
> > > [drill-rpc-1.4.0.jar:1.4.0]
> > > at org.apache.drill.exec.rpc.RpcBus.handle(RpcBus.java:69)
> > > [drill-rpc-1.4.0.jar:1.4.0]
> > > at
> > > org.apache.drill.exec.rpc.RpcBus$RequestEvent.run(RpcBus.java:400)
> > > [drill-rpc-1.4.0.jar:1.4.0]
> > > at
> > > org.apache.drill.common.SerializedExecutor$RunnableProcessor.run(S
> > > er
> > > ia
> > > lizedExecutor.java:105)
> > > [drill-rpc-1.4.0.jar:1.4.0]
> > > at
> > > org.apache.drill.exec.rpc.RpcBus$SameExecutor.execute(RpcBus.java:
> > > 26
> > > 4)
> > > [drill-rpc-1.4.0.jar:1.4.0]
> > > at
> > > org.apache.drill.common.SerializedExecutor.execute(SerializedExecutor.
> > > java:142)
> > > [drill-rpc-1.4.0.jar:1.4.0]
> > > at
> > > org.apache.drill.exec.rpc.RpcBus$InboundHandler.decode(RpcBus.java
> > > :2
> > > 98
> > > )
> > > [drill-rpc-1.4.0.jar:1.4.0]
> > > at
> > > org.apache.drill.exec.rpc.RpcBus$InboundHandler.decode(RpcBus.java
> > > :2
> > > 69
> > > )
> > > [drill-rpc-1.4.0.jar:1.4.0]
> > > at
> > > io.netty.handler.codec.MessageToMessageDecoder.channelRead(Message
> > > To
> > > Me
> > > ssageDecoder.java:89) [netty-codec-4.0.27.Final.jar:4.0.27.Final]
> > > at
> > > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(A
> > > bs
> > > tr
> > > actChannelHandlerContext.java:339)
> > > [netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > > at
> > > io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(Abs
> > > tr
> > > ac
> > > tChannelHandlerContext.java:324)
> > > [netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > > at
> > > io.netty.handler.timeout.IdleStateHandler.channelRead(IdleStateHan
> > > dl
> > > er
> > > .java:254) [netty-handler-4.0.27.Final.jar:4.0.27.Final]
> > > at
> > > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(A
> > > bs
> > > tr
> > > actChannelHandlerContext.java:339)
> > > [netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > > at
> > > io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(Abs
> > > tr
> > > ac
> > > tChannelHandlerContext.java:324)
> > > [netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > > at
> > > io.netty.handler.codec.MessageToMessageDecoder.channelRead(Message
> > > To
> > > Me
> > > ssageDecoder.java:103) [netty-codec-4.0.27.Final.jar:4.0.27.Final]
> > > at
> > > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(A
> > > bs
> > > tr
> > > actChannelHandlerContext.java:339)
> > > [netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > > at
> > > io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(Abs
> > > tr
> > > ac
> > > tChannelHandlerContext.java:324)
> > > [netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > > at
> > > io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMess
> > > ag
> > > eD
> > > ecoder.java:242) [netty-codec-4.0.27.Final.jar:4.0.27.Final]
> > > at
> > > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(A
> > > bs
> > > tr
> > > actChannelHandlerContext.java:339)
> > > [netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > > at
> > > io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(Abs
> > > tr
> > > ac
> > > tChannelHandlerContext.java:324)
> > > [netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > > at
> > > io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelI
> > > nb
> > > ou
> > > ndHandlerAdapter.java:86)
> > > [netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > > at
> > > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(A
> > > bs
> > > tr
> > > actChannelHandlerContext.java:339)
> > > [netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > > at
> > > io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(Abs
> > > tr
> > > ac
> > > tChannelHandlerContext.java:324)
> > > [netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > > at
> > > io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultCha
> > > nn
> > > el
> > > Pipeline.java:847) [netty-transport-4.0.27.Final.jar:4.0.27.Final]
> > > at
> > > io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.
> > > ep
> > > ollInReady(AbstractEpollStreamChannel.java:618)
> > > [netty-transport-native-epoll-4.0.27.Final-linux-x86_64.jar:na]
> > > at
> > > io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.
> > > ja
> > > va
> > > :329) [netty-transport-native-epoll-4.0.27.Final-linux-x86_64.jar:na]
> > > at
> > > io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:250)
> > > [netty-transport-native-epoll-4.0.27.Final-linux-x86_64.jar:na]
> > > at
> > > io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThr
> > > ea
> > > dE
> > > ventExecutor.java:111) [netty-common-4.0.27.Final.jar:4.0.27.Final]
> > > at java.lang.Thread.run(Thread.java:745) [na:1.7.0_71]
> > > 2016-01-22 23:16:45,852 [Client-1] INFO
> > > o.a.drill.exec.rpc.user.UserClient - Channel closed
> > > /192.168.200.129:57436<http://192.168.200.129:57436> <-->
> > > /192.168.200.129:31010<http://192.168.200.129:31010>.
> > > 2016-01-22 23:16:45,853 [qtp1683069650-5882] ERROR
> > > o.a.d.e.server.rest.QueryResources - Query from Web UI Failed
> > > org.apache.drill.common.exceptions.UserRemoteException: DATA_WRITE
> ERROR:
> > > Failed to drop table
> > >
> > > -Kumiko
> > > -----Original Message-----
> > > From: Jason Altekruse
> > > [mailto:altekruseja...@gmail.com<mailto:altekruseja...@gmail.com>]
> > > Sent: Friday, January 22, 2016 3:52 PM
> > > To: user <user@drill.apache.org<mailto:user@drill.apache.org>>
> > > Cc: Kevin Verhoeven
> > > <kevin.verhoe...@ds-iq.com<mailto:kevin.verhoe...@ds-iq.com>>; Ki Kang <
> > > ki.k...@ds-iq.com<mailto:ki.k...@ds-iq.com>>
> > > Subject: Re: DATA_WRITE ERROR: Failed to drop table
> > >
> > > Looking at where this message is produced, there was likely a
> > > lower level filesystem error that was not related to permissions.
> > > Can you check the logs for more info?
> > >
> > > The error message you see on the command line should have an error
> > > ID you can use to search the logs.
> > >
> > > - Jason
> > >
> > > On Fri, Jan 22, 2016 at 3:22 PM, Kumiko Yada
> > > <kumiko.y...@ds-iq.com<mailto:kumiko.y...@ds-iq.com>>
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > > I created the table using CREATE TABLE AS (CTAS) command, then I
> > > > tried to DROP this directory with DROP TABLE command, I'm
> > > > getting the error "DATA_WRITE ERROR: Failed to drop table".
> > > >
> > > > I verified that I have a full permission to the directory. Has
> > > > anyone seen this?
> > > >
> > > > Thanks
> > > > Kumiko
> > > >
> > >
> >
>
