Public bug reported: Priority *wishlist*:
This is a fix that was from the sahara-dashboard repo that came in after the merge was started. It needs to be ported to the horizon codebase post-merge. Original patch: https://review.openstack.org/#/c/92833/ Sahara currently demands that the URL for an hdfs data source begins with the hdfs scheme "hdfs://". The UI enforces this restriction as well. When the hdfs scheme is specified, hadoop requires the hostname and/or port to be specified as well. For use of an external hdfs, of course, the host/port are always necessary. On a long running cluster, the local hdfs can be used by specifying the host/port of the local namenode in the path so that data can be read/written to the cluster hdfs, for example "hdfs://test- master:9000/user/hadoop/input". However, hadoop supports simpler absolute and relative paths to access the local hdfs without specification of the host and port. ** Affects: horizon Importance: Undecided Assignee: Chad Roberts (croberts) Status: New ** Description changed: Priority *wishlist*: This is a fix that was from the sahara-dashboard repo that came in after the merge was started. It needs to be ported to the horizon codebase post-merge. + + Original patch: https://review.openstack.org/#/c/92833/ Sahara currently demands that the URL for an hdfs data source begins with the hdfs scheme "hdfs://". The UI enforces this restriction as well. When the hdfs scheme is specified, hadoop requires the hostname and/or port to be specified as well. For use of an external hdfs, of course, the host/port are always necessary. On a long running cluster, the local hdfs can be used by specifying the host/port of the local namenode in the path so that data can be read/written to the cluster hdfs, for example "hdfs://test- master:9000/user/hadoop/input". However, hadoop supports simpler absolute and relative paths to access the local hdfs without specification of the host and port. ** Changed in: horizon Assignee: (unassigned) => Chad Roberts (croberts) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1336283 Title: [data processing] Allow for HDFS data sources without prefix Status in OpenStack Dashboard (Horizon): New Bug description: Priority *wishlist*: This is a fix that was from the sahara-dashboard repo that came in after the merge was started. It needs to be ported to the horizon codebase post-merge. Original patch: https://review.openstack.org/#/c/92833/ Sahara currently demands that the URL for an hdfs data source begins with the hdfs scheme "hdfs://". The UI enforces this restriction as well. When the hdfs scheme is specified, hadoop requires the hostname and/or port to be specified as well. For use of an external hdfs, of course, the host/port are always necessary. On a long running cluster, the local hdfs can be used by specifying the host/port of the local namenode in the path so that data can be read/written to the cluster hdfs, for example "hdfs://test- master:9000/user/hadoop/input". However, hadoop supports simpler absolute and relative paths to access the local hdfs without specification of the host and port. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1336283/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
