refactor noop transform to use dpk_ structures

[daw3rd]

Why are these changes needed?

To adapt to the new transform project structure.

Related issue number (if any).

#774

[shahrokhDaijavad]

@daw3rd I have reviewed 2 things so far:

1. Going over your README file
2. Testing the code by running make run-cli-sample successfully

On the README, everything looks good, but I have a suggestion for improvement:
In the Usage section, both CLI and make run-cli-sample use the Python runtime. Since noop is a good learning transform for first-time users, it makes sense to add two small sections of code for using CLI to run Ray and Spark runtimes. An example is the README for fdedup here: https://github.com/IBM/data-prep-kit/blob/noop-refactor/transforms/universal/fdedup/README.md.
Since we have the generic: python -m dpk_$(TRANSFORM_NAME).runtime
an alternative, if you do not want to have new Ray and Spark sections in the README, is just changing the CLI part to:
python -m dpk_noop/transform_python --noop_sleep_sec 10 ...
=>
python -m dpk_noop/transform_runtime --noop_sleep_sec 10 ... and saying that runtime can be python, ray, or spark.

[daw3rd]

@daw3rd I have reviewed 2 things so far:

1. Going over your README file

2. Testing the code by running `make run-cli-sample` successfully

On the README, everything looks good, but I have a suggestion for improvement: In the Usage section, both CLI and make run-cli-sample use the Python runtime. Since noop is a good learning transform for first-time users, it makes sense to add two small sections of code for using CLI to run Ray and Spark runtimes. An example is the README for fdedup here: https://github.com/IBM/data-prep-kit/blob/noop-refactor/transforms/universal/fdedup/README.md. Since we have the generic: python -m dpk_$(TRANSFORM_NAME).runtime an alternative, if you do not want to have new Ray and Spark sections in the README, is just changing the CLI part to: python -m dpk_noop/transform_python --noop_sleep_sec 10 ... => python -m dpk_noop/transform_runtime --noop_sleep_sec 10 ... and saying that runtime can be python, ray, or spark.

I added an example of running the Ray runtime. Do we need to show how to run all the local_*.py?

[shahrokhDaijavad]

@daw3rd I have reviewed 2 things so far:

1. Going over your README file

2. Testing the code by running `make run-cli-sample` successfully

On the README, everything looks good, but I have a suggestion for improvement: In the Usage section, both CLI and make run-cli-sample use the Python runtime. Since noop is a good learning transform for first-time users, it makes sense to add two small sections of code for using CLI to run Ray and Spark runtimes. An example is the README for fdedup here: https://github.com/IBM/data-prep-kit/blob/noop-refactor/transforms/universal/fdedup/README.md. Since we have the generic: python -m dpk_$(TRANSFORM_NAME).runtime an alternative, if you do not want to have new Ray and Spark sections in the README, is just changing the CLI part to: python -m dpk_noop/transform_python --noop_sleep_sec 10 ... => python -m dpk_noop/transform_runtime --noop_sleep_sec 10 ... and saying that runtime can be python, ray, or spark.

I added an example of running the Ray runtime. Do we need to show how to run all the local_*.py?

@daw3rd We don't need to show how to run all 3, but when you show the command line for Ray runtime, you want to add a sentence saying that the runtime could be python, ray or spark.

[daw3rd]

@daw3rd I have reviewed 2 things so far:

1. Going over your README file

2. Testing the code by running `make run-cli-sample` successfully

On the README, everything looks good, but I have a suggestion for improvement: In the Usage section, both CLI and make run-cli-sample use the Python runtime. Since noop is a good learning transform for first-time users, it makes sense to add two small sections of code for using CLI to run Ray and Spark runtimes. An example is the README for fdedup here: https://github.com/IBM/data-prep-kit/blob/noop-refactor/transforms/universal/fdedup/README.md. Since we have the generic: python -m dpk_$(TRANSFORM_NAME).runtime an alternative, if you do not want to have new Ray and Spark sections in the README, is just changing the CLI part to: python -m dpk_noop/transform_python --noop_sleep_sec 10 ... => python -m dpk_noop/transform_runtime --noop_sleep_sec 10 ... and saying that runtime can be python, ray, or spark.

I added an example of running the Ray runtime. Do we need to show how to run all the local_*.py?

@daw3rd We don't need to show how to run all 3, but when you show the command line for Ray runtime, you want to add a sentence saying that the runtime could be python, ray or spark.

@shahrokhDaijavad OK I added spark example and was more specific about running the various runtimes. If you want more, maybe get together to discuss.

[shahrokhDaijavad]

Thanks, @daw3rd Looks good!

[touma-I]

trying to go through this with a fine comb as the noop is a reference for everything we do. will have some more tomorrow during our call. thanks

[touma-I]

more comments in preparation for our call. thanks