You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have our python module that is called from our streamparse topology, right now we dpkg the module in the site-packages folder, but we want to have a way to override the location, for example if engineer wants to try his change, he/she can just redirect streamparse to look for the module at specific location (instead of in site-packages folder).
Will setting PYTHONPATH work for our case? I think it'll work for submitting topology only, but then likely fail when Storm spawn the spout/bolt process (unless the env var is being propagated). If setting PYTHONPATH is not right solution for our case, is there a recommended solution? Thanks!
The text was updated successfully, but these errors were encountered:
Our case is we have our python modules (used in spout/bolt code) automatically installed on the machines, and on dev machine engineer sometimes want to run their own version for quick test, etc. We want to tell streamparse to temporary look for the modules in that override location, instead of the installed location. I really appreciate if someone can share their experience on this matter, or provide us guidelines. Thanks!
We have our python module that is called from our streamparse topology, right now we dpkg the module in the site-packages folder, but we want to have a way to override the location, for example if engineer wants to try his change, he/she can just redirect streamparse to look for the module at specific location (instead of in site-packages folder).
Will setting PYTHONPATH work for our case? I think it'll work for submitting topology only, but then likely fail when Storm spawn the spout/bolt process (unless the env var is being propagated). If setting PYTHONPATH is not right solution for our case, is there a recommended solution? Thanks!
The text was updated successfully, but these errors were encountered: