[jira] [Created] (CAMEL-19571) camel-parquet-avro: Add other compression codecs than gzip
Kengo Seki created CAMEL-19571: -- Summary: camel-parquet-avro: Add other compression codecs than gzip Key: CAMEL-19571 URL: https://issues.apache.org/jira/browse/CAMEL-19571 Project: Camel Issue Type: Improvement Reporter: Kengo Seki Assignee: Kengo Seki Currently, the Parquet-Avro data format only supports the gzip compression for marshalling, but other codecs such as snappy and zstd are also popular, so let's add them. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19563) Investigate usages of raw types
[ https://issues.apache.org/jira/browse/CAMEL-19563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739658#comment-17739658 ] Otavio Rodolfo Piske commented on CAMEL-19563: -- I noticed the ticket is missing a link to where someone can find a list of these. It's available on our sonarqube instance: https://sonarcloud.io/project/overview?id=apache_camel Obs: i am on PTO, so responding sporadically. > Investigate usages of raw types > --- > > Key: CAMEL-19563 > URL: https://issues.apache.org/jira/browse/CAMEL-19563 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Assignee: Adriano Marcondes Machado >Priority: Major > Labels: easy, help-wanted > > There are many source files using Raw types. I believe many of them could be > safely converted to use proper generics. This is a task to investigate and > fix as many as possible. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-19563) Investigate usages of raw types
[ https://issues.apache.org/jira/browse/CAMEL-19563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano Marcondes Machado reassigned CAMEL-19563: - Assignee: Adriano Marcondes Machado > Investigate usages of raw types > --- > > Key: CAMEL-19563 > URL: https://issues.apache.org/jira/browse/CAMEL-19563 > Project: Camel > Issue Type: Task >Reporter: Otavio Rodolfo Piske >Assignee: Adriano Marcondes Machado >Priority: Major > Labels: easy, help-wanted > > There are many source files using Raw types. I believe many of them could be > safely converted to use proper generics. This is a task to investigate and > fix as many as possible. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19570) Kafka max.poll.interval.ms declared in Long and not Integer
Alexandru Neaţă created CAMEL-19570: --- Summary: Kafka max.poll.interval.ms declared in Long and not Integer Key: CAMEL-19570 URL: https://issues.apache.org/jira/browse/CAMEL-19570 Project: Camel Issue Type: Bug Components: camel-kafka Affects Versions: 4.0-RC1 Reporter: Alexandru Neaţă Fix For: 4.0-RC2 The option for [max.poll.interval.ms|https://camel.apache.org/components/3.20.x/kafka-component.html#_component_option_maxPollIntervalMs] from camel is not the same type as the one from [kafka|https://docs.confluent.io/platform/current/installation/configuration/consumer-configs.html#max-poll-interval-ms]. With the latest version we see a nasty type incompatibility error. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19569) [observability|opentelemetry].CurrentSpanTest.testContextDoesNotLeak() fail on Github Actions
[
https://issues.apache.org/jira/browse/CAMEL-19569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17739611#comment-17739611
]
Peter Palaga commented on CAMEL-19569:
--
Both tests are passing for me locally and I am not sure what is different on GH
actions.
> [observability|opentelemetry].CurrentSpanTest.testContextDoesNotLeak() fail
> on Github Actions
> -
>
> Key: CAMEL-19569
> URL: https://issues.apache.org/jira/browse/CAMEL-19569
> Project: Camel
> Issue Type: Bug
>Reporter: Peter Palaga
>Priority: Major
>
> {{org.apache.camel.opentelemetry.CurrentSpanTest.testContextDoesNotLeak()}}
> and {{org.apache.camel.observation.CurrentSpanTest.testContextDoesNotLeak}}
> fail on GutHub Actions:
> {code}
> [ERROR] org.apache.camel.opentelemetry.CurrentSpanTest.testContextDoesNotLeak
> -- Time elapsed: 1.115 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: expected: <30> but was: <1>
> at
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at
> org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
> at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:528)
> at
> org.apache.camel.opentelemetry.CamelOpenTelemetryTestSupport.verifyTraceSpanNumbers(CamelOpenTelemetryTestSupport.java:156)
> at
> org.apache.camel.opentelemetry.CurrentSpanTest.testContextDoesNotLeak(CurrentSpanTest.java:196)
> {code}
> {code}
> [ERROR] org.apache.camel.observation.CurrentSpanTest.testContextDoesNotLeak
> -- Time elapsed: 1.182 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: expected: <30> but was: <1>
> at
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
> at
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
> at
> org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
> at
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
> at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:528)
> at
> org.apache.camel.observation.CamelMicrometerObservationTestSupport.verifyTraceSpanNumbers(CamelMicrometerObservationTestSupport.java:205)
> at
> org.apache.camel.observation.CurrentSpanTest.testContextDoesNotLeak(CurrentSpanTest.java:202)
> {code}
> Seen in this PR: https://github.com/apache/camel/pull/10539
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19569) [observability|opentelemetry].CurrentSpanTest.testContextDoesNotLeak() fail on Github Actions
Peter Palaga created CAMEL-19569:
Summary:
[observability|opentelemetry].CurrentSpanTest.testContextDoesNotLeak() fail on
Github Actions
Key: CAMEL-19569
URL: https://issues.apache.org/jira/browse/CAMEL-19569
Project: Camel
Issue Type: Bug
Reporter: Peter Palaga
{{org.apache.camel.opentelemetry.CurrentSpanTest.testContextDoesNotLeak()}} and
{{org.apache.camel.observation.CurrentSpanTest.testContextDoesNotLeak}} fail on
GutHub Actions:
{code}
[ERROR] org.apache.camel.opentelemetry.CurrentSpanTest.testContextDoesNotLeak
-- Time elapsed: 1.115 s <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <30> but was: <1>
at
org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at
org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at
org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
at
org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
at
org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:528)
at
org.apache.camel.opentelemetry.CamelOpenTelemetryTestSupport.verifyTraceSpanNumbers(CamelOpenTelemetryTestSupport.java:156)
at
org.apache.camel.opentelemetry.CurrentSpanTest.testContextDoesNotLeak(CurrentSpanTest.java:196)
{code}
{code}
[ERROR] org.apache.camel.observation.CurrentSpanTest.testContextDoesNotLeak --
Time elapsed: 1.182 s <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <30> but was: <1>
at
org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at
org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at
org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
at
org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:150)
at
org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:145)
at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:528)
at
org.apache.camel.observation.CamelMicrometerObservationTestSupport.verifyTraceSpanNumbers(CamelMicrometerObservationTestSupport.java:205)
at
org.apache.camel.observation.CurrentSpanTest.testContextDoesNotLeak(CurrentSpanTest.java:202)
{code}
Seen in this PR: https://github.com/apache/camel/pull/10539
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19568) HTTP/2 Multipart boundary
Ruben Romero Montes created CAMEL-19568:
---
Summary: HTTP/2 Multipart boundary
Key: CAMEL-19568
URL: https://issues.apache.org/jira/browse/CAMEL-19568
Project: Camel
Issue Type: Bug
Components: camel-mail
Affects Versions: 4.0-M3
Reporter: Ruben Romero Montes
When using multipart/mixed responses a basic java.net.HttpClient fails to
process the response because it defaults to HTTP/2.
{code:java}
Exception in thread "main" java.io.IOException: protocol error:
java.io.IOException: Bad header value 'multipart/mixed;
boundary="=_Part_0_1089205692.1688375583933"'
at
java.net.http/jdk.internal.net.http.HttpClientImpl.send(HttpClientImpl.java:909)
at
java.net.http/jdk.internal.net.http.HttpClientFacade.send(HttpClientFacade.java:133)
at com.example.App.main(App.java:22)
Caused by: java.io.IOException: protocol error: java.io.IOException: Bad header
value 'multipart/mixed;
boundary="=_Part_0_1089205692.1688375583933"'
at
java.net.http/jdk.internal.net.http.Http2Connection.protocolError(Http2Connection.java:1089)
at
java.net.http/jdk.internal.net.http.Http2Connection.processFrame(Http2Connection.java:868)
at
java.net.http/jdk.internal.net.http.frame.FramesDecoder.decode(FramesDecoder.java:155)
at
java.net.http/jdk.internal.net.http.Http2Connection$FramesController.processReceivedData(Http2Connection.java:265)
at
java.net.http/jdk.internal.net.http.Http2Connection.asyncReceive(Http2Connection.java:714)
at
java.net.http/jdk.internal.net.http.Http2Connection$Http2TubeSubscriber.processQueue(Http2Connection.java:1440)
at
java.net.http/jdk.internal.net.http.common.SequentialScheduler$LockingRestartableTask.run(SequentialScheduler.java:205)
at
java.net.http/jdk.internal.net.http.common.SequentialScheduler$CompleteRestartableTask.run(SequentialScheduler.java:149)
at
java.net.http/jdk.internal.net.http.common.SequentialScheduler$SchedulableTask.run(SequentialScheduler.java:230)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1623)
{code}
When using HTTP/1.1 this is not an issue.
It seems the main difference is the format of the Content-Type header.
{code}
Content-Type: multipart/mixed;
boundary="=_Part_0_644068325.1688368219924"
{code}
When the removing the extra CRLF and tabs from the header, the client processes
the response successfully.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-19567) Create a Camel-Opensearch Starter
[ https://issues.apache.org/jira/browse/CAMEL-19567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-19567. -- Resolution: Fixed > Create a Camel-Opensearch Starter > - > > Key: CAMEL-19567 > URL: https://issues.apache.org/jira/browse/CAMEL-19567 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19567) Create a Camel-Opensearch Starter
Andrea Cosentino created CAMEL-19567: Summary: Create a Camel-Opensearch Starter Key: CAMEL-19567 URL: https://issues.apache.org/jira/browse/CAMEL-19567 Project: Camel Issue Type: New Feature Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18837) Component for Opensearch
[
https://issues.apache.org/jira/browse/CAMEL-18837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-18837:
-
Fix Version/s: 4.0.0
(was: 3.x)
> Component for Opensearch
>
>
> Key: CAMEL-18837
> URL: https://issues.apache.org/jira/browse/CAMEL-18837
> Project: Camel
> Issue Type: New Feature
>Reporter: Federico Mariani
>Assignee: Adriano Marcondes Machado
>Priority: Major
> Labels: help-wanted
> Fix For: 4.0.0
>
>
> {code:java}
> OpenSearch is a community-driven, open source search and analytics suite
> derived from Apache 2.0 licensed Elasticsearch 7.10.2 & Kibana 7.10.2. It
> consists of a search engine daemon, OpenSearch, and a visualization and user
> interface, OpenSearch Dashboards.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18837) Component for Opensearch
[
https://issues.apache.org/jira/browse/CAMEL-18837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-18837.
--
Resolution: Fixed
> Component for Opensearch
>
>
> Key: CAMEL-18837
> URL: https://issues.apache.org/jira/browse/CAMEL-18837
> Project: Camel
> Issue Type: New Feature
>Reporter: Federico Mariani
>Assignee: Adriano Marcondes Machado
>Priority: Major
> Labels: help-wanted
> Fix For: 4.0.0
>
>
> {code:java}
> OpenSearch is a community-driven, open source search and analytics suite
> derived from Apache 2.0 licensed Elasticsearch 7.10.2 & Kibana 7.10.2. It
> consists of a search engine daemon, OpenSearch, and a visualization and user
> interface, OpenSearch Dashboards.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19566) Camel micrometer documentation shows wrong parameter value name for summary
Jiri Ondrusek created CAMEL-19566: - Summary: Camel micrometer documentation shows wrong parameter value name for summary Key: CAMEL-19566 URL: https://issues.apache.org/jira/browse/CAMEL-19566 Project: Camel Issue Type: Bug Components: camel-micrometer Affects Versions: 4.0-RC1 Reporter: Jiri Ondrusek Assignee: Jiri Ondrusek As you can see [here|https://github.com/apache/camel/blob/main/components/camel-micrometer/src/main/java/org/apache/camel/component/micrometer/MicrometerUtils.java#L40] allowed values for metrics type are 'counter', 'summary' and 'timer'. Values in the [doc|https://camel.apache.org/components/3.20.x/micrometer-component.html#_endpoint_path_option_metricsType] are * counter * distribution_summary * timer Distribution_summary should be changed to summary. -- This message was sent by Atlassian Jira (v8.20.10#820010)
