[jira] [Updated] (IGNITE-18330) Fix javadoc in Transaction#resume(), Transaction#suspend

2023-07-22 Thread bin.yin (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-18330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bin.yin updated IGNITE-18330: - External issue URL: https://github.com/apache/ignite/pull/10604 > Fix javadoc in Transaction#res

[jira] [Commented] (IGNITE-18330) Fix javadoc in Transaction#resume(), Transaction#suspend

2023-07-22 Thread bin.yin (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-18330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17745886#comment-17745886 ] bin.yin commented on IGNITE-18330: -- [~AldoRaine] Hello, I have updated this Jav

[jira] [Comment Edited] (IGNITE-18330) Fix javadoc in Transaction#resume(), Transaction#suspend

2023-07-22 Thread bin.yin (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-18330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17745886#comment-17745886 ] bin.yin edited comment on IGNITE-18330 at 7/22/23 7:4

[jira] [Comment Edited] (IGNITE-18330) Fix javadoc in Transaction#resume(), Transaction#suspend

2023-07-22 Thread bin.yin (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-18330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17745886#comment-17745886 ] bin.yin edited comment on IGNITE-18330 at 7/22/23 7:5

[jira] [Created] (IGNITE-20024) When MySQL is used as the underlying storage, an exception is thrown "Can not set java.time.LocalDateTime field org.apache.ignite.examples.model.Person.createdTime to j

2023-07-22 Thread bin.yin (Jira)
Key: IGNITE-20024 URL: https://issues.apache.org/jira/browse/IGNITE-20024 Project: Ignite Issue Type: Bug Components: persistence Reporter: bin.yin Assignee: bin.yin h3. Question: When I use IgniteCache.get(key)

[jira] [Commented] (IGNITE-20024) When MySQL is used as the underlying storage, an exception is thrown "Can not set java.time.LocalDateTime field org.apache.ignite.examples.model.Person.createdTime to

2023-07-22 Thread bin.yin (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17745898#comment-17745898 ] bin.yin commented on IGNITE-20024: -- [~ivandasch]  I want to modify the def

[jira] [Updated] (IGNITE-20024) When MySQL is used as the underlying storage, an exception is thrown "Can not set java.time.LocalDateTime field org.apache.ignite.examples.model.Person.createdTime to j

2023-07-22 Thread bin.yin (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bin.yin updated IGNITE-20024: - Description: h3. Question: First, I use ??IgniteCache#loadCache?? load from RDBMS. When I use

[jira] [Updated] (IGNITE-20024) When MySQL is used as the underlying storage, an exception is thrown "Can not set java.time.LocalDateTime field org.apache.ignite.examples.model.Person.createdTime to j

2023-07-22 Thread bin.yin (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bin.yin updated IGNITE-20024: - Description: h3. Question: {{First, I use ??IgniteCache#loadCache?? load from RDBMS. When I use

[jira] [Updated] (IGNITE-20024) When MySQL is used as the underlying storage, an exception is thrown "Can not set java.time.LocalDateTime field org.apache.ignite.examples.model.Person.createdTime to j

2023-07-22 Thread bin.yin (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bin.yin updated IGNITE-20024: - Description: h3. Question: {{First, I use `IgniteCache#loadCache` load from RDBMS. When I use

[jira] [Updated] (IGNITE-20024) When MySQL is used as the underlying storage, an exception is thrown "Can not set java.time.LocalDateTime field org.apache.ignite.examples.model.Person.createdTime to j

2023-07-22 Thread bin.yin (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bin.yin updated IGNITE-20024: - Description: h3. Question: {{First, I use `IgniteCache#loadCache` __ load from RDBMS. When I use

[jira] [Updated] (IGNITE-20024) When H2 is used as the underlying storage, an exception is thrown "Can not set java.time.LocalDateTime field org.apache.ignite.examples.model.Person.createdTime to java

2023-07-23 Thread bin.yin (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bin.yin updated IGNITE-20024: - Summary: When H2 is used as the underlying storage, an exception is thrown "Can no

[jira] [Created] (IGNITE-20061) Add SystemProperty for H2Connection#STATEMENT_CACHE_SIZE

2023-07-26 Thread asdfgh19 (Jira)
asdfgh19 created IGNITE-20061: - Summary: Add SystemProperty for H2Connection#STATEMENT_CACHE_SIZE Key: IGNITE-20061 URL: https://issues.apache.org/jira/browse/IGNITE-20061 Project: Ignite Issue

[jira] [Updated] (IGNITE-20150) JDBC port not exposed in docker-compose.yml in Ignite 3

2023-08-03 Thread Aleksandr (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-20150: --- Labels: ignite-3 (was: ) > JDBC port not exposed in docker-compose.yml in Ignit

[jira] [Commented] (IGNITE-20150) JDBC port not exposed in docker-compose.yml in Ignite 3

2023-08-03 Thread Aleksandr (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750695#comment-17750695 ] Aleksandr commented on IGNITE-20150: As a result, the documentation ticket sh

[jira] [Created] (IGNITE-20151) Minor fixes in Ignite 3 public documentation

2023-08-03 Thread Aleksandr (Jira)
Aleksandr created IGNITE-20151: -- Summary: Minor fixes in Ignite 3 public documentation Key: IGNITE-20151 URL: https://issues.apache.org/jira/browse/IGNITE-20151 Project: Ignite Issue Type: Task

[jira] [Assigned] (IGNITE-20150) JDBC port not exposed in docker-compose.yml in Ignite 3

2023-08-03 Thread Aleksandr (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr reassigned IGNITE-20150: -- Assignee: Ivan Zlenko > JDBC port not exposed in docker-compose.yml in Ignit

[jira] [Assigned] (IGNITE-20150) JDBC port not exposed in docker-compose.yml in Ignite 3

2023-08-03 Thread Aleksandr (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr reassigned IGNITE-20150: -- Assignee: (was: Aleksandr) > JDBC port not exposed in docker-compose.yml in Ignit

[jira] [Commented] (IGNITE-20150) JDBC port not exposed in docker-compose.yml in Ignite 3

2023-08-03 Thread Aleksandr (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750796#comment-17750796 ] Aleksandr commented on IGNITE-20150: [~ivan.zlenko] could you create follo

[jira] [Assigned] (IGNITE-20150) JDBC port not exposed in docker-compose.yml in Ignite 3

2023-08-03 Thread Aleksandr (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr reassigned IGNITE-20150: -- Assignee: Aleksandr (was: Ivan Zlenko) > JDBC port not exposed in docker-compose.yml

[jira] [Created] (IGNITE-20158) CLI: cluster/node config update is not user friendly

2023-08-03 Thread Aleksandr (Jira)
Aleksandr created IGNITE-20158: -- Summary: CLI: cluster/node config update is not user friendly Key: IGNITE-20158 URL: https://issues.apache.org/jira/browse/IGNITE-20158 Project: Ignite Issue

[jira] [Updated] (IGNITE-20158) CLI: cluster/node config update is not user friendly

2023-08-07 Thread Aleksandr (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-20158: --- Description: The configuration update process can be painful because of the way CLI parses the

[jira] [Assigned] (IGNITE-19953) Ignite 3 CLI: --verbose twice does not work

2023-08-08 Thread Aleksandr (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-19953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr reassigned IGNITE-19953: -- Assignee: Aleksandr > Ignite 3 CLI: --verbose twice does not w

[jira] [Created] (IGNITE-20179) CLI should provide user-friendly list options

2023-08-08 Thread Aleksandr (Jira)
Aleksandr created IGNITE-20179: -- Summary: CLI should provide user-friendly list options Key: IGNITE-20179 URL: https://issues.apache.org/jira/browse/IGNITE-20179 Project: Ignite Issue Type

[jira] [Updated] (IGNITE-20179) CLI should provide user-friendly list options

2023-08-08 Thread Aleksandr (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-20179: --- Description: We have several command options that should accept a list of strings, for example

[jira] [Updated] (IGNITE-20179) CLI should provide user-friendly list options

2023-08-08 Thread Aleksandr (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-20179: --- Description: We have several command options that should accept a list of strings, for example

[jira] [Updated] (IGNITE-20179) CLI should provide user-friendly list options

2023-08-08 Thread Aleksandr (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-20179: --- Description: We have several command options that should accept a list of strings, for example

[jira] [Created] (IGNITE-20186) [Ignite Website] Add Upcoming Events

2023-08-09 Thread Evgenia (Jira)
Evgenia created IGNITE-20186: Summary: [Ignite Website] Add Upcoming Events Key: IGNITE-20186 URL: https://issues.apache.org/jira/browse/IGNITE-20186 Project: Ignite Issue Type: Task

[jira] [Commented] (IGNITE-20082) Fix ODBC package

2023-08-17 Thread Aleksandr (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755450#comment-17755450 ] Aleksandr commented on IGNITE-20082: Thank you for the contribution, merged

[jira] [Created] (IGNITE-20254) Refactor CLI exception handling

2023-08-18 Thread Aleksandr (Jira)
Aleksandr created IGNITE-20254: -- Summary: Refactor CLI exception handling Key: IGNITE-20254 URL: https://issues.apache.org/jira/browse/IGNITE-20254 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-20286) Information about REST port disappeared from logs

2023-08-25 Thread Igor (Jira)
Igor created IGNITE-20286: - Summary: Information about REST port disappeared from logs Key: IGNITE-20286 URL: https://issues.apache.org/jira/browse/IGNITE-20286 Project: Ignite Issue Type: Bug

[jira] [Updated] (IGNITE-20286) Information about REST port disappeared from logs

2023-08-25 Thread Igor (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor updated IGNITE-20286: -- Description: The information about taken REST port is disappeared from logs. Previously the string was

[jira] [Updated] (IGNITE-20286) Information about REST port disappeared from logs

2023-08-25 Thread Igor (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor updated IGNITE-20286: -- Description: The information about taken REST port is disappeared from logs. Previously the string was

[jira] [Resolved] (IGNITE-18330) Fix javadoc in Transaction#resume(), Transaction#suspend

2023-08-27 Thread bin.yin (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-18330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bin.yin resolved IGNITE-18330. -- Resolution: Fixed > Fix javadoc in Transaction#resume(), Transaction#susp

[jira] [Reopened] (IGNITE-18330) Fix javadoc in Transaction#resume(), Transaction#suspend

2023-08-27 Thread bin.yin (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-18330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bin.yin reopened IGNITE-18330: -- > Fix javadoc in Transaction#resume(), Transaction#susp

[jira] [Created] (IGNITE-20351) Log responce error in Rest test

2023-09-05 Thread Aleksandr (Jira)
Aleksandr created IGNITE-20351: -- Summary: Log responce error in Rest test Key: IGNITE-20351 URL: https://issues.apache.org/jira/browse/IGNITE-20351 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-20552) The example code is giving a NotSerializableException

2023-10-03 Thread yafengshi (Jira)
yafengshi created IGNITE-20552: -- Summary: The example code is giving a NotSerializableException Key: IGNITE-20552 URL: https://issues.apache.org/jira/browse/IGNITE-20552 Project: Ignite Issue

[jira] [Resolved] (IGNITE-20552) The example code is giving a NotSerializableException

2023-10-03 Thread yafengshi (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yafengshi resolved IGNITE-20552. Resolution: Fixed > The example code is giving a NotSerializableExcept

[jira] [Reopened] (IGNITE-20552) The example code is giving a NotSerializableException

2023-10-03 Thread yafengshi (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yafengshi reopened IGNITE-20552: > The example code is giving a NotSerializableExcept

[jira] [Updated] (IGNITE-20552) The example code is giving a NotSerializableException

2023-10-03 Thread yafengshi (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yafengshi updated IGNITE-20552: --- Labels: newbie (was: bugfix) > The example code is giving a NotSerializableExcept

[jira] [Assigned] (IGNITE-20552) The example code is giving a NotSerializableException

2023-10-05 Thread yafengshi (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yafengshi reassigned IGNITE-20552: -- Assignee: yafengshi > The example code is giving a NotSerializableExcept

[jira] [Resolved] (IGNITE-20552) The example code is giving a NotSerializableException

2023-10-05 Thread yafengshi (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yafengshi resolved IGNITE-20552. Resolution: Fixed > The example code is giving a NotSerializableExcept

[jira] [Reopened] (IGNITE-20552) The example code is giving a NotSerializableException

2023-10-05 Thread yafengshi (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yafengshi reopened IGNITE-20552: Ignite Flags: (was: Docs Required,Release Notes Required) > The example code is givin

[jira] [Created] (IGNITE-20591) Connect to another cluster does not work from interactive mode

2023-10-06 Thread Aleksandr (Jira)
Aleksandr created IGNITE-20591: -- Summary: Connect to another cluster does not work from interactive mode Key: IGNITE-20591 URL: https://issues.apache.org/jira/browse/IGNITE-20591 Project: Ignite

[jira] [Updated] (IGNITE-20591) Connect to another cluster does not work from interactive mode

2023-10-06 Thread Aleksandr (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-20591: --- Description: I had two nodes (10300 and 10400), initialized one node, and wanted to initialize the

[jira] [Updated] (IGNITE-20552) The example code is giving a NotSerializableException

2023-10-09 Thread yafengshi (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yafengshi updated IGNITE-20552: --- Reviewer: (was: yafengshi) > The example code is giving a NotSerializableExcept

[jira] [Commented] (IGNITE-20552) The example code is giving a NotSerializableException

2023-10-09 Thread yafengshi (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17773159#comment-17773159 ] yafengshi commented on IGNITE-20552: [~aonikolaev] , Please review my cha

[jira] [Updated] (IGNITE-20552) The example code is giving a NotSerializableException

2023-10-09 Thread yafengshi (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yafengshi updated IGNITE-20552: --- Reviewer: Aleksandr Nikolaev > The example code is giving a NotSerializableExcept

[jira] [Created] (IGNITE-7338) can get value by entry.getValue but cann't get value by entry.getKey

2017-12-28 Thread dean (JIRA)
dean created IGNITE-7338: Summary: can get value by entry.getValue but cann't get value by entry.getKey Key: IGNITE-7338 URL: https://issues.apache.org/jira/browse/IGNITE-7338 Project: Ignite

[jira] [Commented] (IGNITE-7338) can get value by entry.getValue but cann't get value by entry.getKey

2017-12-28 Thread dean (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16305873#comment-16305873 ] dean commented on IGNITE-7338: -- if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_ch

[jira] [Comment Edited] (IGNITE-7338) can get value by entry.getValue but cann't get value by entry.getKey

2017-12-28 Thread dean (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16305873#comment-16305873 ] dean edited comment on IGNITE-7338 at 12/29/17 1:04 AM:

[jira] [Comment Edited] (IGNITE-7338) can get value by entry.getValue but cann't get value by entry.getKey

2017-12-28 Thread dean (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16305873#comment-16305873 ] dean edited comment on IGNITE-7338 at 12/29/17 1:05 AM:

[jira] [Comment Edited] (IGNITE-7338) can get value by entry.getValue but cann't get value by entry.getKey

2017-12-28 Thread dean (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16305873#comment-16305873 ] dean edited comment on IGNITE-7338 at 12/29/17 1:06 AM:

[jira] [Updated] (IGNITE-7338) can get value by entry.getValue but cann't get value by cache.get(entry.getKey)

2017-12-28 Thread dean (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dean updated IGNITE-7338: - Summary: can get value by entry.getValue but cann't get value by cache.get(entry.getKey) (was: can get val

[jira] [Updated] (IGNITE-7338) can get value by entry.getValue but cann't get value by cache.get(entry.getKey)

2017-12-28 Thread dean (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dean updated IGNITE-7338: - Description: if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_charge_rule")){ CcbCdrCha

[jira] [Updated] (IGNITE-7338) can get value by entry.getValue but cann't get value by cache.get(entry.getKey)

2017-12-28 Thread dean (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dean updated IGNITE-7338: - Description: if(cacheName.equalsIgnoreCase("tariff-ccb_cdr_charge_rule")){ CcbCdrCha

[jira] [Updated] (IGNITE-7338) can get value by entry.getValue but cann't get value by cache.get(entry.getKey)

2017-12-28 Thread dean (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dean updated IGNITE-7338: - Description: bossapp@Linux-Power-NB-AltiDB2-XT:/home/bossapp6$java -version java version "1.7.0" J

[jira] [Comment Edited] (IGNITE-3653) P2P doesn't work for remote filter and filter factory.

2018-01-03 Thread tonysze (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16310748#comment-16310748 ] tonysze edited comment on IGNITE-3653 at 1/4/18 5:32 AM: -

[jira] [Commented] (IGNITE-3653) P2P doesn't work for remote filter and filter factory.

2018-01-03 Thread tonysze (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16310748#comment-16310748 ] tonysze commented on IGNITE-3653: - In Ignite 2.3.0, I have added the following lin

[jira] [Comment Edited] (IGNITE-3653) P2P doesn't work for remote filter and filter factory.

2018-01-03 Thread tonysze (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16310748#comment-16310748 ] tonysze edited comment on IGNITE-3653 at 1/4/18 5:33 AM: -

[jira] [Comment Edited] (IGNITE-3653) P2P doesn't work for remote filter and filter factory.

2018-01-03 Thread tonysze (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-3653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16310748#comment-16310748 ] tonysze edited comment on IGNITE-3653 at 1/4/18 5:33 AM: -

[jira] [Created] (IGNITE-7402) Add ODBC security support

2018-01-12 Thread Blackfield (JIRA)
Blackfield created IGNITE-7402: -- Summary: Add ODBC security support Key: IGNITE-7402 URL: https://issues.apache.org/jira/browse/IGNITE-7402 Project: Ignite Issue Type: Improvement

[jira] [Commented] (IGNITE-7338) can get value by entry.getValue but cann't get value by cache.get(entry.getKey)

2018-01-24 Thread dean (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16337470#comment-16337470 ] dean commented on IGNITE-7338: -- @[~andrey-kuznetsov]  i have resolve this proble

[jira] [Resolved] (IGNITE-7338) can get value by entry.getValue but cann't get value by cache.get(entry.getKey)

2018-01-24 Thread dean (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dean resolved IGNITE-7338. -- Resolution: Fixed > can get value by entry.getValue but cann't get value by > cache.get(e

[jira] [Created] (IGNITE-7620) Not able to run query in Ignite YARN

2018-02-04 Thread Puviarasu (JIRA)
Puviarasu created IGNITE-7620: - Summary: Not able to run query in Ignite YARN Key: IGNITE-7620 URL: https://issues.apache.org/jira/browse/IGNITE-7620 Project: Ignite Issue Type: Bug Affects

[jira] [Updated] (IGNITE-7620) Not able to run query in Ignite YARN

2018-02-04 Thread Puviarasu (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Puviarasu updated IGNITE-7620: -- Description: Not able to run query in Ignite YARN deployment.  Ignite version 2.3.0 Failed to run

[jira] [Created] (IGNITE-7799) Dependency Conflict : Conlicting JARs

2018-02-23 Thread PandaMonkey (JIRA)
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

[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs

2018-02-23 Thread PandaMonkey (JIRA)
[ 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

[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs

2018-02-23 Thread PandaMonkey (JIRA)
[ 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

[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient

2018-02-23 Thread PandaMonkey (JIRA)
[ 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

[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient

2018-02-23 Thread PandaMonkey (JIRA)
[ 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

[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient

2018-02-23 Thread PandaMonkey (JIRA)
[ 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

[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient

2018-02-23 Thread PandaMonkey (JIRA)
[ 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

[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient

2018-02-23 Thread PandaMonkey (JIRA)
[ 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 J

[jira] [Commented] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient

2018-02-23 Thread PandaMonkey (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374332#comment-16374332 ] PandaMonkey commented on IGNITE-7799: - [~vkulichenko], thx for your quick reply

[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient

2018-02-23 Thread PandaMonkey (JIRA)
[ 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

[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient

2018-02-23 Thread PandaMonkey (JIRA)
[ 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

[jira] [Commented] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient

2018-02-23 Thread PandaMonkey (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374366#comment-16374366 ] PandaMonkey commented on IGNITE-7799: - [~vkulichenko] I accept that you close

[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient

2018-02-23 Thread PandaMonkey (JIRA)
[ 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

[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient

2018-02-23 Thread PandaMonkey (JIRA)
[ 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

[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient

2018-02-23 Thread PandaMonkey (JIRA)
[ 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

[jira] [Updated] (IGNITE-7799) Dependency Conflict : Conlicting JARs org.apache.httpcomponents:httpclient

2018-02-23 Thread PandaMonkey (JIRA)
[ 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

[jira] [Created] (IGNITE-7804) when new node join cluster,rebalance communication with demand and supply message is very slow

2018-02-23 Thread dean (JIRA)
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

[jira] [Commented] (IGNITE-7804) when new node join cluster,rebalance communication with demand and supply message is very slow

2018-02-24 Thread dean (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16375392#comment-16375392 ] dean commented on IGNITE-7804: -- h5. supply node infos: ignite-server-14043-2018-02-

[jira] [Issue Comment Deleted] (IGNITE-7804) when new node join cluster,rebalance communication with demand and supply message is very slow

2018-02-24 Thread dean (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dean updated IGNITE-7804: - Comment: was deleted (was: h5. supply node infos: ignite-server-14043-2018-02-12.1.log:2018-02-12 10:10:09,339

[jira] [Updated] (IGNITE-7804) when new node join cluster,rebalance communication with demand and supply message is very slow

2018-02-24 Thread dean (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dean updated IGNITE-7804: - Description: h5. supply node infos: ignite-server-14043-2018-02-12.1.log:2018-02-12 10:10:09,339 INFO sys

[jira] [Updated] (IGNITE-7804) when new node join cluster,rebalance communication with demand and supply message is very slow

2018-02-24 Thread dean (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dean updated IGNITE-7804: - Description: h5. supply node infos: ignite-server-14043-2018-02-12.1.log:2018-02-12 10:10:09,339 INFO sys

[jira] [Updated] (IGNITE-7804) when new node join cluster,rebalance communication with demand and supply message is very slow

2018-02-24 Thread dean (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-7804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dean updated IGNITE-7804: - Description: h5. supply node infos: ignite-server-14043-2018-02-12.1.log:2018-02-12 10:10:09,339 INFO sys

[jira] [Created] (IGNITE-7850) Download page must link to KEYS and contain verification details

2018-02-28 Thread Sebb (JIRA)
Sebb created IGNITE-7850: Summary: Download page must link to KEYS and contain verification details Key: IGNITE-7850 URL: https://issues.apache.org/jira/browse/IGNITE-7850 Project: Ignite Issue

[jira] [Created] (IGNITE-7977) Download page mirror choice is buried

2018-03-16 Thread Sebb (JIRA)
Sebb created IGNITE-7977: Summary: Download page mirror choice is buried Key: IGNITE-7977 URL: https://issues.apache.org/jira/browse/IGNITE-7977 Project: Ignite Issue Type: Improvement

[jira] [Commented] (IGNITE-6287) DDL Support for WebConsole

2018-03-29 Thread Stan (JIRA)
[ https://issues.apache.org/jira/browse/IGNITE-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420160#comment-16420160 ] Stan commented on IGNITE-6287: -- Not sure where else to post this, so posting it here. 

[jira] [Created] (IGNITE-20615) SQL queries by ODBC throws exceptions

2023-10-10 Thread Igor (Jira)
Igor created IGNITE-20615: - Summary: SQL queries by ODBC throws exceptions Key: IGNITE-20615 URL: https://issues.apache.org/jira/browse/IGNITE-20615 Project: Ignite Issue Type: Bug

[jira] [Updated] (IGNITE-20615) SQL queries by ODBC throws exceptions

2023-10-11 Thread Igor (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor updated IGNITE-20615: -- Labels: ignite-3 (was: ) > SQL queries by ODBC throws excepti

[jira] [Resolved] (IGNITE-20615) SQL queries by ODBC throws exceptions

2023-10-11 Thread Igor (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor resolved IGNITE-20615. --- Resolution: Not A Problem Pyodbc tries to get metadata about non executed query - this feature is not yet

[jira] [Created] (IGNITE-20625) SELECT MIN(column), MAX(column) by ODBC throws exceptions

2023-10-11 Thread Igor (Jira)
Igor created IGNITE-20625: - Summary: SELECT MIN(column), MAX(column) by ODBC throws exceptions Key: IGNITE-20625 URL: https://issues.apache.org/jira/browse/IGNITE-20625 Project: Ignite Issue Type

[jira] [Updated] (IGNITE-20625) SELECT MIN(column), MAX(column) by ODBC throws exceptions

2023-10-11 Thread Igor (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor updated IGNITE-20625: -- Description: h3. Steps to reproduce: # Connect to Ignite using ODBC driver (Python). # Execute separate

[jira] [Updated] (IGNITE-20625) SELECT MIN(column), MAX(column) by ODBC throws exception

2023-10-11 Thread Igor (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor updated IGNITE-20625: -- Summary: SELECT MIN(column), MAX(column) by ODBC throws exception (was: SELECT MIN(column), MAX(column) by

[jira] [Created] (IGNITE-20639) Remove portRange from network configuration

2023-10-12 Thread Aleksandr (Jira)
Aleksandr created IGNITE-20639: -- Summary: Remove portRange from network configuration Key: IGNITE-20639 URL: https://issues.apache.org/jira/browse/IGNITE-20639 Project: Ignite Issue Type: Task

[jira] [Commented] (IGNITE-20512) REST API: Remove port range

2023-10-12 Thread Aleksandr (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774583#comment-17774583 ] Aleksandr commented on IGNITE-20512: Hi, [~ptupitsyn]. Can you review th

[jira] [Updated] (IGNITE-20648) Can not init cluster with 21 java

2023-10-13 Thread Aleksandr (Jira)
[ https://issues.apache.org/jira/browse/IGNITE-20648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr updated IGNITE-20648: --- Description: To reproduce the issue: 1) build packages with 11 java 2) start node with 21 java 3

[jira] [Created] (IGNITE-20648) Can not init cluster with 21 java

2023-10-13 Thread Aleksandr (Jira)
Aleksandr created IGNITE-20648: -- Summary: Can not init cluster with 21 java Key: IGNITE-20648 URL: https://issues.apache.org/jira/browse/IGNITE-20648 Project: Ignite Issue Type: Bug

<    5   6   7   8   9   10   11   12   13   14   >