-
Notifications
You must be signed in to change notification settings - Fork 345
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
property "type" must be provided when reading from the Broker #5529
Comments
Thanks for reporting. Do you mind providing the dump of your Integration spec. The Pipe should have created an Integration named |
There is no integration created. The message on the
and here see there are no such resources:
|
@squakez regardless if I set the: ...
properties:
type: <my cloud event type>
... on the |
Update: I restarted over and now this worked: apiVersion: camel.apache.org/v1
kind: Pipe
metadata:
name: log-sink-pipe
spec:
source:
ref:
kind: Broker
apiVersion: eventing.knative.dev/v1
name: kamelet
properties:
type: com.corp.my.beer.source
sink:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1
name: log-sink Gave me the trigger I wanted. |
OK, I found it out: When I edit this pipe, the CLI says I have to I guess that's also a diffenrent bug? |
I think the root cause is the second bug you've reported. If you create this from scratch with the right property does it work? in such case, feel free to close this issue and we'll work to fix #5531. |
I think this is two pieces:
|
Okey, we'll keep this open to answer the first question, thanks. |
In the past we hit certain problems when using Brokers (see apache/camel-k-runtime#536). However, this should have been solved as we now leverage directly Camel Knative component. I'm proceeding with a fix. |
@squakez I think this is not the same as apache/camel-k-runtime/issues/536. Yes, we have had problems with the broker name (e.g. when using a customized broker name other than default) and this one has been fixed already. This one here is different. The type information mentioned here refers to the cloud event type information that is used to filter the event stream. In a Pipe users currently need to set this event type in order to filter the event stream, but it is totally valid to read all events from a broker without any type filter. We need to fix the Trigger filter that is created as part of Camel K Knative traits to allow users to get the full event stream without any filter. |
Thanks for having a look at that @christophd - I am dropping the PR and you can continue the work as I understood you were about to work on a side request related. Thanks! |
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
- Fixes apache#5537: Support filter attributes other than event type (e.g. source, subject, extensions) - Fixes apache#5529: Allows empty filter to consume the full event stream - Fixes apache#5446: Knative Trigger creation is only based on event type attribute - Fixes apache#5577: Consistently support "cloudEventsType" property in Pipes source/sink - Update documentation and improve Knative Kamelet/Pipe user guide
What happened?
Creating a logger-pipe that reads from the broker seems to not work:
In theory it should create a trigger that has no filter, which is valid
Steps to reproduce
Relevant log output
The text was updated successfully, but these errors were encountered: