[jira] [Comment Edited] (HDDS-631) Ozone classpath shell command is not working
[
https://issues.apache.org/jira/browse/HDDS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758545#comment-16758545
]
Anu Engineer edited comment on HDDS-631 at 2/1/19 6:09 PM:
---
+1, feel free to commit at will. Thanks for getting this done, just that if you
run this command without any options, can you please print out all paths, and
instruction on how to modify each one?
was (Author: anu):
+1, feel free to commit at will. Thanks for getting this done.
> Ozone classpath shell command is not working
>
>
> Key: HDDS-631
> URL: https://issues.apache.org/jira/browse/HDDS-631
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
>Reporter: Nanda kumar
>Assignee: Elek, Marton
>Priority: Blocker
> Attachments: HDDS-631.00.patch, HDDS-631.001.patch
>
>
> In the ozone package (tar) the ozone and its dependency jars are copied to an
> incorrect location. We use to have the jars in {{share/hadoop/}} for
> each module. Those directories are empty now. All the jars are placed in
> {{share/ozone/lib}} directory.
> With this structure when we run {{ozone classpath}} command, we get an
> incorrect output.
> {code}
> $ bin/ozone classpath
> /Users/nvadivelu/apache/ozone-0.4.0-SNAPSHOT/etc/hadoop:/Users/nvadivelu/apache/ozone-0.4.0-SNAPSHOT/share/hadoop/common/*
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HDDS-631) Ozone classpath shell command is not working
[
https://issues.apache.org/jira/browse/HDDS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758545#comment-16758545
]
Anu Engineer edited comment on HDDS-631 at 2/1/19 6:10 PM:
---
+1, feel free to commit at will. Thanks for getting this done, just that if you
run this command without any options, can you please print out all paths, and
instruction on how to modify each one? I mean sometimes it is easy as a
developer and support engineer to see all this info without typing the same
command 4 times.
was (Author: anu):
+1, feel free to commit at will. Thanks for getting this done, just that if you
run this command without any options, can you please print out all paths, and
instruction on how to modify each one?
> Ozone classpath shell command is not working
>
>
> Key: HDDS-631
> URL: https://issues.apache.org/jira/browse/HDDS-631
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
>Reporter: Nanda kumar
>Assignee: Elek, Marton
>Priority: Blocker
> Attachments: HDDS-631.00.patch, HDDS-631.001.patch
>
>
> In the ozone package (tar) the ozone and its dependency jars are copied to an
> incorrect location. We use to have the jars in {{share/hadoop/}} for
> each module. Those directories are empty now. All the jars are placed in
> {{share/ozone/lib}} directory.
> With this structure when we run {{ozone classpath}} command, we get an
> incorrect output.
> {code}
> $ bin/ozone classpath
> /Users/nvadivelu/apache/ozone-0.4.0-SNAPSHOT/etc/hadoop:/Users/nvadivelu/apache/ozone-0.4.0-SNAPSHOT/share/hadoop/common/*
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HDDS-631) Ozone classpath shell command is not working
[
https://issues.apache.org/jira/browse/HDDS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755890#comment-16755890
]
Elek, Marton edited comment on HDDS-631 at 2/1/19 1:32 PM:
---
bq. Still, we need to have a proper directory structure for the jars.
I am not sure. The classpath can be read from the .classpath files with the
shell command even without structure. I can create a poc to show this...
was (Author: elek):
b1. Still, we need to have a proper directory structure for the jars.
I am not sure. The classpath can be read from the .classpath files with the
shell command even without structure. I can create a poc to show this...
> Ozone classpath shell command is not working
>
>
> Key: HDDS-631
> URL: https://issues.apache.org/jira/browse/HDDS-631
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
>Reporter: Nanda kumar
>Assignee: Elek, Marton
>Priority: Blocker
> Attachments: HDDS-631.00.patch
>
>
> In the ozone package (tar) the ozone and its dependency jars are copied to an
> incorrect location. We use to have the jars in {{share/hadoop/}} for
> each module. Those directories are empty now. All the jars are placed in
> {{share/ozone/lib}} directory.
> With this structure when we run {{ozone classpath}} command, we get an
> incorrect output.
> {code}
> $ bin/ozone classpath
> /Users/nvadivelu/apache/ozone-0.4.0-SNAPSHOT/etc/hadoop:/Users/nvadivelu/apache/ozone-0.4.0-SNAPSHOT/share/hadoop/common/*
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HDDS-631) Ozone classpath shell command is not working
[
https://issues.apache.org/jira/browse/HDDS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755812#comment-16755812
]
Sandeep Nemuri edited comment on HDDS-631 at 1/30/19 9:15 AM:
--
+1 for {{ozone classpath client}}, Without this we have to manually find the
lib location and add it to client(hadoop) classpath.
When hdfs is trying to access o3fs, If we only add
{{hadoop-ozone-filesystem.jar}} to HADOOP_CLASSPATH. The client fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.ratis.thirdparty.com.google.protobuf.ByteString
{noformat}
Apart form {{hadoop-ozone-filesystem.jar}} we had to add the ozone lib
directory to access o3fs from hdfs.
was (Author: sandeep nemuri):
+1 for {{ozone classpath clients}}, Without this we have to manually find the
lib location and add it to client(hadoop) classpath.
When hdfs is trying to access o3fs, If we only add
{{hadoop-ozone-filesystem.jar}} to HADOOP_CLASSPATH. The client fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.ratis.thirdparty.com.google.protobuf.ByteString
{noformat}
Apart form {{hadoop-ozone-filesystem.jar}} we had to add the ozone lib
directory to access o3fs from hdfs.
> Ozone classpath shell command is not working
>
>
> Key: HDDS-631
> URL: https://issues.apache.org/jira/browse/HDDS-631
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
>Reporter: Nanda kumar
>Priority: Blocker
> Attachments: HDDS-631.00.patch
>
>
> In the ozone package (tar) the ozone and its dependency jars are copied to an
> incorrect location. We use to have the jars in {{share/hadoop/}} for
> each module. Those directories are empty now. All the jars are placed in
> {{share/ozone/lib}} directory.
> With this structure when we run {{ozone classpath}} command, we get an
> incorrect output.
> {code}
> $ bin/ozone classpath
> /Users/nvadivelu/apache/ozone-0.4.0-SNAPSHOT/etc/hadoop:/Users/nvadivelu/apache/ozone-0.4.0-SNAPSHOT/share/hadoop/common/*
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HDDS-631) Ozone classpath shell command is not working
[
https://issues.apache.org/jira/browse/HDDS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16648161#comment-16648161
]
Nanda kumar edited comment on HDDS-631 at 1/30/19 8:30 AM:
---
Sounds good, then we can have different commands to get the classpath.
{{ozone classpath om}}
{{ozone classpath scm}}
{{ozone classpath client}}
Still, we need to have a proper directory structure for the jars.
was (Author: nandakumar131):
Sounds good, then we can have different commands to get the classpath.
{{ozone classpath om}}
{{ozone classpath scm}}
{{ozone classpath clients}}
Still, we need to have a proper directory structure for the jars.
> Ozone classpath shell command is not working
>
>
> Key: HDDS-631
> URL: https://issues.apache.org/jira/browse/HDDS-631
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
>Reporter: Nanda kumar
>Priority: Blocker
> Attachments: HDDS-631.00.patch
>
>
> In the ozone package (tar) the ozone and its dependency jars are copied to an
> incorrect location. We use to have the jars in {{share/hadoop/}} for
> each module. Those directories are empty now. All the jars are placed in
> {{share/ozone/lib}} directory.
> With this structure when we run {{ozone classpath}} command, we get an
> incorrect output.
> {code}
> $ bin/ozone classpath
> /Users/nvadivelu/apache/ozone-0.4.0-SNAPSHOT/etc/hadoop:/Users/nvadivelu/apache/ozone-0.4.0-SNAPSHOT/share/hadoop/common/*
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Comment Edited] (HDDS-631) Ozone classpath shell command is now working
[
https://issues.apache.org/jira/browse/HDDS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16646842#comment-16646842
]
Bharat Viswanadham edited comment on HDDS-631 at 10/11/18 6:11 PM:
---
Thank You [~nandakumar131] for reporting this issue.
This is caused by HDDS-447.
After doing the slight modification to scripts it is showing classpath.
Attached the patch.
But one thing is for each component we have a classpath and that defines the
jars needed from ozone/share/lib/, but for classpath just adding that will
cause multiple version of jars in that. This one I was not sure how to address
it. Or is it okay to just show up ozone/share/lib/*?
cc [~elek]
Now:
hadoop@1b442e6641a0:~$ ozone classpath
/opt/hadoop/etc/hadoop:/opt/hadoop/share/hadoop/common/*:/opt/hadoop/share/ozone/lib/*
{code:java}
hadoop@1b442e6641a0:~$ ozone classpath --glob
[jira] [Comment Edited] (HDDS-631) Ozone classpath shell command is now working
[
https://issues.apache.org/jira/browse/HDDS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16646842#comment-16646842
]
Bharat Viswanadham edited comment on HDDS-631 at 10/11/18 6:10 PM:
---
Thank You [~nandakumar131] for reporting this issue.
This is caused by HDDS-447.
After doing the slight modification to scripts it is showing classpath.
Attached the patch.
But one thing is for each component we have a classpath and that defines the
jars needed from ozone/share/lib/, but for classpath just adding that will
cause multiple version of jars in that. This one I was not sure how to address
it. Or is it okay to just show up ozone/share/lib/*?
cc [~elek]
Now:
hadoop@1b442e6641a0:~$ ozone classpath
/opt/hadoop/etc/hadoop:/opt/hadoop/share/hadoop/common/*:/opt/hadoop/share/ozone/lib/*
{code:java}
hadoop@1b442e6641a0:~$ ozone classpath --glob
