-
Notifications
You must be signed in to change notification settings - Fork 408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The status of the rule is Stopped #596
Comments
Could you please refer to this link - #569? It can be solved by compile a native build with edgex support. |
I was build kuiper with "make build_with_edgex",so Kuiper should support EdgeX. Kuiper's plugins/source folder is empty. |
The edgex will be compiled into |
Shouldn't Kuiper be compiled into edgex enabled binaries? build kuiper with "make build_with_edgex" ,return "Build successfully" |
The separated binary version of Kuiper does not include EdgeX source because EdgeX requires additional libraries (zeromq library), and Kuiper cannot be started without installing the lib. Kuiper is not only for EdgeX, so it will confuse user that do not use EdgeX.
It seems there already have an existed kuiperd process, you need to kill it. |
Thank you very much for your patient answers . I understand what you mean. But I think it’s not a compilation problem . Because I ran the source code of edgex-go, installed zeromq, and compiled and ran successfully. The readme file under kuiper is written to be compiled with "make build_with_edgex", which means that this version of kuiper contains the source of Edgex. |
1、create stream
2、create rule
3、show rule status
Connecting to 127.0.0.1:20498...
Question:
When creating a stream,TYPE="edgex",What is the meaning of “TYPE” ,and “ cannot get the plugin file path: invalid name edgex: not exist”,the “edgex” is the file “edgex.yaml” in etc/source?? this file is exists.
The text was updated successfully, but these errors were encountered: