Job Binary Internal data name is difficult to understand

[Yuhara Motoki]

When register Job Binary Internal,
The name is automatically determined by regstration date.

It is difficult to know which data registered.

Example
$ sahara job-binary-data-create --file input.txt
+--------------------------------------------------------------+-----------------+
| id | name |
+--------------------------------------------------------------+-----------------+
| e706cc63-a38e-40fe-bcd1-cf4a46cd5277 | d20150305080909 |
+--------------------------------------------------------------+-----------------+

[lu huichun (lhcxx0508)]

hi Yuhara Motoki

I think you should use sahara job-binary-create command, there is a parameter called --name.

if you use sahara job-binary-data-create, it only create data in the DB, but can not show up in the horizon page in job binary page

[Sergey Lukjanov (slukjanov)]

Yeah, the job-binary-data-create just creates the binary entry in sahara db, it's not important how it's named.

[Yuhara Motoki (yuhara-motoki)]

Hi

Thank you for your comment.

I use job-binary-data-create to store some HiveQL scripts.
And I use that job-binary-internal for creating job-binary-create.
ex)
sahara job-binary create --name <job-binary-name> --url internal-db://<job-binary-internal-id>

I'm not sure if I don't create job-binary-internal, where I store HiveQL scripts and How I write value of --url option.