[jira] [Commented] (CAMEL-18355) HTTP component overwrites basic authentication credentials with proxy authentication
[
https://issues.apache.org/jira/browse/CAMEL-18355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17585149#comment-17585149
]
Claus Ibsen commented on CAMEL-18355:
-
Can you backport this to 3.18.x branch
> HTTP component overwrites basic authentication credentials with proxy
> authentication
> -
>
> Key: CAMEL-18355
> URL: https://issues.apache.org/jira/browse/CAMEL-18355
> Project: Camel
> Issue Type: Bug
> Components: camel-http
>Affects Versions: 3.18.0
>Reporter: Oliver Holzmann
>Assignee: Karen Lease
>Priority: Major
> Fix For: 3.18.2, 3.19.0
>
>
> We use HTTP endpoints with basic authentication (params {{authUsername}},
> {{authPassword}}) via a proxy that requires proxy authentication (params
> {{proxyAuthUsername}}, {{proxyAuthPassword}}).
> But basic authentication fails. In debug logs we see that basic
> authentication header is using proxy credentials.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18428) Fhir component documentation describes the option password as the Username
[ https://issues.apache.org/jira/browse/CAMEL-18428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18428. - Resolution: Fixed > Fhir component documentation describes the option password as the Username > -- > > Key: CAMEL-18428 > URL: https://issues.apache.org/jira/browse/CAMEL-18428 > Project: Camel > Issue Type: Task > Components: camel-fhir >Affects Versions: 3.18.1 >Reporter: Pedro >Priority: Trivial > Labels: documentation > Fix For: 3.18.2, 3.19.0 > > > Fhir component documentation describes the option/query parameter "password" > as the "Username to use for basic authentication." instead of the "Password > to use for basic authentication." -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18406) camel-jbang - CLI to control routes such as suspend/resume/stats
[ https://issues.apache.org/jira/browse/CAMEL-18406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18406: Description: It would be good if we could - control routes such as start/stop/suspend/resume - context statistics *DONE* - route statistics so you can see their state, number of messages processed etc *DONE* - show health check status as well in the get commands *DONE* - show camel and runtime version - show memory usage was: It would be good if we could - control routes such as start/stop/suspend/resume - context statistics *DONE* - route statistics so you can see their state, number of messages processed etc *DONE* - show health check status as well in the get commands *DONE* > camel-jbang - CLI to control routes such as suspend/resume/stats > > > Key: CAMEL-18406 > URL: https://issues.apache.org/jira/browse/CAMEL-18406 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > It would be good if we could > - control routes such as start/stop/suspend/resume > - context statistics *DONE* > - route statistics so you can see their state, number of messages processed > etc *DONE* > - show health check status as well in the get commands *DONE* > - show camel and runtime version > - show memory usage -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18429) camel-jbang - Shutdown timeout 10 sec by default
Claus Ibsen created CAMEL-18429: --- Summary: camel-jbang - Shutdown timeout 10 sec by default Key: CAMEL-18429 URL: https://issues.apache.org/jira/browse/CAMEL-18429 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen Fix For: 3.19.0 camel run is intended for development purposes so lets make the shutdown quicker in case there is a stuck message or something takes a long time. The default of 45 sec is a bit too long to wait. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18382) Google-bigquery allow different value types from headers
[ https://issues.apache.org/jira/browse/CAMEL-18382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584775#comment-17584775 ] Jiri Ondrusek commented on CAMEL-18382: --- ok, thanks > Google-bigquery allow different value types from headers > - > > Key: CAMEL-18382 > URL: https://issues.apache.org/jira/browse/CAMEL-18382 > Project: Camel > Issue Type: Improvement > Components: camel-google-bigquery >Affects Versions: 3.18.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Minor > Fix For: 3.19.0 > > > One of the ways of execution of sql via `google-bigquery` component is to > pass values in header. Header values are passed into the sql request. > Unfortunately each object is converted to String in [this > line|https://github.com/apache/camel/blob/main/components/camel-google/camel-google-bigquery/src/main/java/org/apache/camel/component/google/bigquery/sql/GoogleBigQuerySQLProducer.java#L160.] > > It would be nice, if the component could keep several types based on the type > of the value (like numeric, boolean) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18382) Google-bigquery allow different value types from headers
[ https://issues.apache.org/jira/browse/CAMEL-18382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584774#comment-17584774 ] Claus Ibsen commented on CAMEL-18382: - No its fine to do this change and document the change in the 3.19 upgrade guide. > Google-bigquery allow different value types from headers > - > > Key: CAMEL-18382 > URL: https://issues.apache.org/jira/browse/CAMEL-18382 > Project: Camel > Issue Type: Improvement > Components: camel-google-bigquery >Affects Versions: 3.18.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Minor > Fix For: 3.19.0 > > > One of the ways of execution of sql via `google-bigquery` component is to > pass values in header. Header values are passed into the sql request. > Unfortunately each object is converted to String in [this > line|https://github.com/apache/camel/blob/main/components/camel-google/camel-google-bigquery/src/main/java/org/apache/camel/component/google/bigquery/sql/GoogleBigQuerySQLProducer.java#L160.] > > It would be nice, if the component could keep several types based on the type > of the value (like numeric, boolean) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18382) Google-bigquery allow different value types from headers
[ https://issues.apache.org/jira/browse/CAMEL-18382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17584772#comment-17584772 ] Jiri Ondrusek commented on CAMEL-18382: --- Hi [~davsclaus] , as I'm thinking about it, I see one problem. If I change the detection to use different types (not only String), it will break back-compatibility. Any user who is using current implementation would need to revisit scheme , potentially convert existing data. I can imagine a solution with a configuration property (something like _dynamicSqlTypeDetetection_ with default value false) which enables to switch on this new feature. What do you think? > Google-bigquery allow different value types from headers > - > > Key: CAMEL-18382 > URL: https://issues.apache.org/jira/browse/CAMEL-18382 > Project: Camel > Issue Type: Improvement > Components: camel-google-bigquery >Affects Versions: 3.18.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Minor > Fix For: 3.19.0 > > > One of the ways of execution of sql via `google-bigquery` component is to > pass values in header. Header values are passed into the sql request. > Unfortunately each object is converted to String in [this > line|https://github.com/apache/camel/blob/main/components/camel-google/camel-google-bigquery/src/main/java/org/apache/camel/component/google/bigquery/sql/GoogleBigQuerySQLProducer.java#L160.] > > It would be nice, if the component could keep several types based on the type > of the value (like numeric, boolean) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18423) camel-microprofile-config: Handle NoSuchElementException in CamelMicroProfilePropertiesSource. loadProperties(Predicate filter)
[ https://issues.apache.org/jira/browse/CAMEL-18423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Netherton resolved CAMEL-18423. - Resolution: Fixed > camel-microprofile-config: Handle NoSuchElementException in > CamelMicroProfilePropertiesSource. loadProperties(Predicate filter) > --- > > Key: CAMEL-18423 > URL: https://issues.apache.org/jira/browse/CAMEL-18423 > Project: Camel > Issue Type: Improvement > Components: camel-microprofile-config >Affects Versions: 3.18.0, 3.18.1 >Reporter: James Netherton >Assignee: James Netherton >Priority: Major > Fix For: 3.18.2, 3.19.0 > > > Extension of https://issues.apache.org/jira/browse/CAMEL-18233. > We need to handle NoSuchElementException in the > loadProperties(Predicate filter) variant of loadProperties in > CamelMicroProfilePropertiesSource. I thought it was not required because the > config does an optional lookup, but it seems even that can fail if config > values are not resolvable. -- This message was sent by Atlassian Jira (v8.20.10#820010)
