[jira] [Created] (IGNITE-7804) when new node join cluster,rebalance communication with demand and supply message is very slow
dean created IGNITE-7804: Summary: when new node join cluster,rebalance communication with demand and supply message is very slow Key: IGNITE-7804 URL: https://issues.apache.org/jira/browse/IGNITE-7804 Project: Ignite Issue Type: Bug Components: general Affects Versions: 1.9 Reporter: dean -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7803) REST: Add support to get values inserted via SQL
Alexey Kuznetsov created IGNITE-7803:
Summary: REST: Add support to get values inserted via SQL
Key: IGNITE-7803
URL: https://issues.apache.org/jira/browse/IGNITE-7803
Project: Ignite
Issue Type: Task
Components: rest
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
Fix For: 2.5
Scenario:
# create table person(id integer primary key, name varchar(100), salary
integer);
# insert into person(id, name, salary) values (1, Alex, 300)
# get via REST:
{{http://host:port/ignite?cmd=get=SQL_PUBLIC_PERSON=int=1}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7802) Clarify how to hook Ignite and a 3rd party persistence
Denis Magda created IGNITE-7802: --- Summary: Clarify how to hook Ignite and a 3rd party persistence Key: IGNITE-7802 URL: https://issues.apache.org/jira/browse/IGNITE-7802 Project: Ignite Issue Type: Task Components: documentation Reporter: Denis Magda Assignee: Akmal Chaudhri Fix For: 2.5 The existing documentation doesn't explain all the steps needed to integrate Ignite with a 3rd party db: [https://apacheignite.readme.io/docs/3rd-party-store] Specifically, the following has to be covered: * Dedicated section for RDBMS setup. Copying of a JDBC driver, enabling a right CacheStore implementation, defining the mapping, or automating this process with Web Console. * NoSQL databases section. Refer to Cassandra pages. * Other 3rd party stores. Clarify how to write a custom CacheStore that is not supported out of the box. The goal is to avoid questions like this: http://apache-ignite-users.70518.x6.nabble.com/Ignite-with-mariadb-td20101.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7419) Document swap usage in Ignite 2.x memory architecture
[ https://issues.apache.org/jira/browse/IGNITE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16375099#comment-16375099 ] Prachi Garg commented on IGNITE-7419: - To do: * Update the Durable Memory page[1]: In Persistence section, create 3 sub sections - Native Persistence, 3rd Party Persistence, Swap * Add a Swap page in Durable Memory section on Readme.io * Update wikipedia page[2] - Add information about swap [1] [https://apacheignite.readme.io/docs/durable-memory] [2] https://en.wikipedia.org/wiki/Apache_Ignite#Memory_architecture > Document swap usage in Ignite 2.x memory architecture > - > > Key: IGNITE-7419 > URL: https://issues.apache.org/jira/browse/IGNITE-7419 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.4 > > > Explain how swap is supported and works in Ignite. Provide a rationale on > Ignite persistence vs swap. > In addition, looks people don't catch what happens when memory region goes > beyond the maximum size. Revisit the persistence configuration: > [http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-3-Swap-Path-configuration-is-causing-issue-td19040.html#a19046] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7131) Document Web Console deployment in Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-7131: Fix Version/s: 2.5 > Document Web Console deployment in Kubernetes > - > > Key: IGNITE-7131 > URL: https://issues.apache.org/jira/browse/IGNITE-7131 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.5 >Reporter: Denis Magda >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.5 > > > The ticket is inspired by the following topic: > http://apache-ignite-users.70518.x6.nabble.com/Web-Console-on-Kubernetes-Cluster-td18591.html > It will be great to put together a documentation about Web Console deployment > on Kubernetes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7131) Document Web Console deployment in Kubernetes
[ https://issues.apache.org/jira/browse/IGNITE-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-7131: --- Assignee: Alexey Kuznetsov > Document Web Console deployment in Kubernetes > - > > Key: IGNITE-7131 > URL: https://issues.apache.org/jira/browse/IGNITE-7131 > Project: Ignite > Issue Type: Task > Components: documentation >Affects Versions: 2.5 >Reporter: Denis Magda >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.5 > > > The ticket is inspired by the following topic: > http://apache-ignite-users.70518.x6.nabble.com/Web-Console-on-Kubernetes-Cluster-td18591.html > It will be great to put together a documentation about Web Console deployment > on Kubernetes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7419) Document swap usage in Ignite 2.x memory architecture
[
https://issues.apache.org/jira/browse/IGNITE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16375084#comment-16375084
]
Denis Magda commented on IGNITE-7419:
-
{{DataRegionConfiguration.getSwapPath/setSwapPath}} is used to configure the
swapping capabilities.
> Document swap usage in Ignite 2.x memory architecture
> -
>
> Key: IGNITE-7419
> URL: https://issues.apache.org/jira/browse/IGNITE-7419
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.4
>
>
> Explain how swap is supported and works in Ignite. Provide a rationale on
> Ignite persistence vs swap.
> In addition, looks people don't catch what happens when memory region goes
> beyond the maximum size. Revisit the persistence configuration:
> [http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-3-Swap-Path-configuration-is-causing-issue-td19040.html#a19046]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7536) Document baseline topology feature and its WebConsole screen
[ https://issues.apache.org/jira/browse/IGNITE-7536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg reassigned IGNITE-7536: --- Assignee: Denis Magda (was: Prachi Garg) > Document baseline topology feature and its WebConsole screen > - > > Key: IGNITE-7536 > URL: https://issues.apache.org/jira/browse/IGNITE-7536 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Denis Magda >Priority: Major > Fix For: 2.4 > > > Document Baseline topology: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-4+Baseline+topology+for+caches] > and how to manage it with Web Console and control.sh script (Ignite > activation doc has to be updated). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7419) Document swap usage in Ignite 2.x memory architecture
[ https://issues.apache.org/jira/browse/IGNITE-7419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-7419: --- Assignee: Prachi Garg (was: Denis Magda) > Document swap usage in Ignite 2.x memory architecture > - > > Key: IGNITE-7419 > URL: https://issues.apache.org/jira/browse/IGNITE-7419 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.4 > > > Explain how swap is supported and works in Ignite. Provide a rationale on > Ignite persistence vs swap. > In addition, looks people don't catch what happens when memory region goes > beyond the maximum size. Revisit the persistence configuration: > [http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-3-Swap-Path-configuration-is-causing-issue-td19040.html#a19046] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7536) Document baseline topology feature and its WebConsole screen
[ https://issues.apache.org/jira/browse/IGNITE-7536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-7536: --- Assignee: Prachi Garg (was: Denis Magda) > Document baseline topology feature and its WebConsole screen > - > > Key: IGNITE-7536 > URL: https://issues.apache.org/jira/browse/IGNITE-7536 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Denis Magda >Assignee: Prachi Garg >Priority: Major > Fix For: 2.4 > > > Document Baseline topology: > [https://cwiki.apache.org/confluence/display/IGNITE/IEP-4+Baseline+topology+for+caches] > and how to manage it with Web Console and control.sh script (Ignite > activation doc has to be updated). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented
[ https://issues.apache.org/jira/browse/IGNITE-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda reassigned IGNITE-7655: --- Assignee: Nikolay Izhikov (was: Denis Magda) > Spark Data Frames: saving data frames into Ignite needs to be documented > > > Key: IGNITE-7655 > URL: https://issues.apache.org/jira/browse/IGNITE-7655 > Project: Ignite > Issue Type: Bug > Components: documentation, spark >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.4 > > > Once IGNITE-7337 is ready for merge. > This new feature of Ignite needs to be documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented
[ https://issues.apache.org/jira/browse/IGNITE-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16375007#comment-16375007 ] Denis Magda commented on IGNITE-7655: - [~NIzhikov] , please clarify the following questions. # You're saying "the data frame will be appended to the existing table. Existing table data will not be changed.". What does appending mean here? As far as I understand, you're just going to *insert* new data ignoring the data which keys are already in the table. # which mode is a default? # Is there a mode that updates existing rows, inserts new from the data frame and does NOT delete the rows that were in the table initially? # How do I set a mode? You start talking about the data frames right away but do not explain how to use them. # You say "Note, internally all inserts are done through IgniteDataStreamer. Several optional parameters exists to configure internal streamer. Please, see full list of available options.". I would start "Saving Data Frame" section with the explanation of how all this works. From what I see, we're going to use CREATE TABLE to create a table and then store data in Ignite with the streamer, right? Please elaborate more on this in the doc. [~abchaudhri], could you please finalize the review after [~NIzhikov] addresses the notes above? Please feel free to work together to make this doc exceptional and easy to follow! > Spark Data Frames: saving data frames into Ignite needs to be documented > > > Key: IGNITE-7655 > URL: https://issues.apache.org/jira/browse/IGNITE-7655 > Project: Ignite > Issue Type: Bug > Components: documentation, spark >Reporter: Nikolay Izhikov >Assignee: Denis Magda >Priority: Major > Fix For: 2.4 > > > Once IGNITE-7337 is ready for merge. > This new feature of Ignite needs to be documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7801) Missing artifact org.apache.ignite:ignite-hibernate_5.1
[ https://issues.apache.org/jira/browse/IGNITE-7801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavan Jadda updated IGNITE-7801: Priority: Blocker (was: Major) > Missing artifact org.apache.ignite:ignite-hibernate_5.1 > --- > > Key: IGNITE-7801 > URL: https://issues.apache.org/jira/browse/IGNITE-7801 > Project: Ignite > Issue Type: Bug > Components: build >Affects Versions: 2.3 >Reporter: Pavan Jadda >Priority: Blocker > > I am trying to implement Hibernate 2nd level cache with Apache Ignite. For > this, I used following maven dependency in pom.xml based on Apache Ignite > [official > documentation|https://apacheignite-mix.readme.io/docs/hibernate-l2-cache]. I > got following excepti[on > |https://apacheignite-mix.readme.io/docs/hibernate-l2-cache]*Missing artifact > org.apache.ignite:ignite-hibernate_5.1:jar:2.3.0* when I build the project. > Code uploaded to > [#https://github.com/pavankjadda/ApacheIgnite-JHipster-Docker]. I am using > Apache Ignite 2.3.0 version. I tried other versions too and nothing worked -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7801) Missing artifact org.apache.ignite:ignite-hibernate_5.1
Pavan Jadda created IGNITE-7801: --- Summary: Missing artifact org.apache.ignite:ignite-hibernate_5.1 Key: IGNITE-7801 URL: https://issues.apache.org/jira/browse/IGNITE-7801 Project: Ignite Issue Type: Bug Components: build Affects Versions: 2.3 Reporter: Pavan Jadda I am trying to implement Hibernate 2nd level cache with Apache Ignite. For this, I used following maven dependency in pom.xml based on Apache Ignite [official documentation|https://apacheignite-mix.readme.io/docs/hibernate-l2-cache]. I got following excepti[on |https://apacheignite-mix.readme.io/docs/hibernate-l2-cache]*Missing artifact org.apache.ignite:ignite-hibernate_5.1:jar:2.3.0* when I build the project. Code uploaded to [#https://github.com/pavankjadda/ApacheIgnite-JHipster-Docker]. I am using Apache Ignite 2.3.0 version. I tried other versions too and nothing worked -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7415) Ability to disable WAL (Documentation)
[ https://issues.apache.org/jira/browse/IGNITE-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda closed IGNITE-7415. --- > Ability to disable WAL (Documentation) > -- > > Key: IGNITE-7415 > URL: https://issues.apache.org/jira/browse/IGNITE-7415 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Anton Vinogradov >Assignee: Prachi Garg >Priority: Critical > Fix For: 2.4 > > > Need to update > [https://apacheignite.readme.io/docs/write-ahead-log#section-wal-modes] > [https://apacheignite.readme.io/docs/data-loading] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PandaMonkey updated IGNITE-7799: Description: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. Maven provides the version arbitration mechanism-"nearest wins strategy", and then your project will explicitly use the older version: httpclient:4.5.1. However, Maven doesn't know which version is actual required by your project. If ignite depends on the methods of com.amazonaws:aws-java-sdk-core, at the same time, those invoked methods need the features definded in httpclient:4.5.2. It would be nice to keep the consistency of library version. It is a minor issue, which will not lead to runtime errors at present stage, however, it may be a potencial risk in long-term maintainance. For the project long-term health, it would be nice to keep the consistency of library version, then the potencial dependency conflict risks can be also elimited. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: was: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. Maven provides the version arbitration mechanism-"nearest wins strategy", and then your project will explicitly use the older version: httpclient:4.5.1. However, Maven doesn't know which version is actual required by your project. If ignite depends on the methods of com.amazonaws:aws-java-sdk-core, at the same time, those invoked methods need the features definded in httpclient:4.5.2. The dependency conflict problem will appear. For the project long-term health, it would be nice to keep the consistency of library version, then the dependency conflict risks can be also elimited. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE
[jira] [Created] (IGNITE-7800) Invalid javadoc for IgniteSystemProperties.IGNITE_NO_SHUTDOWN_HOOK
Ryszard Trojnacki created IGNITE-7800:
-
Summary: Invalid javadoc for
IgniteSystemProperties.IGNITE_NO_SHUTDOWN_HOOK
Key: IGNITE-7800
URL: https://issues.apache.org/jira/browse/IGNITE-7800
Project: Ignite
Issue Type: Bug
Components: 2.3
Affects Versions: 2.3
Reporter: Ryszard Trojnacki
JavaDoc for IgniteSystemProperties.IGNITE_NO_SHUTDOWN_HOOK is:
{quote}_If this system property is set to \{@code false} - no shutdown hook
will be set._
{quote}
but this is incorrect. It should be:
{quote}_If this system property is set to {@code *true*} - no shutdown hook
will be set._
{quote}
Also in code of IgnitionEx.java comment says it should be true, and the same is
from if expression.
{code:java}
// Do NOT set it up only if IGNITE_NO_SHUTDOWN_HOOK=TRUE is provided. if
(!IgniteSystemProperties.getBoolean(IGNITE_NO_SHUTDOWN_HOOK, false)) {
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PandaMonkey updated IGNITE-7799: Description: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. Maven provides the version arbitration mechanism-"nearest wins strategy", and then your project will explicitly use the older version: httpclient:4.5.1. However, Maven doesn't know which version is actual required by your project. If ignite depends on the methods of com.amazonaws:aws-java-sdk-core, at the same time, those invoked methods need the features definded in httpclient:4.5.2. The dependency conflict problem will appear. For the project long-term health, it would be nice to keep the consistency of library version, then the dependency conflict risks can be also elimited. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: was: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. Maven provides the version arbitration mechanism-"nearest wins strategy", and then your project will explicitly use the older version: httpclient:4.5.1. However, Maven doesn't know which version is actual required by your project. If ignite depends on the methods of com.amazonaws:aws-java-sdk-core, at the same time, those invoked methods need the features definded in httpclient:4.5.2. The dependency conflict problem will appear. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient >
[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PandaMonkey updated IGNITE-7799: Description: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. Maven provides the version arbitration mechanism-"nearest wins strategy", and then your project will explicitly use the older version: httpclient:4.5.1. However, Maven doesn't know which version is actual required by your project. If ignite depends on the methods of com.amazonaws:aws-java-sdk-core, at the same time, those invoked methods need the features definded in httpclient:4.5.2. The dependency conflict problem will appear. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: was: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. Maven provides the version arbitration mechanism-"nearest wins", and then your project will explicitly use the older version: httpclient:4.5.1. However, Maven doesn't know which version is actual required by your project. If ignite depends on the methods of com.amazonaws:aws-java-sdk-core, at the same time, those invoked methods need the features definded in httpclient:4.5.2. The dependency conflict problem will appear. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient > -- > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 >
[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PandaMonkey updated IGNITE-7799: Description: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. Maven provides the version arbitration mechanism-"nearest wins", and then your project will explicitly use the older version: httpclient:4.5.1. However, Maven doesn't know which version is actual required by your project. If ignite depends on the methods of com.amazonaws:aws-java-sdk-core, at the same time, those invoked methods need the features definded in httpclient:4.5.2. The dependency conflict problem will appear. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: was: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. Maven provides the version arbitration mechanism-"nearest wins", and then your project will explicitly use the older version: httpclient:4.5.1. The problem will arise when Ignite uses the methods defined in the transitive JAR httpclient 4.5.2, and those required methods don't exist in the loaded version httpclient:4.5.1. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient > -- > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 > Project: Ignite > Issue Type: Bug > Components: aws >Affects Versions: 2.5 >
[jira] [Commented] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374366#comment-16374366 ] PandaMonkey commented on IGNITE-7799: - [~vkulichenko] I accept that you close the issue. Maven doesn't know which version is actual required by your project. If ignite depends on the methods of com.amazonaws:aws-java-sdk-core, at the same time, those invoked methods need the features definded in httpclient:4.5.2. The problem will appear. Btw, nearly all the dependency conflict errors can not be detected during compiling process. > Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient > -- > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 > Project: Ignite > Issue Type: Bug > Components: aws >Affects Versions: 2.5 >Reporter: PandaMonkey >Priority: Minor > Fix For: 3.0 > > > Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are > two versions of *org.apache.httpcomponents:httpclient*. Their introduced path > is: > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 > is the direct dependency. By further analyzing the source code, we found they > have different features. > Maven provides the version arbitration mechanism-"nearest wins", and then > your project will explicitly use the older version: httpclient:4.5.1. The > problem will arise when Ignite uses the methods defined in the transitive JAR > httpclient 4.5.2, and those required methods don't exist in the loaded > version httpclient:4.5.1. > The dependency conflict problem brings high risks of > "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please > notice this problem. *The solution is upgrading httpclient from 4.5.1 to > 4.5.2.* > > ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml > > ===conflict: > size:2 > > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > *Risk for ClassNotFoundException/NotClassDefFoundError:* > a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: > org.apache.http.client.utils.DateUtils$DateFormatHolder$1 > b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: > org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE > org.apache.http.impl.client.DefaultClientConnectionReuseStrategy > org.apache.http.conn.ssl.DefaultHostnameVerifier$1 > *Risk for NoSuchMethodException/NoSuchMethodError:* > Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > createLocalDomainMap()> > match(org.apache.http.cookie.Cookie,org.apache.http.cookie.CookieOrigin)> > org.apache.http.impl.client.HttpClientBuilder > setDnsResolver(org.apache.http.conn.DnsResolver)> > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374346#comment-16374346 ] Valentin Kulichenko commented on IGNITE-7799: - Ignite can't use 4.5.2, because this dependency is excluded by Maven. Such code will not even compile. I don't see an issue here. Closing the ticket. > Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient > -- > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 > Project: Ignite > Issue Type: Bug > Components: aws >Affects Versions: 2.5 >Reporter: PandaMonkey >Priority: Minor > Fix For: 3.0 > > > Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are > two versions of *org.apache.httpcomponents:httpclient*. Their introduced path > is: > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 > is the direct dependency. By further analyzing the source code, we found they > have different features. > Maven provides the version arbitration mechanism-"nearest wins", and then > your project will explicitly use the older version: httpclient:4.5.1. The > problem will arise when Ignite uses the methods defined in the transitive JAR > httpclient 4.5.2, and those required methods don't exist in the loaded > version httpclient:4.5.1. > The dependency conflict problem brings high risks of > "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please > notice this problem. *The solution is upgrading httpclient from 4.5.1 to > 4.5.2.* > > ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml > > ===conflict: > size:2 > > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > *Risk for ClassNotFoundException/NotClassDefFoundError:* > a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: > org.apache.http.client.utils.DateUtils$DateFormatHolder$1 > b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: > org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE > org.apache.http.impl.client.DefaultClientConnectionReuseStrategy > org.apache.http.conn.ssl.DefaultHostnameVerifier$1 > *Risk for NoSuchMethodException/NoSuchMethodError:* > Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > createLocalDomainMap()> > match(org.apache.http.cookie.Cookie,org.apache.http.cookie.CookieOrigin)> > org.apache.http.impl.client.HttpClientBuilder > setDnsResolver(org.apache.http.conn.DnsResolver)> > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko closed IGNITE-7799. --- > Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient > -- > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 > Project: Ignite > Issue Type: Bug > Components: aws >Affects Versions: 2.5 >Reporter: PandaMonkey >Priority: Minor > Fix For: 3.0 > > > Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are > two versions of *org.apache.httpcomponents:httpclient*. Their introduced path > is: > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 > is the direct dependency. By further analyzing the source code, we found they > have different features. > Maven provides the version arbitration mechanism-"nearest wins", and then > your project will explicitly use the older version: httpclient:4.5.1. The > problem will arise when Ignite uses the methods defined in the transitive JAR > httpclient 4.5.2, and those required methods don't exist in the loaded > version httpclient:4.5.1. > The dependency conflict problem brings high risks of > "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please > notice this problem. *The solution is upgrading httpclient from 4.5.1 to > 4.5.2.* > > ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml > > ===conflict: > size:2 > > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > *Risk for ClassNotFoundException/NotClassDefFoundError:* > a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: > org.apache.http.client.utils.DateUtils$DateFormatHolder$1 > b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: > org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE > org.apache.http.impl.client.DefaultClientConnectionReuseStrategy > org.apache.http.conn.ssl.DefaultHostnameVerifier$1 > *Risk for NoSuchMethodException/NoSuchMethodError:* > Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > createLocalDomainMap()> > match(org.apache.http.cookie.Cookie,org.apache.http.cookie.CookieOrigin)> > org.apache.http.impl.client.HttpClientBuilder > setDnsResolver(org.apache.http.conn.DnsResolver)> > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentin Kulichenko resolved IGNITE-7799. - Resolution: Not A Problem > Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient > -- > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 > Project: Ignite > Issue Type: Bug > Components: aws >Affects Versions: 2.5 >Reporter: PandaMonkey >Priority: Minor > Fix For: 3.0 > > > Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are > two versions of *org.apache.httpcomponents:httpclient*. Their introduced path > is: > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 > is the direct dependency. By further analyzing the source code, we found they > have different features. > Maven provides the version arbitration mechanism-"nearest wins", and then > your project will explicitly use the older version: httpclient:4.5.1. The > problem will arise when Ignite uses the methods defined in the transitive JAR > httpclient 4.5.2, and those required methods don't exist in the loaded > version httpclient:4.5.1. > The dependency conflict problem brings high risks of > "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please > notice this problem. *The solution is upgrading httpclient from 4.5.1 to > 4.5.2.* > > ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml > > ===conflict: > size:2 > > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > *Risk for ClassNotFoundException/NotClassDefFoundError:* > a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: > org.apache.http.client.utils.DateUtils$DateFormatHolder$1 > b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: > org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE > org.apache.http.impl.client.DefaultClientConnectionReuseStrategy > org.apache.http.conn.ssl.DefaultHostnameVerifier$1 > *Risk for NoSuchMethodException/NoSuchMethodError:* > Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > createLocalDomainMap()> > match(org.apache.http.cookie.Cookie,org.apache.http.cookie.CookieOrigin)> > org.apache.http.impl.client.HttpClientBuilder > setDnsResolver(org.apache.http.conn.DnsResolver)> > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PandaMonkey updated IGNITE-7799: Description: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. Maven provides the version arbitration mechanism-"nearest wins", and then your project will explicitly use the older version: httpclient:4.5.1. The problem will arise when Ignite uses the methods defined in the transitive JAR httpclient 4.5.2, and those required methods don't exist in the loaded version httpclient:4.5.1. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: was: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient > -- > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 > Project: Ignite > Issue Type: Bug > Components: aws >Affects Versions: 2.5 >Reporter: PandaMonkey >Priority: Minor > Fix For: 3.0 > > > Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are > two versions of *org.apache.httpcomponents:httpclient*. Their introduced path > is: > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > # >
[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PandaMonkey updated IGNITE-7799: Description: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: was: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. It is a minor issue, which will not lead to runtime errors at present stage, however, it may be a potencial risk in long-term maintainance. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient > -- > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 > Project: Ignite > Issue Type: Bug > Components: aws >Affects Versions: 2.5 >Reporter: PandaMonkey >Priority: Minor > Fix For: 3.0 > > > Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are > two versions of *org.apache.httpcomponents:httpclient*. Their introduced path > is: > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 > is the direct
[jira] [Commented] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374332#comment-16374332 ] PandaMonkey commented on IGNITE-7799: - [~vkulichenko], thx for your quick reply. Of course, Maven provides the version arbitration mechanism-"nearest wins", and then your project will explicitly use the older version: httpclient:4.5.1. The problem will arise when Ignite uses the methods defined in the transitive JAR httpclient 4.5.2, and those required methods don't exist in the loaded version httpclient:4.5.1. So it would be nice to keep the consistency of library version. That's what I want to say. Thanks again. > Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient > -- > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 > Project: Ignite > Issue Type: Bug > Components: aws >Affects Versions: 2.5 >Reporter: PandaMonkey >Priority: Minor > Fix For: 3.0 > > > Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are > two versions of *org.apache.httpcomponents:httpclient*. Their introduced path > is: > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 > is the direct dependency. By further analyzing the source code, we found they > have different features. It is a minor issue, which will not lead to runtime > errors at present stage, however, it may be a potencial risk in long-term > maintainance. The dependency conflict problem brings high risks of > "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please > notice this problem. *The solution is upgrading httpclient from 4.5.1 to > 4.5.2.* > > ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml > > ===conflict: > size:2 > > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > *Risk for ClassNotFoundException/NotClassDefFoundError:* > a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: > org.apache.http.client.utils.DateUtils$DateFormatHolder$1 > b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: > org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE > org.apache.http.impl.client.DefaultClientConnectionReuseStrategy > org.apache.http.conn.ssl.DefaultHostnameVerifier$1 > *Risk for NoSuchMethodException/NoSuchMethodError:* > Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > createLocalDomainMap()> > match(org.apache.http.cookie.Cookie,org.apache.http.cookie.CookieOrigin)> > org.apache.http.impl.client.HttpClientBuilder > setDnsResolver(org.apache.http.conn.DnsResolver)> > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PandaMonkey updated IGNITE-7799: Description: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. It is a minor issue, which will not lead to runtime errors at present stage, however, it may be a potencial risk in long-term maintainance. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: was: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient > -- > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 > Project: Ignite > Issue Type: Bug > Components: aws >Affects Versions: 2.5 >Reporter: PandaMonkey >Priority: Major > Fix For: 3.0 > > > Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are > two versions of *org.apache.httpcomponents:httpclient*. Their introduced path > is: > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 > is the direct
[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PandaMonkey updated IGNITE-7799: Priority: Minor (was: Major) > Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient > -- > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 > Project: Ignite > Issue Type: Bug > Components: aws >Affects Versions: 2.5 >Reporter: PandaMonkey >Priority: Minor > Fix For: 3.0 > > > Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are > two versions of *org.apache.httpcomponents:httpclient*. Their introduced path > is: > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 > is the direct dependency. By further analyzing the source code, we found they > have different features. It is a minor issue, which will not lead to runtime > errors at present stage, however, it may be a potencial risk in long-term > maintainance. The dependency conflict problem brings high risks of > "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please > notice this problem. *The solution is upgrading httpclient from 4.5.1 to > 4.5.2.* > > ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml > > ===conflict: > size:2 > > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > *Risk for ClassNotFoundException/NotClassDefFoundError:* > a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: > org.apache.http.client.utils.DateUtils$DateFormatHolder$1 > b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: > org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE > org.apache.http.impl.client.DefaultClientConnectionReuseStrategy > org.apache.http.conn.ssl.DefaultHostnameVerifier$1 > *Risk for NoSuchMethodException/NoSuchMethodError:* > Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > createLocalDomainMap()> > match(org.apache.http.cookie.Cookie,org.apache.http.cookie.CookieOrigin)> > org.apache.http.impl.client.HttpClientBuilder > setDnsResolver(org.apache.http.conn.DnsResolver)> > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PandaMonkey updated IGNITE-7799: Description: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: was: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. As the JVM only load the classes present first on the classpath and shadow the other duplicate ones with the same names. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient > -- > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 > Project: Ignite > Issue Type: Bug > Components: aws >Affects Versions: 2.5 >Reporter: PandaMonkey >Priority: Major > Fix For: 3.0 > > > Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are > two versions of *org.apache.httpcomponents:httpclient*. Their introduced path > is: > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 > is the direct dependency. By further
[jira] [Commented] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374311#comment-16374311 ] Valentin Kulichenko commented on IGNITE-7799: - I believe Maven will use the one provided explicitly in the POM in this case, not transitive one. Did you actually expirience one of these issues? > Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient > -- > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 > Project: Ignite > Issue Type: Bug > Components: aws >Affects Versions: 2.5 >Reporter: PandaMonkey >Priority: Major > Fix For: 3.0 > > > Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are > two versions of *org.apache.httpcomponents:httpclient*. Their introduced path > is: > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 > is the direct dependency. By further analyzing the source code, we found they > have different features. As the JVM only load the classes present first on > the classpath and shadow the other duplicate ones with the same names. The > dependency conflict problem brings high risks of "*NotClassDefFoundError:*" > or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The > solution is upgrading httpclient from 4.5.1 to 4.5.2.* > > ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml > > ===conflict: > size:2 > > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > *Risk for ClassNotFoundException/NotClassDefFoundError:* > a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: > org.apache.http.client.utils.DateUtils$DateFormatHolder$1 > b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: > org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE > org.apache.http.impl.client.DefaultClientConnectionReuseStrategy > org.apache.http.conn.ssl.DefaultHostnameVerifier$1 > *Risk for NoSuchMethodException/NoSuchMethodError:* > Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > createLocalDomainMap()> > match(org.apache.http.cookie.Cookie,org.apache.http.cookie.CookieOrigin)> > org.apache.http.impl.client.HttpClientBuilder > setDnsResolver(org.apache.http.conn.DnsResolver)> > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7718) Collections.singleton() and Collections.singletonMap() are not properly serialized by binary marshaller
[ https://issues.apache.org/jira/browse/IGNITE-7718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374309#comment-16374309 ] Pavel Vinokurov commented on IGNITE-7718: - [~dpavlov], please check the test results > Collections.singleton() and Collections.singletonMap() are not properly > serialized by binary marshaller > --- > > Key: IGNITE-7718 > URL: https://issues.apache.org/jira/browse/IGNITE-7718 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.3 >Reporter: Pavel Vinokurov >Assignee: Pavel Vinokurov >Priority: Major > > After desialization collections obtained by Collections.singleton() and > Collections.singletonMap() does not return collection of binary objects, but > rather collection of deserialized objects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PandaMonkey updated IGNITE-7799: Description: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. As the JVM only load the classes present first on the classpath and shadow the other duplicate ones with the same names. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. *The solution is upgrading httpclient from 4.5.1 to 4.5.2.* ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: was: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. As the JVM only load the classes present first on the classpath and shadow the other duplicate ones with the same names. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient > -- > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 > Project: Ignite > Issue Type: Bug > Components: aws >Affects Versions: 2.5 >Reporter: PandaMonkey >Priority: Major > Fix For: 3.0 > > > Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are > two versions of *org.apache.httpcomponents:httpclient*. Their introduced path > is: > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > Of them, httpclient:4.5.2 is the transitive dependency,
[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PandaMonkey updated IGNITE-7799: Summary: Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient (was: Dependency Conflict : Conlicting JARs) > Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient > -- > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 > Project: Ignite > Issue Type: Bug > Components: aws >Affects Versions: 2.5 >Reporter: PandaMonkey >Priority: Major > Fix For: 3.0 > > > Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are > two versions of *org.apache.httpcomponents:httpclient*. Their introduced path > is: > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 > is the direct dependency. By further analyzing the source code, we found they > have different features. As the JVM only load the classes present first on > the classpath and shadow the other duplicate ones with the same names. The > dependency conflict problem brings high risks of "*NotClassDefFoundError:*" > or "*NoSuchMethodError*" issues at runtime. Please notice this problem. > > ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml > > ===conflict: > size:2 > > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > *Risk for ClassNotFoundException/NotClassDefFoundError:* > a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: > org.apache.http.client.utils.DateUtils$DateFormatHolder$1 > b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: > org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE > org.apache.http.impl.client.DefaultClientConnectionReuseStrategy > org.apache.http.conn.ssl.DefaultHostnameVerifier$1 > *Risk for NoSuchMethodException/NoSuchMethodError:* > Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > createLocalDomainMap()> > match(org.apache.http.cookie.Cookie,org.apache.http.cookie.CookieOrigin)> > org.apache.http.impl.client.HttpClientBuilder > setDnsResolver(org.apache.http.conn.DnsResolver)> > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PandaMonkey updated IGNITE-7799: Description: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. As the JVM only load the classes present first on the classpath and shadow the other duplicate ones with the same names. The dependency conflict problem brings high risks of "*NotClassDefFoundError:*" or "*NoSuchMethodError*" issues at runtime. Please notice this problem. ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: was: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. As the JVM only load the classes present first on the classpath and shadow the other duplicate ones with the same names. The dependency conflict problem brings high risks of "NoSuchMethodException" or "NoSuchMethodError" issues at runtime. Please notice this problem. ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > Dependency Conflict : Conlicting JARs > - > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 > Project: Ignite > Issue Type: Bug > Components: aws >Affects Versions: 2.5 >Reporter: PandaMonkey >Priority: Major > Fix For: 3.0 > > > Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are > two versions of *org.apache.httpcomponents:httpclient*. Their introduced path > is: > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 > is the direct dependency. By further analyzing the source code, we found they > have different features. As the
[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PandaMonkey updated IGNITE-7799: Description: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of *org.apache.httpcomponents:httpclient*. Their introduced path is: # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile # org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. As the JVM only load the classes present first on the classpath and shadow the other duplicate ones with the same names. The dependency conflict problem brings high risks of "NoSuchMethodException" or "NoSuchMethodError" issues at runtime. Please notice this problem. ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: was: Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of org.apache.httpcomponents:httpclient. Their introduced path is: org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. As the JVM only load the classes present first on the classpath and shadow the other duplicate ones with the same names. The dependency conflict problem brings high risks of "NoSuchMethodException" or "NoSuchMethodError" issues at runtime. Please notice this problem. ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: > Dependency Conflict : Conlicting JARs > - > > Key: IGNITE-7799 > URL: https://issues.apache.org/jira/browse/IGNITE-7799 > Project: Ignite > Issue Type: Bug > Components: aws >Affects Versions: 2.5 >Reporter: PandaMonkey >Priority: Major > Fix For: 3.0 > > > Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are > two versions of *org.apache.httpcomponents:httpclient*. Their introduced path > is: > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile > # > org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile > Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 > is the direct dependency. By further analyzing the source code, we found they > have different features. As the JVM only load the classes
[jira] [Created] (IGNITE-7799) Dependency Conflict : Conlicting JARs
PandaMonkey created IGNITE-7799: --- Summary: Dependency Conflict : Conlicting JARs Key: IGNITE-7799 URL: https://issues.apache.org/jira/browse/IGNITE-7799 Project: Ignite Issue Type: Bug Components: aws Affects Versions: 2.5 Reporter: PandaMonkey Fix For: 3.0 Hi, by analyzing ignite-master\modules\aws\pom.xml, I found that there are two versions of org.apache.httpcomponents:httpclient. Their introduced path is: org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile Of them, httpclient:4.5.2 is the transitive dependency, and httpclient:4.5.1 is the direct dependency. By further analyzing the source code, we found they have different features. As the JVM only load the classes present first on the classpath and shadow the other duplicate ones with the same names. The dependency conflict problem brings high risks of "NoSuchMethodException" or "NoSuchMethodError" issues at runtime. Please notice this problem. ===projectPath->org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT@D:\ws\snapshot\ignite-master\modules\aws\pom.xml ===conflict: size:2 org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->com.amazonaws:aws-java-sdk-core:1.11.75::compile->org.apache.httpcomponents:httpclient:4.5.2::compile org.apache.ignite:ignite-aws:2.5.0-SNAPSHOT::null->org.apache.httpcomponents:httpclient:4.5.1::compile *Risk for ClassNotFoundException/NotClassDefFoundError:* a) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.1: org.apache.http.client.utils.DateUtils$DateFormatHolder$1 b) Classes that only exist in org.apache.httpcomponents:httpclient:4.5.2: org.apache.http.conn.ssl.DefaultHostnameVerifier$TYPE org.apache.http.impl.client.DefaultClientConnectionReuseStrategy org.apache.http.conn.ssl.DefaultHostnameVerifier$1 *Risk for NoSuchMethodException/NoSuchMethodError:* Methods that only exist in org.apache.httpcomponents:httpclient:4.5.2: -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7793) SQL does not work if value has index filed which name equals to affinity key name
[
https://issues.apache.org/jira/browse/IGNITE-7793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Cherkasov updated IGNITE-7793:
--
Priority: Blocker (was: Critical)
> SQL does not work if value has index filed which name equals to affinity key
> name
> -
>
> Key: IGNITE-7793
> URL: https://issues.apache.org/jira/browse/IGNITE-7793
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Priority: Blocker
> Fix For: 2.5
>
>
> SQL does not work if value has index filed which name equals to affinity key
> name:
> {code:java}
> public class AKey {
> @AffinityKeyMapped
> int a;
> public AKey(int a) {
> this.a = a;
> }
> }
> public class AVal {
> @QuerySqlField
> int a;
> public AVal(int a) {
> this.a = a;
> }
> }
> AKey aKey = new AKey(1);
> AVal aVal = new AVal(0);
> IgniteCache cache = ignite.cache("Instrument");
> cache.put(aKey, aVal);
> SqlFieldsQuery query = new SqlFieldsQuery("select * from \"Instrument\".AVal
> it where it.a=?");
> List res = cache.query(query.setArgs(0)).getAll();
> if(res.isEmpty()) {
> System.out.println("! FAILED !!!");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7785) SQL query with COUNT and UNION in sub-query produces JdbcSQLException
[ https://issues.apache.org/jira/browse/IGNITE-7785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374170#comment-16374170 ] Pavel Vinokurov commented on IGNITE-7785: - Another one reproducer with GROUP BY: CREATE TABLE Person (id INTEGER PRIMARY KEY, company_id INTEGER, salary DECIMAL); CREATE TABLE Company (id INTEGER PRIMARY KEY, name VARCHAR); CREATE TABLE Company_Value (id INTEGER PRIMARY KEY, company_id INTEGER, market_value DECIMAL); INSERT INTO Person (id, company_id, salary) VALUES (1, 1, 100), (2, 2, 200), (3, 3, 300); INSERT INTO Company (id, name) VALUES (1, 'n1'), (2, 'n2'), (3, 'n3'); INSERT INTO Company_Value (id, company_id, market_value) VALUES (1, 1, 1), (2, 2, 2), (3, 3, 3); CREATE TABLE Address (id INTEGER PRIMARY KEY, person_id INTEGER, city VARCHAR);INSERT INTO Person (id, company_id, salary) VALUES (1, 1, 100), (2, 2, 200), (3, 3, 300);INSERT INTO Address (id, person_id, city) VALUES (1, 1, 'san francisco'), (2, 2, 'paris'), (3, 3, 'new york');INSERT INTO Company (id, name) VALUES (1, 'n1'), (2, 'n2'), (3, 'n3');INSERT INTO Company_Value (id, company_id, market_value) VALUES (1, 1, 1), (2, 2, 2), (3, 3, 3); SELECT a.idFROM (SELECT p1.id as pid, p1.salary, p1.company_id FROM Person p1 WHERE p1.id = 1 UNION SELECT p2.id as pid, p2.salary, p2.company_id FROM Person p2 WHERE p2.id = 2) p LEFT JOIN Company c ON p.company_id = c.id LEFT JOIN Company_Value cv ON c.id = cv.company_id LEFT JOIN Address a ON a.person_id = p.pid; Caused by: org.h2.jdbc.JdbcSQLException: Column "P__Z2.ID" not found; SQL statement:SELECTC__Z3.ID __C2_0FROM PUBLIC.COMPANY C__Z3 LEFT OUTER JOIN PUBLIC.COMPANY_VALUE CV__Z4 ON C__Z3.ID = CV__Z4.COMPANY_ID LEFT OUTER JOIN PUBLIC.ADDRESS A__Z5 ON A__Z5.PERSON_ID = P__Z2.IDORDER BY 1 [42122-195] > SQL query with COUNT and UNION in sub-query produces JdbcSQLException > - > > Key: IGNITE-7785 > URL: https://issues.apache.org/jira/browse/IGNITE-7785 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.1, 2.3 >Reporter: Pavel Vinokurov >Priority: Major > > SQL initial script: > CREATE TABLE Person(id INTEGER PRIMARY KEY, company_id INTEGER); > CREATE TABLE Company(id INTEGER PRIMARY KEY, name VARCHAR); > INSERT INTO Person(id,company_id) VALUES (1, 1), (2, 2), (3, 3); > INSERT INTO Company(id,name) VALUES (1,'n1'), (2,'n2'), (3,'n3'); > SQL Query: > SELECT count(1) FROM person p > LEFT JOIN (select id from company union select id from company) as c on > c.id=p.company_id > JDBC Exception: > Caused by: org.h2.jdbc.JdbcSQLException: Column "P__Z0.COMPANY_ID" must be in > the GROUP BY list; SQL statement: > SELECT > P__Z0.COMPANY_ID __C0_0, > COUNT(1) __C0_1 > FROM PUBLIC.PERSON P__Z0 [90016-195] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7777) Thin Client lib: Node.js
[ https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374077#comment-16374077 ] Alexey Kosenchuk commented on IGNITE-: -- Yee... we do think about this. Will provide the API for review first, of course. > Thin Client lib: Node.js > > > Key: IGNITE- > URL: https://issues.apache.org/jira/browse/IGNITE- > Project: Ignite > Issue Type: New Feature > Components: thin client >Reporter: Alexey Kosenchuk >Assignee: Alexey Kosenchuk >Priority: Major > > Implement Thin (lightweight) Client lib in Node.js programming language for > Ignite Binary Client Protocol > https://apacheignite.readme.io/docs/binary-client-protocol > Examples of other Thin Clients: > .net > https://github.com/apache/ignite/tree/master/modules/platforms/dotnet/Apache.Ignite.Core/Impl/Client > java > https://github.com/gridgain/apache-ignite/tree/ignite-7421/modules/thinclient > Scope of work > - > Functionality: > Support all operations of the Ignite Binary Client Protocol 2.4. > Support name/password authentication - TBD (not in the protocol yet). > Support optional SSL/TLS communication - TBD (not in the protocol yet). > Support optional failover/reconnect - TBD. > Minimal Node.js version - TBD. > Synch ops emulation - callbacks, or Promises, or asynch/await - TBD. > Examples: > Cover all basic features - Key-value API, SQL, Scan queries, Cluster > configuration/management, Authentication, SSL/TLS. > Tests: > Jasmine tests for all API methods and all basic features. > Simple Jasmine tests to start examples. > How to emulate node failure to test failover/reconnect? - TBD. > Docs: > Auto-generated API spec from comments. JSdoc, or javadoc, or what? - TBD. > Readme for the lib. > Simple instruction to setup/run examples. > Simple instruction to setup/run Jasmine tests. > Docs format - .md in the repo, or dash.readme.io ? - TBD. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
