[jira] [Commented] (IGNITE-11309) JDBC Thin: add flag or property to disable best effort affinity
[
https://issues.apache.org/jira/browse/IGNITE-11309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812061#comment-16812061
]
Ignite TC Bot commented on IGNITE-11309:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3514961buildTypeId=IgniteTests24Java8_RunAll]
> JDBC Thin: add flag or property to disable best effort affinity
> ---
>
> Key: IGNITE-11309
> URL: https://issues.apache.org/jira/browse/IGNITE-11309
> Project: Ignite
> Issue Type: Task
> Components: jdbc
>Affects Versions: 2.8
>Reporter: Alexander Lapin
>Assignee: Alexander Lapin
>Priority: Major
> Labels: iep-23
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It's necessary to have an ability to disable best effort affinity among thin
> clients including thin jdbc client.
> It's not obvious whether it should be flag in connection string, app
> properties or some other place, so research required.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-1204) Cluster Discovery via Consul
[
https://issues.apache.org/jira/browse/IGNITE-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16812000#comment-16812000
]
Saikat Maitra commented on IGNITE-1204:
---
[~roman_s] [~raulvk]
I am looking into this issue and found something similar ignite consul cluster
discovery client here
[https://github.com/andrea-zanetti/ignite-consul]
This library depends on consul orbitz client
[https://github.com/rickfast/consul-client]
I wanted to connect to understand if it is something we can use to build the
consul discovery module?
Regards,
Saikat
> Cluster Discovery via Consul
>
>
> Key: IGNITE-1204
> URL: https://issues.apache.org/jira/browse/IGNITE-1204
> Project: Ignite
> Issue Type: New Feature
> Components: general
>Reporter: Raúl Kripalani
>Assignee: Saikat Maitra
>Priority: Major
> Labels: discovery
>
> According to [their website|https://www.consul.io/]:
> {quote}
> * Consul makes it simple for services to register themselves and to discover
> other services via a DNS or HTTP interface.
> * Pairing service discovery with health checking prevents routing requests to
> unhealthy hosts and enables services to easily provide circuit breakers.
> * Consul scales to multiple datacenters out of the box with no complicated
> configuration. Look up services in other datacenters, or keep the request
> local.
> * Flexible key/value store for dynamic configuration, feature flagging,
> coordination, leader election and more. Long poll for near-instant
> notification of configuration changes.
> {quote}
> It would be nice to provide cluster discovery via Consul.
> Consul itself is MPL v2 licensed. According to [this ASF
> reference|https://www.apache.org/legal/resolved.html#category-b], this is a
> Category B license meaning that it's not viral by nature but it requires some
> degree of reciprocity. We don't really care much about this, because we won't
> be packaging Consul obviously.
> Moreover, there's a [client on GitHub|https://github.com/Ecwid/consul-api]
> that's ASLv2. Worse comes to worst, we could just invoke the HTTP API
> directly with no dependencies.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11563) DELETE WHERE does not work in prepared statements
[
https://issues.apache.org/jira/browse/IGNITE-11563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811995#comment-16811995
]
Pavel Kuznetsov commented on IGNITE-11563:
--
nb: for the query
{code}
DELETE FROM TEST_TABLE WHERE ID = ? AND VALUE = 'this row should be deleted'
{code}
Fast delete is not used, but it should.
> DELETE WHERE does not work in prepared statements
> -
>
> Key: IGNITE-11563
> URL: https://issues.apache.org/jira/browse/IGNITE-11563
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Stefan
>Assignee: Pavel Kuznetsov
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> With SQL I cannot delete a row using a prepared statement. The following
> statement is simply ignored:
> {{DELETE}} {{FROM}} {{AnyTable WHERE}} {{id = ?}}
> This happens with JDBC-Thin and with ODBC so I suspect that the cluster gets
> the correct data but handles it wrong. By adding an always-true-condition it
> works as expected:
> {{DELETE}} {{FROM}} {{AnyTable WHERE}} {{id = id AND}} {{id = ?}}
> I tested with a very simple table that was created with:
> {{CREATE TABLE testtable (}}
> {{ "ID" NUMBER(19,0),}}
> {{ "VALUE" VARCHAR2(255 CHAR),}}
> {{ PRIMARY KEY (ID)}}
> {{) WITH "template=replicated,cache_name=testtable"}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10654) Report in case of creating index with already existing fields collection.
[
https://issues.apache.org/jira/browse/IGNITE-10654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811883#comment-16811883
]
Ignite TC Bot commented on IGNITE-10654:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 3{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3526226]]
* IgniteBinaryObjectsCacheTestSuite3:
IgniteCacheGroupsTest.testEntriesTtlAtomicReplicated - 0,0% fails in last 162
master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3526276buildTypeId=IgniteTests24Java8_RunAll]
> Report in case of creating index with already existing fields collection.
> -
>
> Key: IGNITE-10654
> URL: https://issues.apache.org/jira/browse/IGNITE-10654
> Project: Ignite
> Issue Type: Improvement
> Components: sql
>Affects Versions: 2.7
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Report in log if new index creating with already existing fields collection.
> for example, need to log warn here:
> {code:java}
> cache.query(new SqlFieldsQuery("create index \"idx1\" on Val(keyStr,
> keyLong)"));
> cache.query(new SqlFieldsQuery("create index \"idx3\" on Val(keyStr,
> keyLong)"));
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11694) Add documentation for SqlFieldsQuery.updateBatchSize into thin clients docs
Taras Ledkov created IGNITE-11694:
-
Summary: Add documentation for SqlFieldsQuery.updateBatchSize into
thin clients docs
Key: IGNITE-11694
URL: https://issues.apache.org/jira/browse/IGNITE-11694
Project: Ignite
Issue Type: Task
Components: documentation
Affects Versions: 2.7
Reporter: Taras Ledkov
Fix For: 2.8
The property {{SqlFieldsQuery.updateBatchSize}} is introduced by the patch
IGNITE-11499.
ODBC, thin JDBC, thin client documentation should be changed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11693) Add support SqlFieldsQuery.updateBatchSize for ODBC client.
Taras Ledkov created IGNITE-11693:
-
Summary: Add support SqlFieldsQuery.updateBatchSize for ODBC
client.
Key: IGNITE-11693
URL: https://issues.apache.org/jira/browse/IGNITE-11693
Project: Ignite
Issue Type: Task
Components: odbc
Affects Versions: 2.7
Reporter: Taras Ledkov
Fix For: 2.8
Add support {{SqlFieldsQuery.updateBatchSize}} for ODBC client.
The property {{SqlFieldsQuery.updateBatchSize}} is introduced by the patch
IGNITE-11499.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11692) Add support SqlFieldsQuery.updateBatchSize for thin client protocol and java thin client
Taras Ledkov created IGNITE-11692:
-
Summary: Add support SqlFieldsQuery.updateBatchSize for thin
client protocol and java thin client
Key: IGNITE-11692
URL: https://issues.apache.org/jira/browse/IGNITE-11692
Project: Ignite
Issue Type: Task
Components: thin client
Affects Versions: 2.7
Reporter: Taras Ledkov
Fix For: 2.8
Add support {{SqlFieldsQuery.updateBatchSize}} for thin client protocol and
java thin client.
The property {{SqlFieldsQuery.updateBatchSize}} is introduced by the patch
IGNITE-11499.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7101) .NET: IIgnite.GetVersion
[
https://issues.apache.org/jira/browse/IGNITE-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811805#comment-16811805
]
Pavel Tupitsyn commented on IGNITE-7101:
[~ashapkin] Stage property is not populated.
> .NET: IIgnite.GetVersion
>
>
> Key: IGNITE-7101
> URL: https://issues.apache.org/jira/browse/IGNITE-7101
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Alexandr Shapkin
>Priority: Trivial
> Labels: .NET, newbie
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> Add {{IIgnite.GetVersion}} method and {{IClusterNode.Version}} property.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-11525) .NET: Deprecate SqlQuery API
[ https://issues.apache.org/jira/browse/IGNITE-11525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Tupitsyn resolved IGNITE-11525. - Resolution: Fixed > .NET: Deprecate SqlQuery API > > > Key: IGNITE-11525 > URL: https://issues.apache.org/jira/browse/IGNITE-11525 > Project: Ignite > Issue Type: Task > Components: platforms, thin client >Reporter: Taras Ledkov >Assignee: Pavel Tupitsyn >Priority: Major > Labels: .NET > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > This API is very limited comparing to SqlFieldsQuery. Let's deprecate it with > proper links to SqlFieldsQuery. This should be not only deprecation on public > API, but removal from examples as well. > Also please remove hidden columns _key, _val from examples. > All of this includes: > * Thin client and examples > * .NET Core examples > * LINQPad examples > Parent ticket: IGNITE-11334 > Ticket for documentation: IGNITE-11370 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11525) .NET: Deprecate SqlQuery API
[
https://issues.apache.org/jira/browse/IGNITE-11525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811775#comment-16811775
]
Pavel Tupitsyn commented on IGNITE-11525:
-
Merged to master: {{9fb5e46b2353e15e290d834b70f458fcc4ce7778}}
> .NET: Deprecate SqlQuery API
>
>
> Key: IGNITE-11525
> URL: https://issues.apache.org/jira/browse/IGNITE-11525
> Project: Ignite
> Issue Type: Task
> Components: platforms, thin client
>Reporter: Taras Ledkov
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This API is very limited comparing to SqlFieldsQuery. Let's deprecate it with
> proper links to SqlFieldsQuery. This should be not only deprecation on public
> API, but removal from examples as well.
> Also please remove hidden columns _key, _val from examples.
> All of this includes:
> * Thin client and examples
> * .NET Core examples
> * LINQPad examples
> Parent ticket: IGNITE-11334
> Ticket for documentation: IGNITE-11370
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
