novatechflow commented on PR #767: URL: https://github.com/apache/wayang/pull/767#issuecomment-4629377103
lot of changes: - `bin/wayang-submit `now adds the Java 17 `--add-opens / --add-exports` flags automatically. - base Dockerfile now builds from the assembly tarball, prunes `sources/javadocs/README` files, creates a smoke input, and enables `FLAG_WAYANG=true` using an empty config file. - Hadoop `FileSystems` registration is lazy, so clean Java-only images do not fail when Hadoop classes are absent. HDFS behavior should remain intact when Hadoop jars are present on the classpath at startup, tests passed on that. - Python API host is now configurable via `wayang.api.python.url,` `wayang.api.python.host`, `wayang.api.python.port`, or `WAYANG_API_URL / WAYANG_API_HOST / WAYANG_API_PORT`. - Added optional `python/Dockerfile`, `python/docker/entrypoint.sh`, and `python/examples/wordcount.py.` - Python-enabled image keeps Python deps out of the base Wayang image; it layers Python 3.11 and `pywy` on top of the assembled Wayang runtime. - Docker workflow now uses `docker buildx build --load`, runs Java WordCount smoke, builds the Python image, and smoke-tests Python against REST by hostname. **Verified**: - `bash -n bin/wayang-submit` - `python3 -m py_compile` ... - Maven install/package with Java 17 - `docker buildx build --load -t apache-wayang:ci .` - Java WordCount in clean container passed: found `apache`, `test`, `smoke`, `wayang`, `docker` - Base image prune check returned no `README.md, *-sources.jar, or *-javadoc.jar` - `docker buildx build --load -f python/Dockerfile -t apache-wayang-python:ci .` - Python REST/client smoke passed using `WAYANG_API_HOST=wayang-rest-local;` REST logs show `Successfully executed WayangJob`, and output was written in the REST container. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
