[jira] [Closed] (CAMEL-8171) Split the XSD element name attributes
[ https://issues.apache.org/jira/browse/CAMEL-8171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen closed CAMEL-8171. -- > Split the XSD element name attributes > - > > Key: CAMEL-8171 > URL: https://issues.apache.org/jira/browse/CAMEL-8171 > Project: Camel > Issue Type: New Feature >Reporter: srinivas > > Hi, > I am trying to split the XSD element which are colon separated like > and I want > to split and save the attributes for later use. I dont want to hard code the > attributes names -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8171) Split the XSD element name attributes
[ https://issues.apache.org/jira/browse/CAMEL-8171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8171. Resolution: Invalid Use mailing list to ask these kind of questions. > Split the XSD element name attributes > - > > Key: CAMEL-8171 > URL: https://issues.apache.org/jira/browse/CAMEL-8171 > Project: Camel > Issue Type: New Feature >Reporter: srinivas > > Hi, > I am trying to split the XSD element which are colon separated like > and I want > to split and save the attributes for later use. I dont want to hard code the > attributes names -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8171) Split the XSD element name attributes
[ https://issues.apache.org/jira/browse/CAMEL-8171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256768#comment-14256768 ] srinivas commented on CAMEL-8171: - Hi Claus, I have pasted my question there also but no one is responding. > Split the XSD element name attributes > - > > Key: CAMEL-8171 > URL: https://issues.apache.org/jira/browse/CAMEL-8171 > Project: Camel > Issue Type: New Feature >Reporter: srinivas > > Hi, > I am trying to split the XSD element which are colon separated like > and I want > to split and save the attributes for later use. I dont want to hard code the > attributes names -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8172) Enable multiple consumers for kafka endpoint
Ivan Vasyliev created CAMEL-8172:
Summary: Enable multiple consumers for kafka endpoint
Key: CAMEL-8172
URL: https://issues.apache.org/jira/browse/CAMEL-8172
Project: Camel
Issue Type: Improvement
Components: camel-kafka
Reporter: Ivan Vasyliev
Fix For: 2.15.0
Attachments: Enable_multiple_consumers.patch
MultipleConsumersSupport.java
{quote}
* A rare few endpoints do in fact support multiple consumers and thus the
purpose of this interface.
* For example JMS endpoints which have topics that can be consumed by multiple
consumers.
{quote}
Kafka has nothing else but topics and I'm wondering why this was not
implemented right away.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8172) Enable multiple consumers for kafka endpoint
[
https://issues.apache.org/jira/browse/CAMEL-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Vasyliev updated CAMEL-8172:
-
Attachment: Enable_multiple_consumers.patch
> Enable multiple consumers for kafka endpoint
>
>
> Key: CAMEL-8172
> URL: https://issues.apache.org/jira/browse/CAMEL-8172
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
>Reporter: Ivan Vasyliev
> Fix For: 2.15.0
>
> Attachments: Enable_multiple_consumers.patch
>
>
> MultipleConsumersSupport.java
> {quote}
> * A rare few endpoints do in fact support multiple consumers and thus the
> purpose of this interface.
> * For example JMS endpoints which have topics that can be consumed by
> multiple consumers.
> {quote}
> Kafka has nothing else but topics and I'm wondering why this was not
> implemented right away.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8172) Enable multiple consumers for kafka endpoint
[
https://issues.apache.org/jira/browse/CAMEL-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Vasyliev updated CAMEL-8172:
-
Estimated Complexity: Needs James Gosling (was: Unknown)
> Enable multiple consumers for kafka endpoint
>
>
> Key: CAMEL-8172
> URL: https://issues.apache.org/jira/browse/CAMEL-8172
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
>Reporter: Ivan Vasyliev
> Fix For: 2.15.0
>
> Attachments: Enable_multiple_consumers.patch
>
>
> MultipleConsumersSupport.java
> {quote}
> * A rare few endpoints do in fact support multiple consumers and thus the
> purpose of this interface.
> * For example JMS endpoints which have topics that can be consumed by
> multiple consumers.
> {quote}
> Kafka has nothing, but topics and I'm wondering why this was not implemented
> right away.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8172) Enable multiple consumers for kafka endpoint
[
https://issues.apache.org/jira/browse/CAMEL-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Vasyliev updated CAMEL-8172:
-
Description:
MultipleConsumersSupport.java
{quote}
* A rare few endpoints do in fact support multiple consumers and thus the
purpose of this interface.
* For example JMS endpoints which have topics that can be consumed by multiple
consumers.
{quote}
Kafka has nothing, but topics and I'm wondering why this was not implemented
right away.
was:
MultipleConsumersSupport.java
{quote}
* A rare few endpoints do in fact support multiple consumers and thus the
purpose of this interface.
* For example JMS endpoints which have topics that can be consumed by multiple
consumers.
{quote}
Kafka has nothing else but topics and I'm wondering why this was not
implemented right away.
> Enable multiple consumers for kafka endpoint
>
>
> Key: CAMEL-8172
> URL: https://issues.apache.org/jira/browse/CAMEL-8172
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
>Reporter: Ivan Vasyliev
> Fix For: 2.15.0
>
> Attachments: Enable_multiple_consumers.patch
>
>
> MultipleConsumersSupport.java
> {quote}
> * A rare few endpoints do in fact support multiple consumers and thus the
> purpose of this interface.
> * For example JMS endpoints which have topics that can be consumed by
> multiple consumers.
> {quote}
> Kafka has nothing, but topics and I'm wondering why this was not implemented
> right away.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CAMEL-8172) Enable multiple consumers for kafka endpoint
[
https://issues.apache.org/jira/browse/CAMEL-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Vasyliev updated CAMEL-8172:
-
Estimated Complexity: (was: Needs James Gosling)
> Enable multiple consumers for kafka endpoint
>
>
> Key: CAMEL-8172
> URL: https://issues.apache.org/jira/browse/CAMEL-8172
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
>Reporter: Ivan Vasyliev
> Fix For: 2.15.0
>
> Attachments: Enable_multiple_consumers.patch
>
>
> MultipleConsumersSupport.java
> {quote}
> * A rare few endpoints do in fact support multiple consumers and thus the
> purpose of this interface.
> * For example JMS endpoints which have topics that can be consumed by
> multiple consumers.
> {quote}
> Kafka has nothing, but topics and I'm wondering why this was not implemented
> right away.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (CAMEL-8149) Support application-generated document identifiers in bulk index requests
[ https://issues.apache.org/jira/browse/CAMEL-8149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-8149: -- Assignee: Claus Ibsen > Support application-generated document identifiers in bulk index requests > - > > Key: CAMEL-8149 > URL: https://issues.apache.org/jira/browse/CAMEL-8149 > Project: Camel > Issue Type: Improvement > Components: camel-elasticsearch >Affects Versions: 2.14.0 >Reporter: Derek Abdine >Assignee: Claus Ibsen > Fix For: 2.15.0 > > Attachments: camel-8149.patch > > > Elasticsearch (via the elasticsearch-java transport client) provides two > categories of APIs to write and read data: Individual requests (index, get, > delete) and bulk requests. > When performing bulk updates one creates individual index requests and adds > them to the bulk request. When creating an index request one can set the > source document, id, etc. > The current design of the camel-elasticsearch component controls the > transformation and assembly of an input body (json string, byte[], > xcontentfactory, map) to an index request. Thus, it is impossible to set the > id on the index request that goes into a bulk action. The end result is that > the id is set by the default behavior of the underlying elasticsearch-java > client which generates a random identifier. This is problematic in > situations where control is needed over the id, e.g. for de-duplication > purposes. > My proposal is to improve the design of the producer to allow for > elasticsearch-java ActionRequest sub-classes in the message body so that > upstream message processors can control the creation of those requests. > I've attached a patch and sent a pull request on github. > Thank you! > Derek Abdine -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8149) Support application-generated document identifiers in bulk index requests
[ https://issues.apache.org/jira/browse/CAMEL-8149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8149. Resolution: Fixed Thanks for the PR. > Support application-generated document identifiers in bulk index requests > - > > Key: CAMEL-8149 > URL: https://issues.apache.org/jira/browse/CAMEL-8149 > Project: Camel > Issue Type: Improvement > Components: camel-elasticsearch >Affects Versions: 2.14.0 >Reporter: Derek Abdine >Assignee: Claus Ibsen > Fix For: 2.15.0 > > Attachments: camel-8149.patch > > > Elasticsearch (via the elasticsearch-java transport client) provides two > categories of APIs to write and read data: Individual requests (index, get, > delete) and bulk requests. > When performing bulk updates one creates individual index requests and adds > them to the bulk request. When creating an index request one can set the > source document, id, etc. > The current design of the camel-elasticsearch component controls the > transformation and assembly of an input body (json string, byte[], > xcontentfactory, map) to an index request. Thus, it is impossible to set the > id on the index request that goes into a bulk action. The end result is that > the id is set by the default behavior of the underlying elasticsearch-java > client which generates a random identifier. This is problematic in > situations where control is needed over the id, e.g. for de-duplication > purposes. > My proposal is to improve the design of the producer to allow for > elasticsearch-java ActionRequest sub-classes in the message body so that > upstream message processors can control the creation of those requests. > I've attached a patch and sent a pull request on github. > Thank you! > Derek Abdine -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8170) add support to camel-solr for List objects in the message body
[ https://issues.apache.org/jira/browse/CAMEL-8170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8170: --- Affects Version/s: (was: 2.15.0) 2.14.0 > add support to camel-solr for List objects in the message > body > - > > Key: CAMEL-8170 > URL: https://issues.apache.org/jira/browse/CAMEL-8170 > Project: Camel > Issue Type: New Feature > Components: camel-solr >Affects Versions: 2.14.0 >Reporter: Kranti Parisa >Priority: Minor > Fix For: 2.15.0 > > > upstream could prepare List of SolrInputDocument and we should support > passing the list in via the message body. > Here is the Github Pull request > https://github.com/apache/camel/pull/359 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8170) add support to camel-solr for List objects in the message body
[ https://issues.apache.org/jira/browse/CAMEL-8170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-8170: --- Fix Version/s: 2.15.0 > add support to camel-solr for List objects in the message > body > - > > Key: CAMEL-8170 > URL: https://issues.apache.org/jira/browse/CAMEL-8170 > Project: Camel > Issue Type: New Feature > Components: camel-solr >Affects Versions: 2.14.0 >Reporter: Kranti Parisa >Priority: Minor > Fix For: 2.15.0 > > > upstream could prepare List of SolrInputDocument and we should support > passing the list in via the message body. > Here is the Github Pull request > https://github.com/apache/camel/pull/359 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-8170) add support to camel-solr for List objects in the message body
[ https://issues.apache.org/jira/browse/CAMEL-8170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-8170: -- Assignee: Claus Ibsen > add support to camel-solr for List objects in the message > body > - > > Key: CAMEL-8170 > URL: https://issues.apache.org/jira/browse/CAMEL-8170 > Project: Camel > Issue Type: New Feature > Components: camel-solr >Affects Versions: 2.14.0 >Reporter: Kranti Parisa >Assignee: Claus Ibsen >Priority: Minor > Fix For: 2.15.0 > > > upstream could prepare List of SolrInputDocument and we should support > passing the list in via the message body. > Here is the Github Pull request > https://github.com/apache/camel/pull/359 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8170) add support to camel-solr for List objects in the message body
[ https://issues.apache.org/jira/browse/CAMEL-8170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8170. Resolution: Fixed > add support to camel-solr for List objects in the message > body > - > > Key: CAMEL-8170 > URL: https://issues.apache.org/jira/browse/CAMEL-8170 > Project: Camel > Issue Type: New Feature > Components: camel-solr >Affects Versions: 2.14.0 >Reporter: Kranti Parisa >Assignee: Claus Ibsen >Priority: Minor > Fix For: 2.15.0 > > > upstream could prepare List of SolrInputDocument and we should support > passing the list in via the message body. > Here is the Github Pull request > https://github.com/apache/camel/pull/359 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-2939) Cassandra component for Camel http://github.com/ticktock/camel-cassandra
[ https://issues.apache.org/jira/browse/CAMEL-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256829#comment-14256829 ] Claus Ibsen commented on CAMEL-2939: Thanks Gerald Going to merge your PR. Do you mind help with documentation? And are there still things to do? The CQL can maybe be injected using property placeholders, For example as we do in the sql example http://camel.apache.org/sql-example.html and also you can maybe refer to a bean to lookup in the registry that provides the query. > Cassandra component for Camel http://github.com/ticktock/camel-cassandra > > > Key: CAMEL-2939 > URL: https://issues.apache.org/jira/browse/CAMEL-2939 > Project: Camel > Issue Type: New Feature >Affects Versions: 2.3.0 >Reporter: Scott Clasen > Fix For: Future > > Attachments: camel-cassandra.tar.gz > > > Take a look at http://github.com/ticktock/camel-cassandra, its a Cassandra > component for Camel. > Please pull into the camel codebase if its up to snuff, or let me know what I > need to do to get it there -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-2939) Cassandra component for Camel http://github.com/ticktock/camel-cassandra
[ https://issues.apache.org/jira/browse/CAMEL-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-2939: --- Fix Version/s: (was: Future) 2.15.0 > Cassandra component for Camel http://github.com/ticktock/camel-cassandra > > > Key: CAMEL-2939 > URL: https://issues.apache.org/jira/browse/CAMEL-2939 > Project: Camel > Issue Type: New Feature >Affects Versions: 2.3.0 >Reporter: Scott Clasen > Fix For: 2.15.0 > > Attachments: camel-cassandra.tar.gz > > > Take a look at http://github.com/ticktock/camel-cassandra, its a Cassandra > component for Camel. > Please pull into the camel codebase if its up to snuff, or let me know what I > need to do to get it there -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-2939) Cassandra component for Camel http://github.com/ticktock/camel-cassandra
[ https://issues.apache.org/jira/browse/CAMEL-2939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-2939: -- Assignee: Claus Ibsen > Cassandra component for Camel http://github.com/ticktock/camel-cassandra > > > Key: CAMEL-2939 > URL: https://issues.apache.org/jira/browse/CAMEL-2939 > Project: Camel > Issue Type: New Feature >Affects Versions: 2.3.0 >Reporter: Scott Clasen >Assignee: Claus Ibsen > Fix For: 2.15.0 > > Attachments: camel-cassandra.tar.gz > > > Take a look at http://github.com/ticktock/camel-cassandra, its a Cassandra > component for Camel. > Please pull into the camel codebase if its up to snuff, or let me know what I > need to do to get it there -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-7766) Exception in split does not trigger onException in main route
[ https://issues.apache.org/jira/browse/CAMEL-7766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-7766. Resolution: Not a Problem Fix Version/s: 2.15.0 > Exception in split does not trigger onException in main route > - > > Key: CAMEL-7766 > URL: https://issues.apache.org/jira/browse/CAMEL-7766 > Project: Camel > Issue Type: Bug > Components: camel-core >Affects Versions: 2.13.2 > Environment: JDK7 / W7 >Reporter: Benjamin BONNET >Assignee: Claus Ibsen > Fix For: 2.15.0 > > > Exception thrown in a sequential split does not trigger onException applying > to main route. > That bug may be a regression linked to commit#78c7350 (CAMEL-5681 fix) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-8161) camel-swagger - Use JMX to lookup Camel's so we support everyone
[ https://issues.apache.org/jira/browse/CAMEL-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-8161: -- Assignee: Claus Ibsen > camel-swagger - Use JMX to lookup Camel's so we support everyone > > > Key: CAMEL-8161 > URL: https://issues.apache.org/jira/browse/CAMEL-8161 > Project: Camel > Issue Type: Improvement > Components: camel-swagger >Reporter: Claus Ibsen >Assignee: Claus Ibsen > Fix For: 2.15.0 > > > Currently there is only spring support out of the box > https://github.com/apache/camel/blob/master/components/camel-swagger/src/main/scala/org/apache/camel/component/swagger/spring/SpringRestSwaggerApiDeclarationServlet.scala > Though we could likely use jmx to lookup the Camel's and then grab the rest > definition as xml, and marshal back to objects, which the scala swagger > reader needs. Then it would work in any kind of environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (CAMEL-8172) Enable multiple consumers for kafka endpoint
[
https://issues.apache.org/jira/browse/CAMEL-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang reassigned CAMEL-8172:
---
Assignee: Willem Jiang
> Enable multiple consumers for kafka endpoint
>
>
> Key: CAMEL-8172
> URL: https://issues.apache.org/jira/browse/CAMEL-8172
> Project: Camel
> Issue Type: Improvement
> Components: camel-kafka
>Reporter: Ivan Vasyliev
>Assignee: Willem Jiang
> Fix For: 2.15.0
>
> Attachments: Enable_multiple_consumers.patch
>
>
> MultipleConsumersSupport.java
> {quote}
> * A rare few endpoints do in fact support multiple consumers and thus the
> purpose of this interface.
> * For example JMS endpoints which have topics that can be consumed by
> multiple consumers.
> {quote}
> Kafka has nothing, but topics and I'm wondering why this was not implemented
> right away.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CAMEL-8173) Support to set InflightRepository from Camel XML DSL
Willem Jiang created CAMEL-8173: --- Summary: Support to set InflightRepository from Camel XML DSL Key: CAMEL-8173 URL: https://issues.apache.org/jira/browse/CAMEL-8173 Project: Camel Issue Type: Improvement Components: camel-blueprint, camel-spring Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.15.0 CamelContext has the method to setup the InflightRepository, but there is not XML DSL supports it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8173) Support to set InflightRepository from Camel XML DSL
[ https://issues.apache.org/jira/browse/CAMEL-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256987#comment-14256987 ] Claus Ibsen commented on CAMEL-8173: Works for blueprint also > Support to set InflightRepository from Camel XML DSL > > > Key: CAMEL-8173 > URL: https://issues.apache.org/jira/browse/CAMEL-8173 > Project: Camel > Issue Type: Improvement > Components: camel-blueprint, camel-spring >Reporter: Willem Jiang >Assignee: Willem Jiang > Fix For: 2.15.0 > > > CamelContext has the method to setup the InflightRepository, but there is not > XML DSL supports it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8173) Support to set InflightRepository from Camel XML DSL
[ https://issues.apache.org/jira/browse/CAMEL-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256986#comment-14256986 ] Claus Ibsen commented on CAMEL-8173: Willem see http://camel.apache.org/advanced-configuration-of-camelcontext-using-spring.html You just define a and camel uses that instead. > Support to set InflightRepository from Camel XML DSL > > > Key: CAMEL-8173 > URL: https://issues.apache.org/jira/browse/CAMEL-8173 > Project: Camel > Issue Type: Improvement > Components: camel-blueprint, camel-spring >Reporter: Willem Jiang >Assignee: Willem Jiang > Fix For: 2.15.0 > > > CamelContext has the method to setup the InflightRepository, but there is not > XML DSL supports it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8174) Added TimeoutInflightRepository to track the long processing exchange
Willem Jiang created CAMEL-8174: --- Summary: Added TimeoutInflightRepository to track the long processing exchange Key: CAMEL-8174 URL: https://issues.apache.org/jira/browse/CAMEL-8174 Project: Camel Issue Type: Improvement Reporter: Willem Jiang Assignee: Willem Jiang Fix For: 2.15.0 It could be helpful is we can track the long processing exchange, user can log or send alarm when getting these exchange by extends the TimeoutInflightRepository. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CAMEL-8174) Added TimeoutInflightRepository to track the long processing exchange
[ https://issues.apache.org/jira/browse/CAMEL-8174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-8174: Description: It could be helpful is we can track the long processing exchange, user can log or send alarm when getting these exchange by extending the TimeoutInflightRepository. (was: It could be helpful is we can track the long processing exchange, user can log or send alarm when getting these exchange by extends the TimeoutInflightRepository.) > Added TimeoutInflightRepository to track the long processing exchange > - > > Key: CAMEL-8174 > URL: https://issues.apache.org/jira/browse/CAMEL-8174 > Project: Camel > Issue Type: Improvement >Reporter: Willem Jiang >Assignee: Willem Jiang > Fix For: 2.15.0 > > > It could be helpful is we can track the long processing exchange, user can > log or send alarm when getting these exchange by extending the > TimeoutInflightRepository. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8161) camel-swagger - Use JMX to lookup Camel's so we support everyone
[ https://issues.apache.org/jira/browse/CAMEL-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-8161. Resolution: Fixed > camel-swagger - Use JMX to lookup Camel's so we support everyone > > > Key: CAMEL-8161 > URL: https://issues.apache.org/jira/browse/CAMEL-8161 > Project: Camel > Issue Type: Improvement > Components: camel-swagger >Reporter: Claus Ibsen >Assignee: Claus Ibsen > Fix For: 2.15.0 > > > Currently there is only spring support out of the box > https://github.com/apache/camel/blob/master/components/camel-swagger/src/main/scala/org/apache/camel/component/swagger/spring/SpringRestSwaggerApiDeclarationServlet.scala > Though we could likely use jmx to lookup the Camel's and then grab the rest > definition as xml, and marshal back to objects, which the scala swagger > reader needs. Then it would work in any kind of environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8174) Added TimeoutInflightRepository to track the long processing exchange
[ https://issues.apache.org/jira/browse/CAMEL-8174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14256997#comment-14256997 ] Claus Ibsen commented on CAMEL-8174: Could you hold on this, as there is some thoughts for future Camel release with monitoring of long running exchanges, and as well being able to gain insight to current running exchanges, and do a per exchange dump of their message history, so you can view per exchange where it currently is, and its message tracing. So please wait till after new year and lets discuss here or on the mailing list. > Added TimeoutInflightRepository to track the long processing exchange > - > > Key: CAMEL-8174 > URL: https://issues.apache.org/jira/browse/CAMEL-8174 > Project: Camel > Issue Type: Improvement >Reporter: Willem Jiang >Assignee: Willem Jiang > Fix For: 2.15.0 > > > It could be helpful is we can track the long processing exchange, user can > log or send alarm when getting these exchange by extending the > TimeoutInflightRepository. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CAMEL-8175) camel-swagger - Add support for multiple CamelContexts
Claus Ibsen created CAMEL-8175: -- Summary: camel-swagger - Add support for multiple CamelContexts Key: CAMEL-8175 URL: https://issues.apache.org/jira/browse/CAMEL-8175 Project: Camel Issue Type: Improvement Components: camel-swagger Reporter: Claus Ibsen Fix For: 2.15.0 Related to CAMEL-8161 Instead of having to co-locate camel-swagger in the same deployment as your Camel, then we should add support for supporting multiple camel contexts, so the api-docs can support that. Then people can inspect the rest services per camel, using its id, etc /foo/api-docs /bar/api-docs Where foo and bar is the camelId -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-4427) Fix URI definition for camel-irc to provide valid URIs
[ https://issues.apache.org/jira/browse/CAMEL-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257051#comment-14257051 ] ASF GitHub Bot commented on CAMEL-4427: --- Github user lithium closed the pull request at: https://github.com/apache/camel/pull/358 > Fix URI definition for camel-irc to provide valid URIs > -- > > Key: CAMEL-4427 > URL: https://issues.apache.org/jira/browse/CAMEL-4427 > Project: Camel > Issue Type: Sub-task > Components: camel-irc >Affects Versions: 2.8.0 >Reporter: Hadrian Zbarcea >Assignee: Hadrian Zbarcea > > Hash signs '#' are not quite allowed in URIs. While they do mark a URI > fragment, a URI cannot have more than one fragment (and hence '#' signs) and > URI parameters must appear before the fragment. > The [IRC spec|http://www.irchelp.org/irchelp/rfc/rfc.html] mandates channel > names to start with either a '&' or a '#', both not allowed in a URI (i.e. > need to be escaped). I am proposing the following changes that will make > camel-irc URIs valid. Current URIs will still be supported but deprecated > until 3.0. > The changes/clarifications are: > 1. Current syntax is supported, yet deprecated > 2. Current syntax with '#' symbols properly encoded is supported (i.e. a > channel name will be "%23camel" instead of "camel" > 3. Make the '#' symbol optional (i.e. "channels=camel,activemq" is equivalent > with "channels=%23camel,%23activemq"). That makes URIs simpler, if the '#' is > missing camel-irc will prepend exacly one '#'. > 4. For channels that start with '&' or double "##", like [freenode > non-primary channels] encoding is mandatory. > 5. The userInfo part always represents the username, which could be different > than the nick. The documentation is not clear on that. By default the nick is > the same as the username. > 6. Username is mandatory. > 7. Deprecate the "username" parameter, it must be supplied in the userInfo > part of the URI. > 8. IRC URIs are URLs not URNs; i.e. the scheme must be followed by "://", not > just ":". > I will update the code to preProcess() camel-irc URIs to follow the rules > above and update the documentation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8123) Mina2 SSL initiates handshake backwards
[
https://issues.apache.org/jira/browse/CAMEL-8123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257190#comment-14257190
]
ASF GitHub Bot commented on CAMEL-8123:
---
Github user peterberkman closed the pull request at:
https://github.com/apache/camel/pull/349
> Mina2 SSL initiates handshake backwards
> ---
>
> Key: CAMEL-8123
> URL: https://issues.apache.org/jira/browse/CAMEL-8123
> Project: Camel
> Issue Type: Bug
> Components: camel-mina2
>Affects Versions: 2.13.3, 2.14.0
>Reporter: Justin Cozzens
>Assignee: Willem Jiang
> Fix For: 2.13.4, 2.14.1, 2.15.0
>
>
> The Mina2Consumer and Mina2Producer are configured backwards for SSL
> handshake initiation. The consumer is trying to initiate the handshake rather
> than the producer. You can see this by setting up a SSL enabled consuming
> route and telnet to the port, you will immediately get some data sent from
> the server to the client rather than the server waiting on the client to
> initiate the handshake.
> The issue is Mina2Consumer:160, it is setting UseClientMode to true, it
> should be false. Mina2Producer line 313 needs to also change to the following:
> SslFilter filter = new
> SslFilter(configuration.getSslContextParameters().createSSLContext(),
> configuration.isAutoStartTls());
> filter.setUseClientMode(true);
> connector.getFilterChain().addFirst("sslFilter", filter);
> As far as I can tell this has been a bug since this component was introduced.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8149) Support application-generated document identifiers in bulk index requests
[ https://issues.apache.org/jira/browse/CAMEL-8149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257200#comment-14257200 ] ASF GitHub Bot commented on CAMEL-8149: --- Github user dabdine-r7 closed the pull request at: https://github.com/apache/camel/pull/356 > Support application-generated document identifiers in bulk index requests > - > > Key: CAMEL-8149 > URL: https://issues.apache.org/jira/browse/CAMEL-8149 > Project: Camel > Issue Type: Improvement > Components: camel-elasticsearch >Affects Versions: 2.14.0 >Reporter: Derek Abdine >Assignee: Claus Ibsen > Fix For: 2.15.0 > > Attachments: camel-8149.patch > > > Elasticsearch (via the elasticsearch-java transport client) provides two > categories of APIs to write and read data: Individual requests (index, get, > delete) and bulk requests. > When performing bulk updates one creates individual index requests and adds > them to the bulk request. When creating an index request one can set the > source document, id, etc. > The current design of the camel-elasticsearch component controls the > transformation and assembly of an input body (json string, byte[], > xcontentfactory, map) to an index request. Thus, it is impossible to set the > id on the index request that goes into a bulk action. The end result is that > the id is set by the default behavior of the underlying elasticsearch-java > client which generates a random identifier. This is problematic in > situations where control is needed over the id, e.g. for de-duplication > purposes. > My proposal is to improve the design of the producer to allow for > elasticsearch-java ActionRequest sub-classes in the message body so that > upstream message processors can control the creation of those requests. > I've attached a patch and sent a pull request on github. > Thank you! > Derek Abdine -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CAMEL-8123) Mina2 SSL initiates handshake backwards
[
https://issues.apache.org/jira/browse/CAMEL-8123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257210#comment-14257210
]
ASF GitHub Bot commented on CAMEL-8123:
---
Github user peterberkman closed the pull request at:
https://github.com/apache/camel/pull/350
> Mina2 SSL initiates handshake backwards
> ---
>
> Key: CAMEL-8123
> URL: https://issues.apache.org/jira/browse/CAMEL-8123
> Project: Camel
> Issue Type: Bug
> Components: camel-mina2
>Affects Versions: 2.13.3, 2.14.0
>Reporter: Justin Cozzens
>Assignee: Willem Jiang
> Fix For: 2.13.4, 2.14.1, 2.15.0
>
>
> The Mina2Consumer and Mina2Producer are configured backwards for SSL
> handshake initiation. The consumer is trying to initiate the handshake rather
> than the producer. You can see this by setting up a SSL enabled consuming
> route and telnet to the port, you will immediately get some data sent from
> the server to the client rather than the server waiting on the client to
> initiate the handshake.
> The issue is Mina2Consumer:160, it is setting UseClientMode to true, it
> should be false. Mina2Producer line 313 needs to also change to the following:
> SslFilter filter = new
> SslFilter(configuration.getSslContextParameters().createSSLContext(),
> configuration.isAutoStartTls());
> filter.setUseClientMode(true);
> connector.getFilterChain().addFirst("sslFilter", filter);
> As far as I can tell this has been a bug since this component was introduced.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CAMEL-8174) Added TimeoutInflightRepository to track the long processing exchange
[ https://issues.apache.org/jira/browse/CAMEL-8174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257829#comment-14257829 ] Willem Jiang commented on CAMEL-8174: - Hi Claus, I know you did some related work recently, this issue is try to do some work without changing the camel-core API which means we can back port the patch to the patch branch. I already committed the a patch for it, it just added a new class and some tests, but I can leave this JIRA open before we discuss it after new year. > Added TimeoutInflightRepository to track the long processing exchange > - > > Key: CAMEL-8174 > URL: https://issues.apache.org/jira/browse/CAMEL-8174 > Project: Camel > Issue Type: Improvement >Reporter: Willem Jiang >Assignee: Willem Jiang > Fix For: 2.15.0 > > > It could be helpful is we can track the long processing exchange, user can > log or send alarm when getting these exchange by extending the > TimeoutInflightRepository. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CAMEL-8168) Mina Does Not Unbind From Listening Port
[
https://issues.apache.org/jira/browse/CAMEL-8168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-8168.
-
Resolution: Fixed
Applied the patch into camel master, camel-2.14.x and camel-2.13.x branches.
> Mina Does Not Unbind From Listening Port
>
>
> Key: CAMEL-8168
> URL: https://issues.apache.org/jira/browse/CAMEL-8168
> Project: Camel
> Issue Type: Bug
> Components: camel-mina2, el-mina2
>Affects Versions: 2.13.3, 2.14.1
>Reporter: Willem Jiang
>Assignee: Willem Jiang
> Fix For: 2.13.4, 2.14.2, 2.15.0
>
>
> If a bundle includes a mina consumer as the one below, when you stop the
> bundle, the port is not released. Therefore, when restarting the bundle,
> you'll get a port already in use bind exception.
> {code}
>
> {code}
> Note that the problem does not exist if you're using an IP address other than
> 0.0.0.0. For example:
> {code}
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
