[jira] [Commented] (CAMEL-14626) api maven plugin - Cannot load class
[ https://issues.apache.org/jira/browse/CAMEL-14626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071863#comment-17071863 ] Kirill Yankov commented on CAMEL-14626: --- [~amfirnas22] did you already start? I have done some progress here, I can leave it for you, and maybe help, in case you have already started. > api maven plugin - Cannot load class > > > Key: CAMEL-14626 > URL: https://issues.apache.org/jira/browse/CAMEL-14626 > Project: Camel > Issue Type: Improvement > Components: build system >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.x > > > Lets improve this maven plugin to skip classes that are just type ids, eg T > etc. We can check that the length of the class must be 2+ at least > [WARNING] Ignoring type parameters for argument type, unable to load > parametric type argument T > java.lang.ClassNotFoundException: java.lang.T > at java.net.URLClassLoader.findClass (URLClassLoader.java:471) > at java.lang.ClassLoader.loadClass (ClassLoader.java:588) > at java.lang.ClassLoader.loadClass (ClassLoader.java:521) > at org.apache.camel.maven.AbstractApiMethodGeneratorMojo.getCanonicalName > (AbstractApiMethodGeneratorMojo.java:345) > at jdk.internal.reflect.GeneratedMethodAccessor226.invoke (Unknown Source) > at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:566) > at > org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke > (UberspectImpl.java:556) > at > org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke > (UberspectImpl.java:539) > at org.apache.velocity.runtime.parser.node.ASTMethod.execute > (ASTMethod.java:214) > at org.apache.velocity.runtime.parser.node.ASTReference.execute > (ASTReference.java:324) > at org.apache.velocity.runtime.parser.node.ASTReference.value > (ASTReference.java:637) > at org.apache.velocity.runtime.parser.node.ASTExpression.value > (ASTExpression.java:72) > at org.apache.velocity.runtime.parser.node.ASTSetDirective.render > (ASTSetDirective.java:235) > at org.apache.velocity.runtime.parser.node.ASTBlock.render > (ASTBlock.java:144) > at org.apache.velocity.runtime.directive.Foreach.renderBlock > (Foreach.java:306) > at org.apache.velocity.runtime.directive.Foreach.render (Foreach.java:276) > at org.apache.velocity.runtime.parser.node.ASTDirective.render > (ASTDirective.java:295) > at org.apache.velocity.runtime.parser.node.SimpleNode.render > (SimpleNode.java:423) > at org.apache.velocity.Template.merge (Template.java:357) > at org.apache.velocity.Template.merge (Template.java:262) > at org.apache.camel.maven.AbstractGeneratorMojo.mergeTemplate > (AbstractGeneratorMojo.java:161) > at org.apache.camel.maven.AbstractApiMethodGeneratorMojo.executeInternal > (AbstractApiMethodGeneratorMojo.java:83) > at org.apache.camel.maven.ApiComponentGeneratorMojo.executeInternal > (ApiComponentGeneratorMojo.java:87) > at org.apache.camel.maven.AbstractGeneratorMojo.execute > (AbstractGeneratorMojo.java:103) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14626) api maven plugin - Cannot load class
[ https://issues.apache.org/jira/browse/CAMEL-14626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071862#comment-17071862 ] Kirill Yankov commented on CAMEL-14626: --- type parameter can be also encountered in a list of argTypes, for example Map, just ignoring it will make the generated code not compilable. Should we better substitute it with Object? > api maven plugin - Cannot load class > > > Key: CAMEL-14626 > URL: https://issues.apache.org/jira/browse/CAMEL-14626 > Project: Camel > Issue Type: Improvement > Components: build system >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.x > > > Lets improve this maven plugin to skip classes that are just type ids, eg T > etc. We can check that the length of the class must be 2+ at least > [WARNING] Ignoring type parameters for argument type, unable to load > parametric type argument T > java.lang.ClassNotFoundException: java.lang.T > at java.net.URLClassLoader.findClass (URLClassLoader.java:471) > at java.lang.ClassLoader.loadClass (ClassLoader.java:588) > at java.lang.ClassLoader.loadClass (ClassLoader.java:521) > at org.apache.camel.maven.AbstractApiMethodGeneratorMojo.getCanonicalName > (AbstractApiMethodGeneratorMojo.java:345) > at jdk.internal.reflect.GeneratedMethodAccessor226.invoke (Unknown Source) > at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke > (DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke (Method.java:566) > at > org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke > (UberspectImpl.java:556) > at > org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke > (UberspectImpl.java:539) > at org.apache.velocity.runtime.parser.node.ASTMethod.execute > (ASTMethod.java:214) > at org.apache.velocity.runtime.parser.node.ASTReference.execute > (ASTReference.java:324) > at org.apache.velocity.runtime.parser.node.ASTReference.value > (ASTReference.java:637) > at org.apache.velocity.runtime.parser.node.ASTExpression.value > (ASTExpression.java:72) > at org.apache.velocity.runtime.parser.node.ASTSetDirective.render > (ASTSetDirective.java:235) > at org.apache.velocity.runtime.parser.node.ASTBlock.render > (ASTBlock.java:144) > at org.apache.velocity.runtime.directive.Foreach.renderBlock > (Foreach.java:306) > at org.apache.velocity.runtime.directive.Foreach.render (Foreach.java:276) > at org.apache.velocity.runtime.parser.node.ASTDirective.render > (ASTDirective.java:295) > at org.apache.velocity.runtime.parser.node.SimpleNode.render > (SimpleNode.java:423) > at org.apache.velocity.Template.merge (Template.java:357) > at org.apache.velocity.Template.merge (Template.java:262) > at org.apache.camel.maven.AbstractGeneratorMojo.mergeTemplate > (AbstractGeneratorMojo.java:161) > at org.apache.camel.maven.AbstractApiMethodGeneratorMojo.executeInternal > (AbstractApiMethodGeneratorMojo.java:83) > at org.apache.camel.maven.ApiComponentGeneratorMojo.executeInternal > (ApiComponentGeneratorMojo.java:87) > at org.apache.camel.maven.AbstractGeneratorMojo.execute > (AbstractGeneratorMojo.java:103) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14734) camel-hbase - Upgrade to newer 2.x release
[ https://issues.apache.org/jira/browse/CAMEL-14734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061546#comment-17061546 ] Kirill Yankov commented on CAMEL-14734: --- I'll try to do it > camel-hbase - Upgrade to newer 2.x release > -- > > Key: CAMEL-14734 > URL: https://issues.apache.org/jira/browse/CAMEL-14734 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14735) Upgrade hbase component to the latest version of hbase (2.x.x)
[ https://issues.apache.org/jira/browse/CAMEL-14735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061544#comment-17061544 ] Kirill Yankov commented on CAMEL-14735: --- closing as duplicate, sorry > Upgrade hbase component to the latest version of hbase (2.x.x) > -- > > Key: CAMEL-14735 > URL: https://issues.apache.org/jira/browse/CAMEL-14735 > Project: Camel > Issue Type: Improvement > Components: camel-hbase >Reporter: Kirill Yankov >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (CAMEL-14735) Upgrade hbase component to the latest version of hbase (2.x.x)
[ https://issues.apache.org/jira/browse/CAMEL-14735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Yankov closed CAMEL-14735. - Resolution: Duplicate > Upgrade hbase component to the latest version of hbase (2.x.x) > -- > > Key: CAMEL-14735 > URL: https://issues.apache.org/jira/browse/CAMEL-14735 > Project: Camel > Issue Type: Improvement > Components: camel-hbase >Reporter: Kirill Yankov >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14735) Upgrade hbase component to the latest version of hbase (2.x.x)
Kirill Yankov created CAMEL-14735: - Summary: Upgrade hbase component to the latest version of hbase (2.x.x) Key: CAMEL-14735 URL: https://issues.apache.org/jira/browse/CAMEL-14735 Project: Camel Issue Type: Improvement Components: camel-hbase Reporter: Kirill Yankov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14576) camel-hbase - Test using test containers
[
https://issues.apache.org/jira/browse/CAMEL-14576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060601#comment-17060601
]
Kirill Yankov commented on CAMEL-14576:
---
Just an interesting notice. Tests for the component are currently not working
at all. There is a dependency problem with Guava which leads to exception when
starting HBaseTestingUtility.
{code:java}
java.lang.NoSuchMethodError:
com.google.common.base.Objects.toStringHelper(Ljava/lang/Object;)Lcom/google/common/base/Objects$ToStringHelper;
at
org.apache.hadoop.metrics2.lib.MetricsRegistry.toString(MetricsRegistry.java:414)at
org.apache.hadoop.metrics2.lib.MetricsRegistry.toString(MetricsRegistry.java:414)
at java.lang.String.valueOf(String.java:2994) at
java.lang.StringBuilder.append(StringBuilder.java:131){code}
But this is suppressed in tests: by the check
{code:java}
if (systemReady){
//test actions
}
{code}
`systemReady` is set to false on exception and all the tests are just skipped.
> camel-hbase - Test using test containers
>
>
> Key: CAMEL-14576
> URL: https://issues.apache.org/jira/browse/CAMEL-14576
> Project: Camel
> Issue Type: Improvement
>Reporter: Claus Ibsen
>Priority: Major
> Labels: help-wanted
> Fix For: 3.x
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14576) camel-hbase - Test using test containers
[ https://issues.apache.org/jira/browse/CAMEL-14576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060118#comment-17060118 ] Kirill Yankov commented on CAMEL-14576: --- Or you suggest just to implement GenericContainer container class, and put all the HBase init logic in it? > camel-hbase - Test using test containers > > > Key: CAMEL-14576 > URL: https://issues.apache.org/jira/browse/CAMEL-14576 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14576) camel-hbase - Test using test containers
[ https://issues.apache.org/jira/browse/CAMEL-14576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17059907#comment-17059907 ] Kirill Yankov edited comment on CAMEL-14576 at 3/16/20, 2:42 AM: - Just to clarify. So you suggest to move HBaseTestingUtility startup and configuration to a container? Then the question is where to keep this test-utility initialisation code (which will run in a generic java container)? In camel-testcontainers project? was (Author: manonthegithub): Just to clarify. So you suggest to move HBaseTestingUtility startup and configuration to a container? Then the question is where to keep this test-utility initialisation code? In camel-testcontainers project? > camel-hbase - Test using test containers > > > Key: CAMEL-14576 > URL: https://issues.apache.org/jira/browse/CAMEL-14576 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14576) camel-hbase - Test using test containers
[ https://issues.apache.org/jira/browse/CAMEL-14576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17059907#comment-17059907 ] Kirill Yankov commented on CAMEL-14576: --- Just to clarify. So you suggest to move HBaseTestingUtility startup and configuration to a container? Then the question is where to keep this test-utility initialisation code? In camel-testcontainers project? > camel-hbase - Test using test containers > > > Key: CAMEL-14576 > URL: https://issues.apache.org/jira/browse/CAMEL-14576 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14576) camel-hbase - Test using test containers
[ https://issues.apache.org/jira/browse/CAMEL-14576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058680#comment-17058680 ] Kirill Yankov commented on CAMEL-14576: --- have looked into HBase docker containers, and there seems no official one. What is approach to that? Do you make your own containers and publish them in some docker repo? > camel-hbase - Test using test containers > > > Key: CAMEL-14576 > URL: https://issues.apache.org/jira/browse/CAMEL-14576 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14704) Checkstyle could also do autoformatting
Kirill Yankov created CAMEL-14704: - Summary: Checkstyle could also do autoformatting Key: CAMEL-14704 URL: https://issues.apache.org/jira/browse/CAMEL-14704 Project: Camel Issue Type: Wish Components: build system Reporter: Kirill Yankov I am a new contributor. And as I see in docs and after trial the checkstyle command only does checking of your sources, and outputs details of where you need to correct. It would be nice to have check style which does formatting in project's style automatically, so that you won't need to do it manually. I have used corresponding plugin in scala sbt, there must be one for maven java. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14455) camel-rabbitmq - Option to override the Rabbit MQ DefaultExceptionHandler
[ https://issues.apache.org/jira/browse/CAMEL-14455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17056601#comment-17056601 ] Kirill Yankov commented on CAMEL-14455: --- I think, I can take this issue. I will submit PR asap. > camel-rabbitmq - Option to override the Rabbit MQ DefaultExceptionHandler > - > > Key: CAMEL-14455 > URL: https://issues.apache.org/jira/browse/CAMEL-14455 > Project: Camel > Issue Type: New Feature > Components: camel-rabbitmq >Affects Versions: 2.24.1 >Reporter: Muhammed Shanid A K >Priority: Major > Labels: help-wanted > Fix For: 3.2.0 > > > As mentioned below in the document, Rabbit MQ provide an option to override > the handler of unhandled exception using > ConnectionFactory#setExceptionHandler > [https://www.rabbitmq.com/api-guide.html#unhandled-exceptions] > > Please add a this feature in camel-rabbit when connecting to Rabbit MQ via > Apache Camel. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14663) Camel-AWS2 S3: Add support for multipart download
[ https://issues.apache.org/jira/browse/CAMEL-14663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17054952#comment-17054952 ] Kirill Yankov commented on CAMEL-14663: --- I looked into S3Client interface and there seems to be only support for multipart upload. You probably mean multipart upload? This is for producer. Right? > Camel-AWS2 S3: Add support for multipart download > - > > Key: CAMEL-14663 > URL: https://issues.apache.org/jira/browse/CAMEL-14663 > Project: Camel > Issue Type: Task > Components: camel-aws2 >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-10652) Create a component for Kafka-Stream
[ https://issues.apache.org/jira/browse/CAMEL-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046070#comment-17046070 ] Kirill Yankov commented on CAMEL-10652: --- Manish doesn't mind if I do the component, so I have a few questions. Kafka stream supports not only consuming and producing messages, but lots of transformations. As I understand implementing transformations in the component is not needed (as it is done in camel Producers), so the main things to be implemented are raw Producer and Consumer (as a part of Endpoint and Component), and may them as universal a possible. Therefore the transformation part of Kafka Streams is not a concern. Is that right? > Create a component for Kafka-Stream > --- > > Key: CAMEL-10652 > URL: https://issues.apache.org/jira/browse/CAMEL-10652 > Project: Camel > Issue Type: New Feature > Components: camel-kafka >Reporter: Andrea Cosentino >Priority: Minor > Labels: gsoc2020 > Fix For: Future > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-10173) Create a camel component for etcd v3
[ https://issues.apache.org/jira/browse/CAMEL-10173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17044351#comment-17044351 ] Kirill Yankov commented on CAMEL-10173: --- Hello! I'd like to participate in GSoC, and can work on this component as well! > Create a camel component for etcd v3 > > > Key: CAMEL-10173 > URL: https://issues.apache.org/jira/browse/CAMEL-10173 > Project: Camel > Issue Type: New Feature >Reporter: Luca Burgazzoli >Priority: Minor > Labels: gsoc2020 > Fix For: Future > > > See https://github.com/coreos/jetcd -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-10652) Create a component for Kafka-Stream
[ https://issues.apache.org/jira/browse/CAMEL-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17044350#comment-17044350 ] Kirill Yankov commented on CAMEL-10652: --- I'd like to contribute too as GSoC, in case Manish will have problems or drops it. > Create a component for Kafka-Stream > --- > > Key: CAMEL-10652 > URL: https://issues.apache.org/jira/browse/CAMEL-10652 > Project: Camel > Issue Type: New Feature > Components: camel-kafka >Reporter: Andrea Cosentino >Priority: Minor > Labels: gsoc2020 > Fix For: Future > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
