nicknezis commented on issue #881:
URL: https://github.com/apache/incubator-heron/issues/881#issuecomment-659862401
It seems there are two locations that are relevant to the PEX discussion.
Are there any I'm missing? What changes would be needed to use the output of
`py_binary` build task? Would this be easier or harder for analytics
developers? I'm currently looking to use {Py}Gradle and the LinkedIn PEX plugin
to package my analytics. It would not be ideal if we forced analytic developers
to only use Bazel.
1. Heron Executor: Runs a pyton binary with the pex file as an argument (per
component)
https://github.com/apache/incubator-heron/blob/e1dda9acfded22ac1de86d73981118488d7a3b19/heron/executor/src/python/heron_executor.py#L724
2. Heron CLI checks for `pex` extension:
https://github.com/apache/incubator-heron/blob/e1dda9acfded22ac1de86d73981118488d7a3b19/heron/tools/cli/src/python/submit.py#L439
3. Heron CLI: Uses `pex_loader` library to load the Topology class at submit
time.
https://github.com/apache/incubator-heron/blob/e1dda9acfded22ac1de86d73981118488d7a3b19/heron/tools/cli/src/python/execute.py#L124
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
