Hello,
Thanks. Please take the following steps:
1. Create a JIRA about the issues (Ignored the operation if no code to be
changed).
2. Update the docs (on the `gh-pages` branch).
3. Create a PR on our GitHub (add the `[DOC UPDATE]` in the front of title).
> 2021年3月30日 下午5:10，Mehmet - 写道：
>
>
Hi Charles,
Okay, I can prepare a document about that. Btw, HDFS Storage plugin section
on the Drill official document does not contain this detail(Client files
deployment). If you want I can also open a PR for that section:
It would be nice to document the solution somewhere so that if someone else has
this issue there is some reference.
Best,
-- C
> On Mar 26, 2021, at 11:23 AM, luoc wrote:
>
> Hello,
> Glad to see that you have resolved the issues. BTW, Are you interested in
> contribute the ideas (described
Hello,
Glad to see that you have resolved the issues. BTW, Are you interested in
contribute the ideas (described the solution) in our JIRA? We have a JIRA about
testing the compatibility of drill on CDH.
Also welcome to join our Slack channel:
https://bit.ly/3t4rozO
> 在
Hi,
We have just solved this problem. I would like to talk about our solution
to contribute to the community. Maybe other friends may face the same
problem.
We noticed the reason for that problem is trying to connect CDH's HDFS
without client deployment. So, firstly we deployed our Hadoop client
Hi,
I think the solution to this problem depends on your initiative. Because I
planned to download CDH 6.3.3, but it seems that Cloudera have requested a
license from February 1. Orz...
So, Is it possible that you are using mini cluster (installed HDFS roles
service only) to confirm that drill
Hi,
I don't have any plan yet but I was trying it on our Dev cluster, I'm
thinking of trying it on the prod cluster as well.
Btw, you're right, as far as I see in drillbit.log and
"jars/3rdparty/hadoop-client-3.2.1.jar" folder, I have been using
hadoop-client-3.2.1.jar (My Hadoop version is
Hi,
I am so sorry to hear that. Do you have any plans? And, have you used
hadoop-client-3.2.1.jar to connect the cluster directly? because of the drill
include the hadoop version is 3.2.1.
> 2021年2月28日 上午4:28，Mehmet - 写道：
>
> Hi,
>
> Yes, you're right and I agree with you. Regarding your
Hi,
Yes, you're right and I agree with you. Regarding your last comment; I can
get and read any file from HDFS via terminal. I have attached the
ScreenShot.
Thank you.
27 Şub 2021 Cmt, saat 05:58 tarihinde luoc şunu yazdı:
> Hi,
> Drill 1.18 works well on CDH 5.13. the difference is that I
Hi,
Drill 1.18 works well on CDH 5.13. the difference is that I did not enable
krb, then drill is supported for hadoop 3.x. (CDH 5.x based on hadoop 2.6, 6.x
based on hadoop 3.x)
May the `list` commands only need to connect NameNode for get metadata
(without DataNode), So recommend that you
Hi,
Stack Trace: https://paste.ubuntu.com/p/nFvygSpcjy/
Yes DataNode port is opening and accessible and any firewall problem is
impossible because the Drill was established on the same nodes with
Cloudera cluster.
I consider there is no problem with authentication. Because I can list the
hdfs
Hi,
The storage config is correct. then enabled the Kerberos security. So, please
check the java stack trace to ensure not the authentication problem.
Is it possible to use dfs client connect the HDFS for reading the csv file?
The DataNode port is opening and accessible?
> 2021年2月26日
Hi,
1. Drill version: 1.18.0
2. HDFS Version: Hadoop 3.0-cdh6.3.3
3. Storage config: https://paste.ubuntu.com/p/5Dk9jVCxYr/
4. drill-env.sh file: https://paste.ubuntu.com/p/MGNG4zhbrk/
Thank you.
BR.
luoc , 26 Şub 2021 Cum, 16:14 tarihinde şunu yazdı:
> Hi,
> That does not seem like an
Hi,
That does not seem like an issues with Drill.
Would you please provides more helpful information :
1. Drill version
2. HDFS version
3. Storage config
> 2021年2月26日 下午3:32，Mehmet - 写道：
>
> Hi Team,
>
> I have a problem with Hdfs query on Drill. When I run a "SHOW FILES in
> root.`tmp/` ",
Hi Team,
I have a problem with Hdfs query on Drill. When I run a "SHOW FILES in
root.`tmp/` ", I can list the files correctly.
Bu when I run a select query like "Select * from root.`tmp/` it throws
below error.
Notes:
- I have already checked the state of hdfs health(via dfsadmin and hdfs ui)
and
15 matches
Mail list logo
