I think both approaches are fine for this project. Using Jupyter will be more detailed and fundamental, while the application approach will be more engaging.
I think both approaches are fine for this project. Using Jupyter will be more detailed and fundamental, while the application approach will be more engaging.
...
@@ -69,6 +70,9 @@ Use `OPEN` or `GETFILEBLOCKLOCATIONS` to get that.
...
@@ -69,6 +70,9 @@ Use `OPEN` or `GETFILEBLOCKLOCATIONS` to get that.
**Q10: return specific line of output by recalculate with replicated**`input.parquet`
**Q10: return specific line of output by recalculate with replicated**`input.parquet`
# Application Way
# Application Way
-->
Offer them `docker-compose.yml` , `Dockerfile.sql` , `Dockerfile.hdfs` and `Dockerfile.notebook`, while they are required to complete `Dockerfile.namenode`, `Dockerfile.datanode`.
Offer them `docker-compose.yml` , `Dockerfile.sql` , `Dockerfile.hdfs` and `Dockerfile.notebook`, while they are required to complete `Dockerfile.namenode`, `Dockerfile.datanode`.
Then the main system can be established by running `docker compose up`.
Then the main system can be established by running `docker compose up`.
