Skip to content

using PYTHONPATH or alternative in streamparse #474

@z11373

Description

@z11373

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions