Really good work!
I think this is just the first step, we can use a similar approach for the
others flavours.
But we need to document everything really well and we need to rethink about the
release process, I guess.
Thanks!
--
Andrea Cosentino
--
Apache Camel
Hi
+1
This is great stuff.
So just think how would the developer do when eg you add a new
component in the main Camel repo, lets call it components/camel-foobar
?
Then you go to camel-spring-boot and want to generate a
camel-foobar-starter because it should support SB too (Mind that not
all comp
Hi everyone,
Since Camel 3.0.0 has been released, and given we now have different
subprojects, I'd like to discuss the possibility of moving the spring boot
support into a different git repository.
I see several benefits:
* being able to support different versions of spring boot
* better decou
valdar commented on issue #31: run integration test insided github actions
URL:
https://github.com/apache/camel-kafka-connector/issues/31#issuecomment-563433113
If the time is reasonable we can have them for each PR. Not sure about
resources available though...
---
valdar edited a comment on issue #31: run integration test insided github
actions
URL:
https://github.com/apache/camel-kafka-connector/issues/31#issuecomment-563296282
See if it is possible to have integrations tests running as github actions,
not for each PR but once in a while (nightly?
orpiske edited a comment on issue #31: run integration test insided gihub
actions
URL:
https://github.com/apache/camel-kafka-connector/issues/31#issuecomment-563406117
Personally, I prefer having the tests run for each PR, as it makes it easier
to spot some issues. Depending on the resour
orpiske commented on issue #31: run integration test insided gihub actions
URL:
https://github.com/apache/camel-kafka-connector/issues/31#issuecomment-563406117
Personally, I prefer having the tests run for each PR, as it makes it easier
to spot some issues.
I also think it would a
Great! Thank you very much!
Am 09.12.2019 um 20:07 schrieb Andrea Cosentino:
I already created an infra issue for camel-kafka-connector. I'll do the
same for the camel-website.
Il lun 9 dic 2019, 20:04 Pascal Schumacher ha
scritto:
Hello,
what about sending the camel-kafka-connector and cam
I already created an infra issue for camel-kafka-connector. I'll do the
same for the camel-website.
Il lun 9 dic 2019, 20:04 Pascal Schumacher ha
scritto:
> Hello,
>
> what about sending the camel-kafka-connector and camel-website github
> notification mails to the camel-commits mailing list ins
Hello,
what about sending the camel-kafka-connector and camel-website github
notification mails to the camel-commits mailing list instead of to the
camel-dev mailing list?
This would make the behavior consistent for camel, camel-k,
camel-website and camel-kafka-connector.
What do you think?
Ch
omarsmak opened a new issue #32: Better support for value Schema in the
SourceTask
URL: https://github.com/apache/camel-kafka-connector/issues/32
Currently we build the `SourceRecord` with `Schema.BYTES_SCHEMA` schema.
However, this can be misleading, for example, you can have body message
valdar edited a comment on issue #31: run integration test insided gihub actions
URL:
https://github.com/apache/camel-kafka-connector/issues/31#issuecomment-563296282
See if it is possible to have integrations tests running as github actions,
not as heach PR but once in a while (nightly? w
valdar commented on issue #31: run integration test insided gihub actions
URL:
https://github.com/apache/camel-kafka-connector/issues/31#issuecomment-563296282
See if it is possible to have integrations tests running as github actions,
not as heach PR but once in a while (nightly?).
-
valdar opened a new issue #31: run integration test insided gihub actions
URL: https://github.com/apache/camel-kafka-connector/issues/31
This is an automated message from the Apache Git Service.
To respond to the message, ple
orpiske commented on issue #29: Support using an external Kafka for the tests
URL:
https://github.com/apache/camel-kafka-connector/pull/29#issuecomment-563294547
It's been acting strangely when running via Github actions, so I'll review
this.
-
oscerd merged pull request #28: Camel-AWS S3 example: Use a Transformation
instead of a converter
URL: https://github.com/apache/camel-kafka-connector/pull/28
This is an automated message from the Apache Git Service.
To resp
oscerd commented on issue #30: INFRA - Turn off mail noise to Camel @dev
mailing list
URL:
https://github.com/apache/camel-kafka-connector/issues/30#issuecomment-563284955
Opened.
This is an automated message from the Apache
oscerd commented on issue #30: INFRA - Turn off mail noise to Camel @dev
mailing list
URL:
https://github.com/apache/camel-kafka-connector/issues/30#issuecomment-563284879
https://issues.apache.org/jira/browse/INFRA-19548
Th
oscerd commented on issue #28: Camel-AWS S3 example: Use a Transformation
instead of a converter
URL:
https://github.com/apache/camel-kafka-connector/pull/28#issuecomment-563282671
So, I re-added the converter and as default we'll use that in the example,
but I committed the transformatio
davsclaus opened a new issue #30: INFRA - Turn off mail noise to Camel @dev
mailing list
URL: https://github.com/apache/camel-kafka-connector/issues/30
We need to turn off the noise from camel-kafka-connector on the @dev mailibg
list
like we did for the other projects
its spammed wit
orpiske edited a comment on issue #28: Camel-AWS S3 example: Use a
Transformation instead of a converter
URL:
https://github.com/apache/camel-kafka-connector/pull/28#issuecomment-563280222
@oscerd I think it's very useful to leave this. I've been playing with a
ElasticSearch test and @val
orpiske commented on issue #28: Camel-AWS S3 example: Use a Transformation
instead of a converter
URL:
https://github.com/apache/camel-kafka-connector/pull/28#issuecomment-563280222
@oscerd I think it's very useful to leave this. I've playing with a
ElasticSearch test and @valdar suggeste
oscerd commented on issue #30: INFRA - Turn off mail noise to Camel @dev
mailing list
URL:
https://github.com/apache/camel-kafka-connector/issues/30#issuecomment-563280525
Can you raise this to INFRA?
This is an automated me
omarsmak commented on issue #28: Camel-AWS S3 example: Use a Transformation
instead of a converter
URL:
https://github.com/apache/camel-kafka-connector/pull/28#issuecomment-563279305
Yeah makes sense, also I am working on this ticket
https://github.com/apache/camel-kafka-connector/issues/
oscerd commented on issue #28: Camel-AWS S3 example: Use a Transformation
instead of a converter
URL:
https://github.com/apache/camel-kafka-connector/pull/28#issuecomment-563278705
This was just for showing how can you create a transformation. What I can do
is leaving the converter and ad
omarsmak edited a comment on issue #28: Camel-AWS S3 example: Use a
Transformation instead of a converter
URL:
https://github.com/apache/camel-kafka-connector/pull/28#issuecomment-563275944
Converter is not more suitable here? Since we need to convert the data to
`byte[]` before sending i
omarsmak commented on issue #28: Camel-AWS S3 example: Use a Transformation
instead of a converter
URL:
https://github.com/apache/camel-kafka-connector/pull/28#issuecomment-563275944
Converter is not more suitable here? Since we need to convert the data to
`byte[]` before sending it to Ka
orpiske opened a new pull request #29: Support using an external Kafka for the
tests
URL: https://github.com/apache/camel-kafka-connector/pull/29
This decouples the kafka test service from the local container and allows
using an
external Kafka instance for testing. It also creates the b
oscerd opened a new pull request #28: Camel-AWS S3 example: Use a
Transformation instead of a converter
URL: https://github.com/apache/camel-kafka-connector/pull/28
This is an automated message from the Apache Git Service.
T
orpiske closed pull request #27: Fix camel file test
URL: https://github.com/apache/camel-kafka-connector/pull/27
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub an
orpiske opened a new pull request #27: Fix camel file test
URL: https://github.com/apache/camel-kafka-connector/pull/27
Prevent the file test from failing when the test file has been created but
no content has been written
Th
orpiske commented on issue #27: Fix camel file test
URL:
https://github.com/apache/camel-kafka-connector/pull/27#issuecomment-563263829
Please ignore.
This is an automated message from the Apache Git Service.
To respond to th
oscerd closed issue #18: Support Map and List as Headers
URL: https://github.com/apache/camel-kafka-connector/issues/18
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Git
oscerd merged pull request #26: Map list as headers
URL: https://github.com/apache/camel-kafka-connector/pull/26
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
oscerd opened a new pull request #26: Map list as headers
URL: https://github.com/apache/camel-kafka-connector/pull/26
Fixes #18
This is an automated message from the Apache Git Service.
To respond to the message, please log o
oscerd closed issue #19: Add a CI job for PR
URL: https://github.com/apache/camel-kafka-connector/issues/19
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
oscerd commented on issue #19: Add a CI job for PR
URL:
https://github.com/apache/camel-kafka-connector/issues/19#issuecomment-563168214
This should be done with Github actions
This is an automated message from the Apache Git
oscerd opened a new issue #25: Integrations tests fails if
confluentinc/cp-kafka:5.2.1 has not been pulled
URL: https://github.com/apache/camel-kafka-connector/issues/25
if one do a `mvn clean verify package` without having pulled
`confluentinc/cp-kafka:5.2.1` this is the result:
``
oscerd opened a new issue #24: Test code cleanups: embedded connect runtime
improvements
URL: https://github.com/apache/camel-kafka-connector/issues/24
I think we could investigate if we can cleanup the tests (re)using the work
from:
https://issues.apache.org/jira/browse/KAFKA-7503
oscerd opened a new issue #23: Add a Camel like DSL to translate between DSL
and properties
URL: https://github.com/apache/camel-kafka-connector/issues/23
If we have all the components together, I thought that we can add a DSL that
is very similar to Camel DSL, that is to make it easier fo
oscerd opened a new issue #21: Allow to bridge between Camel DataFormat and
Kafka Connect SMT
URL: https://github.com/apache/camel-kafka-connector/issues/21
It will be nice if we can somehow bridge between whetever we have for Camel
DataFormat and bridge it as Kafka SMT (Single Message Tra
oscerd opened a new issue #22: Allow to bridge between user's custom Camel
Processor and Kafka Connect SMT
URL: https://github.com/apache/camel-kafka-connector/issues/22
If the user has custom Camel Processor, IMHO it will be nice to bridge them
into Kafka Connect as an SMT wrapper, where
oscerd opened a new issue #20: Allow the user to set the key of the
SourceRecord explicitly
URL: https://github.com/apache/camel-kafka-connector/issues/20
Currently, when the messages being polled, via this method:
```
SourceRecord record = new SourceRecord(sourcePartition, sourceOffs
oscerd opened a new issue #19: Add a CI job for PR
URL: https://github.com/apache/camel-kafka-connector/issues/19
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub an
oscerd opened a new issue #18: Support Map and List as Headers
URL: https://github.com/apache/camel-kafka-connector/issues/18
This is an automated message from the Apache Git Service.
To respond to the message, please log on
oscerd opened a new issue #17: Find a better way of using sourcePartition and
sourceOffset
URL: https://github.com/apache/camel-kafka-connector/issues/17
https://github.com/jboss-fuse/camel-kafka-connector/blob/master/core/src/main/java/org/apache/camel/kafkaconnector/CamelSourceTask.java#
oscerd opened a new issue #16: support camel type converters
URL: https://github.com/apache/camel-kafka-connector/issues/16
Provide a way to support camel type converters and/or integrating them in
kafka connect `key.converter` and `value.converter`.
comment 1 @omarsmak: Hello @valda
oscerd opened a new issue #15: Find a way to manage dependencies
URL: https://github.com/apache/camel-kafka-connector/issues/15
In order to support camel components, the proper dependencies must be in the
classpath. Decide a way to do it, there are some alternatives:
- trivial option
oscerd merged pull request #14: Setting up POM as ASF standard
URL: https://github.com/apache/camel-kafka-connector/pull/14
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
oscerd opened a new pull request #14: Setting up POM as ASF standard
URL: https://github.com/apache/camel-kafka-connector/pull/14
This is an automated message from the Apache Git Service.
To respond to the message, please log
50 matches
Mail list logo
