Beam pipeline on Dataflow runner failed with import of module Protobuf output metrics_pb2.py failed
up vote
0
down vote
favorite
To validate the message structure before publishing to Pub/Sub and after consuming from Pub/Sub I use Protobuf messages. The same protobuf compiled output metrics_pb2.py is inside both publisher Python app and subscriber Beam App.
My Beam pipeline works on my local without any problem.
But when I try to run it on Google Dataflow, I got this error
PicklingError: Can't pickle <class 'metrics_pb2.MetricGlucose'>: import of module metrics_pb2 failed
Even I have a multi module data pipeline and I am using a setup.py file, and all other modules can be found by pipeline, I don't know why pipeline cannot see those protobuf compiled output files.
Any idea?
python
google-cloud-platform protocol-buffers google-cloud-dataflow apache-beam asked Nov 21 at 17:18
Erdem A
93
add a comment |
up vote
0
down vote
favorite
To validate the message structure before publishing to Pub/Sub and after consuming from Pub/Sub I use Protobuf messages. The same protobuf compiled output metrics_pb2.py is inside both publisher Python app and subscriber Beam App.
My Beam pipeline works on my local without any problem.
But when I try to run it on Google Dataflow, I got this error
PicklingError: Can't pickle <class 'metrics_pb2.MetricGlucose'>: import of module metrics_pb2 failed
Even I have a multi module data pipeline and I am using a setup.py file, and all other modules can be found by pipeline, I don't know why pipeline cannot see those protobuf compiled output files.
Any idea?
python
google-cloud-platform protocol-buffers google-cloud-dataflow apache-beam asked Nov 21 at 17:18
Erdem A
93
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
To validate the message structure before publishing to Pub/Sub and after consuming from Pub/Sub I use Protobuf messages. The same protobuf compiled output metrics_pb2.py is inside both publisher Python app and subscriber Beam App.
My Beam pipeline works on my local without any problem.
But when I try to run it on Google Dataflow, I got this error
PicklingError: Can't pickle <class 'metrics_pb2.MetricGlucose'>: import of module metrics_pb2 failed
Even I have a multi module data pipeline and I am using a setup.py file, and all other modules can be found by pipeline, I don't know why pipeline cannot see those protobuf compiled output files.
Any idea?
python
google-cloud-platform protocol-buffers google-cloud-dataflow apache-beam asked Nov 21 at 17:18
Erdem A
93
To validate the message structure before publishing to Pub/Sub and after consuming from Pub/Sub I use Protobuf messages. The same protobuf compiled output metrics_pb2.py is inside both publisher Python app and subscriber Beam App.
My Beam pipeline works on my local without any problem.
But when I try to run it on Google Dataflow, I got this error
PicklingError: Can't pickle <class 'metrics_pb2.MetricGlucose'>: import of module metrics_pb2 failed
Even I have a multi module data pipeline and I am using a setup.py file, and all other modules can be found by pipeline, I don't know why pipeline cannot see those protobuf compiled output files.
Any idea?
python
google-cloud-platform protocol-buffers google-cloud-dataflow apache-beam python
google-cloud-platform protocol-buffers google-cloud-dataflow apache-beam asked Nov 21 at 17:18
Erdem A
93
asked Nov 21 at 17:18
Erdem A
93
asked Nov 21 at 17:18
Erdem A
93
asked Nov 21 at 17:18
Erdem A
93
asked Nov 21 at 17:18
Erdem A
93
93
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53417453%2fbeam-pipeline-on-dataflow-runner-failed-with-import-of-module-protobuf-output-me%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
