[jira] [Assigned] (IGNITE-8115) Add a warning on local node startup if the node is not in Baseline
[ https://issues.apache.org/jira/browse/IGNITE-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Singh reassigned IGNITE-8115: --- Assignee: (was: Suraj Singh) > Add a warning on local node startup if the node is not in Baseline > -- > > Key: IGNITE-8115 > URL: https://issues.apache.org/jira/browse/IGNITE-8115 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Priority: Major > Labels: newbie > > The message should contain instructions on how to add the node to baseline. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-5258) CPP: It should be possible to set timeout for SQL query in C++
[
https://issues.apache.org/jira/browse/IGNITE-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suraj Singh reassigned IGNITE-5258:
---
Assignee: (was: Suraj Singh)
> CPP: It should be possible to set timeout for SQL query in C++
> --
>
> Key: IGNITE-5258
> URL: https://issues.apache.org/jira/browse/IGNITE-5258
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 2.0
>Reporter: Igor Sapego
>Priority: Major
> Labels: cpp, newbie
>
> There is {{setTimeout}} and {{getTimeout}} calls for Java queries. Need to
> implement the same mechanism in C++.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11312) JDBC: Thin driver doesn't reports incorrect property names
[ https://issues.apache.org/jira/browse/IGNITE-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16844989#comment-16844989 ] Suraj Singh commented on IGNITE-11312: -- Hi [~slukyanov], Could you please have a look into the last correspondence? Thanks! > JDBC: Thin driver doesn't reports incorrect property names > -- > > Key: IGNITE-11312 > URL: https://issues.apache.org/jira/browse/IGNITE-11312 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Stanislav Lukyanov >Assignee: Suraj Singh >Priority: Major > Labels: newbie > > JDBC driver reports the properties it supports via getPropertyInfo method. It > currently reports the property names as simple strings, like > "enforceJoinOrder". However, when the properties are processed on connect > they are looked up with prefix "ignite.jdbc", e.g. > "ignite.jdbc.enforceJoinOrder". > Because of this UI tools like DBeaver can't properly pass the properties to > Ignite. For example, when "enforceJoinOrder" is set to true in "Connection > settings" -> "Driver properties" menu of DBeaver it has no effect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8115) Add a warning on local node startup if the node is not in Baseline
[ https://issues.apache.org/jira/browse/IGNITE-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Singh reassigned IGNITE-8115: --- Assignee: Suraj Singh > Add a warning on local node startup if the node is not in Baseline > -- > > Key: IGNITE-8115 > URL: https://issues.apache.org/jira/browse/IGNITE-8115 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Suraj Singh >Priority: Major > Labels: newbie > > The message should contain instructions on how to add the node to baseline. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5258) CPP: It should be possible to set timeout for SQL query in C++
[
https://issues.apache.org/jira/browse/IGNITE-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16843373#comment-16843373
]
Suraj Singh commented on IGNITE-5258:
-
Hi [~isapego], I am further looking into this issue, and let you know about any
finding I will have. Thanks!
> CPP: It should be possible to set timeout for SQL query in C++
> --
>
> Key: IGNITE-5258
> URL: https://issues.apache.org/jira/browse/IGNITE-5258
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 2.0
>Reporter: Igor Sapego
>Priority: Major
> Labels: cpp, newbie
>
> There is {{setTimeout}} and {{getTimeout}} calls for Java queries. Need to
> implement the same mechanism in C++.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-5258) CPP: It should be possible to set timeout for SQL query in C++
[
https://issues.apache.org/jira/browse/IGNITE-5258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Suraj Singh reassigned IGNITE-5258:
---
Assignee: Suraj Singh
> CPP: It should be possible to set timeout for SQL query in C++
> --
>
> Key: IGNITE-5258
> URL: https://issues.apache.org/jira/browse/IGNITE-5258
> Project: Ignite
> Issue Type: Task
> Components: platforms
>Affects Versions: 2.0
>Reporter: Igor Sapego
>Assignee: Suraj Singh
>Priority: Major
> Labels: cpp, newbie
>
> There is {{setTimeout}} and {{getTimeout}} calls for Java queries. Need to
> implement the same mechanism in C++.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10223) Affinity methods should return List instead of Collection
[ https://issues.apache.org/jira/browse/IGNITE-10223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Singh reassigned IGNITE-10223: Assignee: Suraj Singh > Affinity methods should return List instead of Collection > - > > Key: IGNITE-10223 > URL: https://issues.apache.org/jira/browse/IGNITE-10223 > Project: Ignite > Issue Type: Bug >Reporter: Stanislav Lukyanov >Assignee: Suraj Singh >Priority: Minor > Labels: newbie > > Methods of class Affinity should return List instead of Collection when order > of nodes matters. > The following methods are supposed to always return a collection with primary > node preceding backups: > Affinity::mapPartitionToPrimaryAndBackups > Affinity::mapKeyToPrimaryAndBackups > The return type for both methods is Collection. The Javadocs > say: "Note that primary node is always first in the returned collection". > In general, the notion of "order" and "first element" is not defined for a > Collection (we could play with iterators, but its awkward from both code and > logic perspective). It makes more sense for this methods to return List > instead. > The task is to introduce List equivalents of these methods. It would also be > nice to check if other APIs have similar issues. > The tricky part is compatibility. > Changing return type from Collection to List is source compatible (meaning > the old client code will compile with the new method), but not binary > compatible (meaning the already compiled client code will break because the > signature has changed). > A compatible solution would be to > - deprecate the existing methods > - add methods with different names, like mapPartitionToPrimaryAndBackups*List* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8115) Add a warning on local node startup if the node is not in Baseline
[ https://issues.apache.org/jira/browse/IGNITE-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16843363#comment-16843363 ] Suraj Singh commented on IGNITE-8115: - Hi [~agoncharuk] , I can pick up this task, provided I have enough information to work upon this. some small reference(s) to which component/file to look into? I am quite new to Ignite. Thanks! > Add a warning on local node startup if the node is not in Baseline > -- > > Key: IGNITE-8115 > URL: https://issues.apache.org/jira/browse/IGNITE-8115 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Priority: Major > Labels: newbie > > The message should contain instructions on how to add the node to baseline. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11312) JDBC: Thin driver doesn't reports incorrect property names
[ https://issues.apache.org/jira/browse/IGNITE-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16842319#comment-16842319 ] Suraj Singh commented on IGNITE-11312: -- Hi there Stanislav, I had gone through the code base and understood your problem. To resolve this issue, Is your ask is to write documentation highlighting this issue by enforcing the person to add _ignite.jdbc_ before similar things or to make some code change to fix it? Thanks, Suraj > JDBC: Thin driver doesn't reports incorrect property names > -- > > Key: IGNITE-11312 > URL: https://issues.apache.org/jira/browse/IGNITE-11312 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Stanislav Lukyanov >Assignee: Suraj Singh >Priority: Major > Labels: newbie > > JDBC driver reports the properties it supports via getPropertyInfo method. It > currently reports the property names as simple strings, like > "enforceJoinOrder". However, when the properties are processed on connect > they are looked up with prefix "ignite.jdbc", e.g. > "ignite.jdbc.enforceJoinOrder". > Because of this UI tools like DBeaver can't properly pass the properties to > Ignite. For example, when "enforceJoinOrder" is set to true in "Connection > settings" -> "Driver properties" menu of DBeaver it has no effect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11312) JDBC: Thin driver doesn't reports incorrect property names
[ https://issues.apache.org/jira/browse/IGNITE-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16842314#comment-16842314 ] Suraj Singh commented on IGNITE-11312: -- _getPropertyInfo_ is present at two places: 1. IgniteJdbcDriver 2. IgniteJdbcThinDriver As the question is raised regarding Thin driver. Therefore, looking into *org/apache/ignite/IgniteJdbcThinDriver.java* file. > JDBC: Thin driver doesn't reports incorrect property names > -- > > Key: IGNITE-11312 > URL: https://issues.apache.org/jira/browse/IGNITE-11312 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Stanislav Lukyanov >Assignee: Suraj Singh >Priority: Major > Labels: newbie > > JDBC driver reports the properties it supports via getPropertyInfo method. It > currently reports the property names as simple strings, like > "enforceJoinOrder". However, when the properties are processed on connect > they are looked up with prefix "ignite.jdbc", e.g. > "ignite.jdbc.enforceJoinOrder". > Because of this UI tools like DBeaver can't properly pass the properties to > Ignite. For example, when "enforceJoinOrder" is set to true in "Connection > settings" -> "Driver properties" menu of DBeaver it has no effect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11312) JDBC: Thin driver doesn't reports incorrect property names
[ https://issues.apache.org/jira/browse/IGNITE-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suraj Singh reassigned IGNITE-11312: Assignee: Suraj Singh > JDBC: Thin driver doesn't reports incorrect property names > -- > > Key: IGNITE-11312 > URL: https://issues.apache.org/jira/browse/IGNITE-11312 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Stanislav Lukyanov >Assignee: Suraj Singh >Priority: Major > Labels: newbie > > JDBC driver reports the properties it supports via getPropertyInfo method. It > currently reports the property names as simple strings, like > "enforceJoinOrder". However, when the properties are processed on connect > they are looked up with prefix "ignite.jdbc", e.g. > "ignite.jdbc.enforceJoinOrder". > Because of this UI tools like DBeaver can't properly pass the properties to > Ignite. For example, when "enforceJoinOrder" is set to true in "Connection > settings" -> "Driver properties" menu of DBeaver it has no effect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11312) JDBC: Thin driver doesn't reports incorrect property names
[ https://issues.apache.org/jira/browse/IGNITE-11312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783032#comment-16783032 ] Suraj Singh commented on IGNITE-11312: -- Can anyone assign this task to me? > JDBC: Thin driver doesn't reports incorrect property names > -- > > Key: IGNITE-11312 > URL: https://issues.apache.org/jira/browse/IGNITE-11312 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Stanislav Lukyanov >Priority: Major > Labels: newbie > > JDBC driver reports the properties it supports via getPropertyInfo method. It > currently reports the property names as simple strings, like > "enforceJoinOrder". However, when the properties are processed on connect > they are looked up with prefix "ignite.jdbc", e.g. > "ignite.jdbc.enforceJoinOrder". > Because of this UI tools like DBeaver can't properly pass the properties to > Ignite. For example, when "enforceJoinOrder" is set to true in "Connection > settings" -> "Driver properties" menu of DBeaver it has no effect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
