[jira] [Commented] (IGNITE-12852) Comma in field is not supported by COPY command
[ https://issues.apache.org/jira/browse/IGNITE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17364016#comment-17364016 ] YuJue Li commented on IGNITE-12852: --- I don't know why the test didn't pass. Can you let [~antkr] (the patch provider) or [~rkondakov] or [~nizhikov] have a look at this problem? > Comma in field is not supported by COPY command > --- > > Key: IGNITE-12852 > URL: https://issues.apache.org/jira/browse/IGNITE-12852 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: YuJue Li >Assignee: YuJue Li >Priority: Critical > Fix For: 2.11 > > Time Spent: 0.5h > Remaining Estimate: 0h > > CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a)); > > a.csv: > 1,"a,b",2 > > COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV; > > The copy command fails because there is a comma in the second field,but this > is a fully legal and compliant CSV format -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14893) Bug in GridCacheWriteBehindStore Flusher thread lookup
[ https://issues.apache.org/jira/browse/IGNITE-14893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Korol reassigned IGNITE-14893: --- Assignee: Ilya Korol > Bug in GridCacheWriteBehindStore Flusher thread lookup > -- > > Key: IGNITE-14893 > URL: https://issues.apache.org/jira/browse/IGNITE-14893 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.8, 2.7.5, 2.7.6, 2.9, 2.8.1, 2.10, 2.9.1 >Reporter: Mike W >Assignee: Ilya Korol >Priority: Major > > There's a bug in GridCacheWriteBehindStore in the flusher method. > [https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/store/GridCacheWriteBehindStore.java#L674] > The logic states there that if flush thread count is not a power of 2, then > perform this math, which is not guaranteed to return a positive number. > > idx = ((h = key.hashCode()) ^ (h >>> 16)) % flushThreadCnt > > For > example, if you pass this string as a key, it returns a negative number: > accb2e8ea33e4a89b4189463cacc3c4e > and then throws an array out of bounds exception when looking up the thread. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-14906) SQL GROUP BY Column not found issue
[
https://issues.apache.org/jira/browse/IGNITE-14906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thibaud Faurie closed IGNITE-14906.
---
Duplicate of IGNITE-14905
> SQL GROUP BY Column not found issue
> ---
>
> Key: IGNITE-14906
> URL: https://issues.apache.org/jira/browse/IGNITE-14906
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql, thin client
>Affects Versions: 2.10
> Environment: Ignite server nodes on linux docker containers.
> Application executed in linux docker container.
> Windows 10 pro : DBeaver, VSCode
> My application language : Scala with Apache Ignite Java official library
>Reporter: Thibaud Faurie
>Priority: Major
>
> I have a query that I want to execute through SQL API.
> I have no issue when I run my Query with DBeaver (via Ignite thin client).
> But as soon as I use it in my code with SQL API, it throws an error saying
> that column permission_id is not found.
> More stranger thing, if I pause execution of my code (which generates an
> instance of client node in my cluster) at the SqlFieldsQuery execution step,
> the same error can be thrown by DBeaver sometimes (not 100% accurate)
> However, I figured out this error only occurs when I use the GROUP BY clause
> and some aggregation functions such as GROUP_CONCAT. As soon as I remove
> those, it works like a charm. I suspect some bug with H2 and distributed
> caches.
> Here is my SQL query :
> SELECT app_id, app_label, app_version, app_universal_id, app_status,
> app_manifest_url, app_store_url, app_created_at, app_updated_at,
> CONCAT_WS('||', permission_id, GROUP_CONCAT(content SEPARATOR ';'), code,
> language_id, label, GROUP_CONCAT(text_id SEPARATOR ';')) AS info_data,
> 'PERMISSION_LANG_VARIANT' AS type_data
> FROM (
> SELECT APP.id AS app_id, APP.label AS app_label, PERMISSION.id AS
> permission_id, TEXT.content, LANG.code, TEXT.language_id, LANG.label, TEXT.id
> AS text_id, APP.version AS app_version, APP.app_universal_id AS
> app_universal_id, APP.status AS app_status, APP.manifest_url AS
> app_manifest_url, APP.store_url AS app_store_url, APP.created_at AS
> app_created_at, APP.updated_at AS app_updated_at
> FROM FUSION.APPLICATION AS APP
> INNER JOIN FUSION.PERMISSION AS PERMISSION ON APP.id =
> PERMISSION.application_id
> INNER JOIN FUSION.TEXT AS TEXT ON TEXT.id = PERMISSION.label_text_id
> INNER JOIN FUSION.LANGUAGE AS LANG ON TEXT.language_id = LANG.id
> UNION ALL
> SELECT APP.id AS app_id, APP.label AS app_label, PERMISSION.id AS
> permission_id, TEXT.content, LANG.code, TEXT.language_id, LANG.label, TEXT.id
> AS text_id, APP.version AS app_version, APP.app_universal_id AS
> app_universal_id, APP.status AS app_status, APP.manifest_url AS
> app_manifest_url, APP.store_url AS app_store_url, APP.created_at AS
> app_created_at, APP.updated_at AS app_updated_at
> FROM FUSION.APPLICATION AS APP
> INNER JOIN FUSION.PERMISSION AS PERMISSION ON APP.id =
> PERMISSION.application_id
> INNER JOIN FUSION.TEXT AS TEXT ON TEXT.id = PERMISSION.description_text_id
> INNER JOIN FUSION.LANGUAGE AS LANG ON TEXT.language_id = LANG.id
> )
> GROUP BY permission_id, language_id
> Here is the code I use to execute:
> var igniteQuery = new SqlFieldsQuery(queryString)
> var query = igniteCache.query(igniteQuery)
> query.getAll()
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-14906) SQL GROUP BY Column not found issue
[
https://issues.apache.org/jira/browse/IGNITE-14906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thibaud Faurie resolved IGNITE-14906.
-
Release Note: Missclick : Duplicate of IGNITE-14905
Resolution: Duplicate
> SQL GROUP BY Column not found issue
> ---
>
> Key: IGNITE-14906
> URL: https://issues.apache.org/jira/browse/IGNITE-14906
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql, thin client
>Affects Versions: 2.10
> Environment: Ignite server nodes on linux docker containers.
> Application executed in linux docker container.
> Windows 10 pro : DBeaver, VSCode
> My application language : Scala with Apache Ignite Java official library
>Reporter: Thibaud Faurie
>Priority: Major
>
> I have a query that I want to execute through SQL API.
> I have no issue when I run my Query with DBeaver (via Ignite thin client).
> But as soon as I use it in my code with SQL API, it throws an error saying
> that column permission_id is not found.
> More stranger thing, if I pause execution of my code (which generates an
> instance of client node in my cluster) at the SqlFieldsQuery execution step,
> the same error can be thrown by DBeaver sometimes (not 100% accurate)
> However, I figured out this error only occurs when I use the GROUP BY clause
> and some aggregation functions such as GROUP_CONCAT. As soon as I remove
> those, it works like a charm. I suspect some bug with H2 and distributed
> caches.
> Here is my SQL query :
> SELECT app_id, app_label, app_version, app_universal_id, app_status,
> app_manifest_url, app_store_url, app_created_at, app_updated_at,
> CONCAT_WS('||', permission_id, GROUP_CONCAT(content SEPARATOR ';'), code,
> language_id, label, GROUP_CONCAT(text_id SEPARATOR ';')) AS info_data,
> 'PERMISSION_LANG_VARIANT' AS type_data
> FROM (
> SELECT APP.id AS app_id, APP.label AS app_label, PERMISSION.id AS
> permission_id, TEXT.content, LANG.code, TEXT.language_id, LANG.label, TEXT.id
> AS text_id, APP.version AS app_version, APP.app_universal_id AS
> app_universal_id, APP.status AS app_status, APP.manifest_url AS
> app_manifest_url, APP.store_url AS app_store_url, APP.created_at AS
> app_created_at, APP.updated_at AS app_updated_at
> FROM FUSION.APPLICATION AS APP
> INNER JOIN FUSION.PERMISSION AS PERMISSION ON APP.id =
> PERMISSION.application_id
> INNER JOIN FUSION.TEXT AS TEXT ON TEXT.id = PERMISSION.label_text_id
> INNER JOIN FUSION.LANGUAGE AS LANG ON TEXT.language_id = LANG.id
> UNION ALL
> SELECT APP.id AS app_id, APP.label AS app_label, PERMISSION.id AS
> permission_id, TEXT.content, LANG.code, TEXT.language_id, LANG.label, TEXT.id
> AS text_id, APP.version AS app_version, APP.app_universal_id AS
> app_universal_id, APP.status AS app_status, APP.manifest_url AS
> app_manifest_url, APP.store_url AS app_store_url, APP.created_at AS
> app_created_at, APP.updated_at AS app_updated_at
> FROM FUSION.APPLICATION AS APP
> INNER JOIN FUSION.PERMISSION AS PERMISSION ON APP.id =
> PERMISSION.application_id
> INNER JOIN FUSION.TEXT AS TEXT ON TEXT.id = PERMISSION.description_text_id
> INNER JOIN FUSION.LANGUAGE AS LANG ON TEXT.language_id = LANG.id
> )
> GROUP BY permission_id, language_id
> Here is the code I use to execute:
> var igniteQuery = new SqlFieldsQuery(queryString)
> var query = igniteCache.query(igniteQuery)
> query.getAll()
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14905) SQL GROUP BY Column not found issue
Thibaud Faurie created IGNITE-14905:
---
Summary: SQL GROUP BY Column not found issue
Key: IGNITE-14905
URL: https://issues.apache.org/jira/browse/IGNITE-14905
Project: Ignite
Issue Type: Bug
Components: cache, sql, thin client
Affects Versions: 2.10
Environment: Ignite server nodes on linux docker containers.
Application executed in linux docker container.
Windows 10 pro : DBeaver, VSCode
My application language : Scala with Apache Ignite Java official library
Reporter: Thibaud Faurie
I have a query that I want to execute through SQL API.
I have no issue when I run my Query with DBeaver (via Ignite thin client).
But as soon as I use it in my code with SQL API, it throws an error saying that
column permission_id is not found.
More stranger thing, if I pause execution of my code (which generates an
instance of client node in my cluster) at the SqlFieldsQuery execution step,
the same error can be thrown by DBeaver sometimes (not 100% accurate)
However, I figured out this error only occurs when I use the GROUP BY clause
and some aggregation functions such as GROUP_CONCAT. As soon as I remove those,
it works like a charm. I suspect some bug with H2 and distributed caches.
Here is my SQL query :
SELECT app_id, app_label, app_version, app_universal_id, app_status,
app_manifest_url, app_store_url, app_created_at, app_updated_at,
CONCAT_WS('||', permission_id, GROUP_CONCAT(content SEPARATOR ';'), code,
language_id, label, GROUP_CONCAT(text_id SEPARATOR ';')) AS info_data,
'PERMISSION_LANG_VARIANT' AS type_data
FROM (
SELECT APP.id AS app_id, APP.label AS app_label, PERMISSION.id AS
permission_id, TEXT.content, LANG.code, TEXT.language_id, LANG.label, TEXT.id
AS text_id, APP.version AS app_version, APP.app_universal_id AS
app_universal_id, APP.status AS app_status, APP.manifest_url AS
app_manifest_url, APP.store_url AS app_store_url, APP.created_at AS
app_created_at, APP.updated_at AS app_updated_at
FROM FUSION.APPLICATION AS APP
INNER JOIN FUSION.PERMISSION AS PERMISSION ON APP.id =
PERMISSION.application_id
INNER JOIN FUSION.TEXT AS TEXT ON TEXT.id = PERMISSION.label_text_id
INNER JOIN FUSION.LANGUAGE AS LANG ON TEXT.language_id = LANG.id
UNION ALL
SELECT APP.id AS app_id, APP.label AS app_label, PERMISSION.id AS
permission_id, TEXT.content, LANG.code, TEXT.language_id, LANG.label, TEXT.id
AS text_id, APP.version AS app_version, APP.app_universal_id AS
app_universal_id, APP.status AS app_status, APP.manifest_url AS
app_manifest_url, APP.store_url AS app_store_url, APP.created_at AS
app_created_at, APP.updated_at AS app_updated_at
FROM FUSION.APPLICATION AS APP
INNER JOIN FUSION.PERMISSION AS PERMISSION ON APP.id =
PERMISSION.application_id
INNER JOIN FUSION.TEXT AS TEXT ON TEXT.id = PERMISSION.description_text_id
INNER JOIN FUSION.LANGUAGE AS LANG ON TEXT.language_id = LANG.id
)
GROUP BY permission_id, language_id
Here is the code I use to execute:
var igniteQuery = new SqlFieldsQuery(queryString)
var query = igniteCache.query(igniteQuery)
query.getAll()
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14906) SQL GROUP BY Column not found issue
Thibaud Faurie created IGNITE-14906:
---
Summary: SQL GROUP BY Column not found issue
Key: IGNITE-14906
URL: https://issues.apache.org/jira/browse/IGNITE-14906
Project: Ignite
Issue Type: Bug
Components: cache, sql, thin client
Affects Versions: 2.10
Environment: Ignite server nodes on linux docker containers.
Application executed in linux docker container.
Windows 10 pro : DBeaver, VSCode
My application language : Scala with Apache Ignite Java official library
Reporter: Thibaud Faurie
I have a query that I want to execute through SQL API.
I have no issue when I run my Query with DBeaver (via Ignite thin client).
But as soon as I use it in my code with SQL API, it throws an error saying that
column permission_id is not found.
More stranger thing, if I pause execution of my code (which generates an
instance of client node in my cluster) at the SqlFieldsQuery execution step,
the same error can be thrown by DBeaver sometimes (not 100% accurate)
However, I figured out this error only occurs when I use the GROUP BY clause
and some aggregation functions such as GROUP_CONCAT. As soon as I remove those,
it works like a charm. I suspect some bug with H2 and distributed caches.
Here is my SQL query :
SELECT app_id, app_label, app_version, app_universal_id, app_status,
app_manifest_url, app_store_url, app_created_at, app_updated_at,
CONCAT_WS('||', permission_id, GROUP_CONCAT(content SEPARATOR ';'), code,
language_id, label, GROUP_CONCAT(text_id SEPARATOR ';')) AS info_data,
'PERMISSION_LANG_VARIANT' AS type_data
FROM (
SELECT APP.id AS app_id, APP.label AS app_label, PERMISSION.id AS
permission_id, TEXT.content, LANG.code, TEXT.language_id, LANG.label, TEXT.id
AS text_id, APP.version AS app_version, APP.app_universal_id AS
app_universal_id, APP.status AS app_status, APP.manifest_url AS
app_manifest_url, APP.store_url AS app_store_url, APP.created_at AS
app_created_at, APP.updated_at AS app_updated_at
FROM FUSION.APPLICATION AS APP
INNER JOIN FUSION.PERMISSION AS PERMISSION ON APP.id =
PERMISSION.application_id
INNER JOIN FUSION.TEXT AS TEXT ON TEXT.id = PERMISSION.label_text_id
INNER JOIN FUSION.LANGUAGE AS LANG ON TEXT.language_id = LANG.id
UNION ALL
SELECT APP.id AS app_id, APP.label AS app_label, PERMISSION.id AS
permission_id, TEXT.content, LANG.code, TEXT.language_id, LANG.label, TEXT.id
AS text_id, APP.version AS app_version, APP.app_universal_id AS
app_universal_id, APP.status AS app_status, APP.manifest_url AS
app_manifest_url, APP.store_url AS app_store_url, APP.created_at AS
app_created_at, APP.updated_at AS app_updated_at
FROM FUSION.APPLICATION AS APP
INNER JOIN FUSION.PERMISSION AS PERMISSION ON APP.id =
PERMISSION.application_id
INNER JOIN FUSION.TEXT AS TEXT ON TEXT.id = PERMISSION.description_text_id
INNER JOIN FUSION.LANGUAGE AS LANG ON TEXT.language_id = LANG.id
)
GROUP BY permission_id, language_id
Here is the code I use to execute:
var igniteQuery = new SqlFieldsQuery(queryString)
var query = igniteCache.query(igniteQuery)
query.getAll()
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14857) Calcite integration. ALTER TABLE support
[ https://issues.apache.org/jira/browse/IGNITE-14857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov reassigned IGNITE-14857: -- Assignee: Aleksey Plekhanov > Calcite integration. ALTER TABLE support > > > Key: IGNITE-14857 > URL: https://issues.apache.org/jira/browse/IGNITE-14857 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Aleksey Plekhanov >Priority: Major > > We need to support DDL commands. The task about the support of ALTER TABLE > ADD/DROP/ALTER COLUMN. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13549) Calcite integration. CREATE/DROP INDEX support
[ https://issues.apache.org/jira/browse/IGNITE-13549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363923#comment-17363923 ] Aleksey Plekhanov commented on IGNITE-13549: [~korlov], [~tledkov-gridgain], [~jooger] can you please review the patch? > Calcite integration. CREATE/DROP INDEX support > -- > > Key: IGNITE-13549 > URL: https://issues.apache.org/jira/browse/IGNITE-13549 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Yury Gerzhedovich >Assignee: Aleksey Plekhanov >Priority: Critical > Time Spent: 10m > Remaining Estimate: 0h > > We need to support DDL commands. The task about the support of CREATE/DROP > INDEX. Potentially with syntaxis as we already have in the H2 engine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14120) select count * returns multiple rows
[
https://issues.apache.org/jira/browse/IGNITE-14120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363798#comment-17363798
]
Ignite TC Bot commented on IGNITE-14120:
{panel:title=Branch: [pull/9164/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9164/head] Base: [master] : New Tests
(3)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Continuous Query 4{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=6048731]]
* {color:#013220}IgniteCacheQuerySelfTestSuite6:
IgniteSqlSinglePartitionMultiParallelismTest.testSimpleCountQuery -
PASSED{color}
* {color:#013220}IgniteCacheQuerySelfTestSuite6:
IgniteSqlSinglePartitionMultiParallelismTest.testWhereCountMultiPartitionsQuery
- PASSED{color}
* {color:#013220}IgniteCacheQuerySelfTestSuite6:
IgniteSqlSinglePartitionMultiParallelismTest.testWhereCountFirstPartitionQuery
- PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6048766buildTypeId=IgniteTests24Java8_RunAll]
> select count * returns multiple rows
>
>
> Key: IGNITE-14120
> URL: https://issues.apache.org/jira/browse/IGNITE-14120
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.8.1
>Reporter: Isaac Zhu
>Assignee: Vladimir Ermakov
>Priority: Major
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> I have a partitioned table which has 1 backup, the *queryParallelism* is set
> to 4.
> The table primary key is column "ID",
> If I do this query:
> select count( * ) from my_table where ID = 1000;
> It will return 4 rows:
> 1
> 0
> 0
> 0
>
> If I query by other not primary-key columns of this table, the result is
> good, like:
> select count( *) from my_table where name = 'abcd'
> result is:
> 0
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12852) Comma in field is not supported by COPY command
[ https://issues.apache.org/jira/browse/IGNITE-12852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363762#comment-17363762 ] Dmitry Pavlov commented on IGNITE-12852: [~liyuj] could you please merge actual master into your PR branch? Unfortunately current failed test number makes it impossible to ananlyse if it is safe to merge. > Comma in field is not supported by COPY command > --- > > Key: IGNITE-12852 > URL: https://issues.apache.org/jira/browse/IGNITE-12852 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8 >Reporter: YuJue Li >Assignee: YuJue Li >Priority: Critical > Fix For: 2.11 > > Time Spent: 0.5h > Remaining Estimate: 0h > > CREATE TABLE test(a int,b varchar(100),c int,PRIMARY key(a)); > > a.csv: > 1,"a,b",2 > > COPY FROM '/data/a.csv' INTO test (a,b,c) FORMAT CSV; > > The copy command fails because there is a comma in the second field,but this > is a fully legal and compliant CSV format -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14658) [IEP-35] SSL metrics
[ https://issues.apache.org/jira/browse/IGNITE-14658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363760#comment-17363760 ] Amelchev Nikita commented on IGNITE-14658: -- Cherry-picked to the 2.11 branch. > [IEP-35] SSL metrics > > > Key: IGNITE-14658 > URL: https://issues.apache.org/jira/browse/IGNITE-14658 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Mikhail Petrov >Priority: Major > Labels: IEP-35 > Fix For: 2.11 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > The following SSL metrics required: > * Count of SSL sessions. > * Count of rejected SSL sessions. > * Handshake time metric. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14658) [IEP-35] SSL metrics
[ https://issues.apache.org/jira/browse/IGNITE-14658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-14658: - Fix Version/s: (was: 2.12) 2.11 > [IEP-35] SSL metrics > > > Key: IGNITE-14658 > URL: https://issues.apache.org/jira/browse/IGNITE-14658 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Assignee: Mikhail Petrov >Priority: Major > Labels: IEP-35 > Fix For: 2.11 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > The following SSL metrics required: > * Count of SSL sessions. > * Count of rejected SSL sessions. > * Handshake time metric. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14904) Dynamic configuration management engine
Valentin Kulichenko created IGNITE-14904: Summary: Dynamic configuration management engine Key: IGNITE-14904 URL: https://issues.apache.org/jira/browse/IGNITE-14904 Project: Ignite Issue Type: Epic Reporter: Valentin Kulichenko -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14903) Calcite. Bump calcite version up to 1.27.0.
[ https://issues.apache.org/jira/browse/IGNITE-14903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanilovsky Evgeny updated IGNITE-14903: Description: Update calcite ver up to 1.27.0. > Calcite. Bump calcite version up to 1.27.0. > --- > > Key: IGNITE-14903 > URL: https://issues.apache.org/jira/browse/IGNITE-14903 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Labels: calcite > > Update calcite ver up to 1.27.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14903) Calcite. Bump calcite version up to 1.27.0.
Stanilovsky Evgeny created IGNITE-14903: --- Summary: Calcite. Bump calcite version up to 1.27.0. Key: IGNITE-14903 URL: https://issues.apache.org/jira/browse/IGNITE-14903 Project: Ignite Issue Type: Improvement Components: sql Reporter: Stanilovsky Evgeny Assignee: Stanilovsky Evgeny -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14901) Document SSL metrics.
[ https://issues.apache.org/jira/browse/IGNITE-14901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363592#comment-17363592 ] Mikhail Petrov commented on IGNITE-14901: - [~nsafonov], Could you please take a look? > Document SSL metrics. > - > > Key: IGNITE-14901 > URL: https://issues.apache.org/jira/browse/IGNITE-14901 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > It is needed to document SSL metrics introduced by > https://issues.apache.org/jira/browse/IGNITE-14658 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14902) Implement RecordView API
Vyacheslav Koptilin created IGNITE-14902:
Summary: Implement RecordView API
Key: IGNITE-14902
URL: https://issues.apache.org/jira/browse/IGNITE-14902
Project: Ignite
Issue Type: Improvement
Reporter: Vyacheslav Koptilin
- Implement a record mapping that is required for {{RecordView}}.
- Implement all {{RecordView}} operations except {{invoke}} IGNITE-14488
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14854) Fix tests IgniteCacheLocalQueryDefaultTimeoutSelfTest for lazy=true mode
[
https://issues.apache.org/jira/browse/IGNITE-14854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363497#comment-17363497
]
Ignite TC Bot commented on IGNITE-14854:
{panel:title=Branch: [pull/9161/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9161/head] Base: [master] : New Tests
(72)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 2{color} [[tests
72|https://ci.ignite.apache.org/viewLog.html?buildId=6041371]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
DefaultQueryTimeoutThickJavaTest.testConcurrent[lazy=true, update=false,
local=true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
DefaultQueryTimeoutThickJavaTest.testNoExplicitTimeout3[lazy=true,
update=false, local=true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
DefaultQueryTimeoutThickJavaTest.testExplicitTimeout2[lazy=true, update=false,
local=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
DefaultQueryTimeoutThickJavaTest.testExplicitTimeout1[lazy=true, update=false,
local=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
DefaultQueryTimeoutThickJavaTest.testExplicitTimeout4[lazy=true, update=false,
local=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
DefaultQueryTimeoutThickJavaTest.testExplicitTimeout3[lazy=true, update=false,
local=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
DefaultQueryTimeoutThickJavaTest.testExplicitTimeout6[lazy=true, update=false,
local=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
DefaultQueryTimeoutThickJavaTest.testExplicitTimeout5[lazy=true, update=false,
local=false] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
DefaultQueryTimeoutThickJavaTest.testExplicitTimeout4[lazy=true, update=false,
local=true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
DefaultQueryTimeoutThickJavaTest.testExplicitTimeout3[lazy=true, update=false,
local=true] - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2:
DefaultQueryTimeoutThickJavaTest.testExplicitTimeout6[lazy=true, update=false,
local=true] - PASSED{color}
... and 61 new tests
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6041446buildTypeId=IgniteTests24Java8_RunAll]
> Fix tests IgniteCacheLocalQueryDefaultTimeoutSelfTest for lazy=true mode
>
>
> Key: IGNITE-14854
> URL: https://issues.apache.org/jira/browse/IGNITE-14854
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.12
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Tests are not stable:
> {{IgniteCacheLocalQueryDefaultTimeoutSelfTest.testQueryTimeout}}
> {{IgniteCacheLocalQueryDefaultTimeoutSelfTest.testQueryDefaultTimeout}}
> The local runs are OK. So I guess the timeout works OK. Looks like the tests
> must be stabilized for TC.
> Root cause: the test isn't adopted for lazy mode (results aren't fetched,
> only iterator is opened)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14709) Allow node to start if there is no bootstraped configuration
[
https://issues.apache.org/jira/browse/IGNITE-14709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-14709:
-
Reviewer: Vyacheslav Koptilin
> Allow node to start if there is no bootstraped configuration
>
>
> Key: IGNITE-14709
> URL: https://issues.apache.org/jira/browse/IGNITE-14709
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Assignee: Mirza Aliev
>Priority: Major
> Labels: ignite-3
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Currently, we faced with a problem when a node starts it is hanged on phase
> when we register {{DistributedConfigurationStorage}}. It happens because when
> {{ConfigurationChanger#register}} is run it requires
> {{ConfigurationStorage#readAll}}, this, in turn, calls
> {{MetaStorageServiceImpl#range}}, but the range is waiting on future until
> cluster init happens, so all process of starting node is hanged.
> Could be reproduced in
> {{IgnitionTest#testNodeStartWithoutBootstrapConfiguration}}
> A possible solution is to not use metastorage in
> {{DistributedConfigurationStorage#readAll}}, and use stored projection of cfg
> keys from Vault.
> Also, node start hangs because {{MetaStorageManager#deployWatches}} also
> waits for metastorage to be initialized with metastorage nodes, so we do not
> need to wait if metastorage nodes weren't explicitly set on start and we
> should move waiting of the future to
> [init|https://issues.apache.org/jira/browse/IGNITE-14414] phase
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14653) Generify Vault and Metastorage services interfaces
[
https://issues.apache.org/jira/browse/IGNITE-14653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363491#comment-17363491
]
Aleksandr Polovtcev edited comment on IGNITE-14653 at 6/15/21, 9:02 AM:
After a brief discussion with [~agura] , we decided to close this ticket due to
the following reasons:
1. It is intended to have different interfaces for each storage type in
Ignite, and having a unified interface for two of them will be inconsistent
with the overall design.
2. Vault and MetaStorage are conceptually two different things: Vault is a
simple local storage, while MetaStorage is a distributed storage with a more
complex contract (like atomicity guarantees).
3. At the moment of writing, these interfaces are already quite different and
unification can prove to be difficult.
was (Author: apolovtcev):
After a brief discussion with [~agura] , we decided to close this ticket due to
the following reasons:
1. It is decided to have different interfaces for each storage type in Ignite,
and having a unified interface for two of them will be inconsistent with the
overall design.
2. Vault and MetaStorage are conceptually two different things: Vault is a
simple local storage, while MetaStorage is a distributed storage with a more
complex contract (like atomicity guarantees).
3. At the moment of writing, these interfaces are already quite different and
unification can prove to be difficult.
> Generify Vault and Metastorage services interfaces
> ---
>
> Key: IGNITE-14653
> URL: https://issues.apache.org/jira/browse/IGNITE-14653
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Priority: Major
> Labels: iep-61, ignite-3
>
> Currently, we have two separate interfaces {{ValutService}} and
> {{MetastorageService}}, but they have a lot of common methods. Seems that it
> would be convenient to have a common interface.
> * Retrieve a common interface for vault and metastorage
> * We need a common interface for listeners on vault and metastorage with
> {{onUpdate}} and {{onError}} methods
> * We should have {{Entry}} interface for vault that will be extended with
> metastorage {{Entry}} with extra revision logic
> * Also seems that {{Watcher}} from metastorage and vault might have a common
> parent
> * Use common contract for {{watch}} method in vault and metastorage
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-14653) Generify Vault and Metastorage services interfaces
[
https://issues.apache.org/jira/browse/IGNITE-14653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev resolved IGNITE-14653.
--
Resolution: Won't Fix
After a brief discussion with [~agura] , we decided to close this ticket due to
the following reasons:
1. It is decided to have different interfaces for each storage type in Ignite,
and having a unified interface for two of them will be inconsistent with the
overall design.
2. Vault and MetaStorage are conceptually two different things: Vault is a
simple local storage, while MetaStorage is a distributed storage with a more
complex contract (like atomicity guarantees).
3. At the moment of writing, these interfaces are already quite different and
unification can prove to be difficult.
> Generify Vault and Metastorage services interfaces
> ---
>
> Key: IGNITE-14653
> URL: https://issues.apache.org/jira/browse/IGNITE-14653
> Project: Ignite
> Issue Type: Improvement
>Reporter: Mirza Aliev
>Priority: Major
> Labels: iep-61, ignite-3
>
> Currently, we have two separate interfaces {{ValutService}} and
> {{MetastorageService}}, but they have a lot of common methods. Seems that it
> would be convenient to have a common interface.
> * Retrieve a common interface for vault and metastorage
> * We need a common interface for listeners on vault and metastorage with
> {{onUpdate}} and {{onError}} methods
> * We should have {{Entry}} interface for vault that will be extended with
> metastorage {{Entry}} with extra revision logic
> * Also seems that {{Watcher}} from metastorage and vault might have a common
> parent
> * Use common contract for {{watch}} method in vault and metastorage
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-14654) Use Cursor instead of Iterator in VaultService#range
[ https://issues.apache.org/jira/browse/IGNITE-14654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev resolved IGNITE-14654. -- Resolution: Invalid Will be fixed during https://issues.apache.org/jira/browse/IGNITE-14408 > Use Cursor instead of Iterator in VaultService#range > > > Key: IGNITE-14654 > URL: https://issues.apache.org/jira/browse/IGNITE-14654 > Project: Ignite > Issue Type: Sub-task >Reporter: Mirza Aliev >Assignee: Mirza Aliev >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14898) IndexOutOfBoundException in flusher selection logic in GridCacheWriteBehindStore
[
https://issues.apache.org/jira/browse/IGNITE-14898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Korol resolved IGNITE-14898.
-
Resolution: Duplicate
> IndexOutOfBoundException in flusher selection logic in
> GridCacheWriteBehindStore
>
>
> Key: IGNITE-14898
> URL: https://issues.apache.org/jira/browse/IGNITE-14898
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.10
>Reporter: Ilya Korol
>Assignee: Ilya Korol
>Priority: Major
>
> There i a bug in GridCacheWriteBehindStore method for selecting which flusher
> should be used for current data write by specified key:
> {code:java}
> /**
> * Return flusher by by key.
> *
> * @param key Key for search.
> * @return flusher.
> */
> private Flusher flusher(K key) {
> int h, idx;
> if (flushThreadCntIsPowerOfTwo)
> idx = ((h = key.hashCode()) ^ (h >>> 16)) & (flushThreadCnt - 1);
> else
> idx = ((h = key.hashCode()) ^ (h >>> 16)) % flushThreadCnt;
> return flushThreads[idx];
> }
> {code}
> In case when flushThreadCount is not a power of 2 and incoming key.hashCode()
> < 0 (e.g. for UUID string) we will get IndexOutOfBoundException.
> http://apache-ignite-users.70518.x6.nabble.com/Bug-in-GridCacheWriteBehindStore-td36189.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13752) Schema evolution converters.
[ https://issues.apache.org/jira/browse/IGNITE-13752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-13752: -- Description: h3. Motivation. The Live-schema concept supposes a tuple of old-version can be upgraded to a tuple of new-version automatically. h3. Description. Table SchemaManager tracks schema changes and keeps a history of changes. Let's implements the mechanics to apply these historical changes to a Row to upgrade to the latest version. was: h3. Motivation. The Live-schema concept supposes a tuple of old-version can be upgraded to a tuple of new-version automatically. h3. Description. Table SchemaManager tracks schema changes and keeps a history of changes. Let's implements the mechanics to apply these historical changes to a Row to upgrade to the latest version. Additionally, * investigate if some changes can be squashed, e.g. "drop column" and "add column" of the same name and create a ticket for this. * Investigate if row upgrade can be "No-op" and just rises a schema version in a Row in-place without copying (e.g. a Row is tombstone or 'null' row was dropped and maybe we can rewrite the whole Row in-place) and create a ticket for possible optimizations. > Schema evolution converters. > > > Key: IGNITE-13752 > URL: https://issues.apache.org/jira/browse/IGNITE-13752 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Andrey Mashenkov >Priority: Major > Labels: iep-54, ignite-3 > Fix For: 3.0.0-alpha3 > > Original Estimate: 360h > Remaining Estimate: 360h > > h3. Motivation. > The Live-schema concept supposes a tuple of old-version can be upgraded to a > tuple of new-version automatically. > h3. Description. > Table SchemaManager tracks schema changes and keeps a history of changes. > Let's implements the mechanics to apply these historical changes to a Row to > upgrade to the latest version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14900) Python "Can not query binary type" error on collections of objects
[
https://issues.apache.org/jira/browse/IGNITE-14900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17363438#comment-17363438
]
Ivan Daschinsky commented on IGNITE-14900:
--
[~bojidar-bg] Hi, thank you for this issue. A brand new version (0.5.0) is
almost ready and we will release it in a week. It also contains transactions,
expiry policy support and some performance imrpovements of asyncio version.
Stay tuned.
> Python "Can not query binary type" error on collections of objects
> --
>
> Key: IGNITE-14900
> URL: https://issues.apache.org/jira/browse/IGNITE-14900
> Project: Ignite
> Issue Type: Bug
> Components: python
>Affects Versions: python-0.4.0
> Environment: {noformat}
> pyignite==0.4.0
> org.apache.ignite:ignite-core:2.10.0{noformat}
>
>Reporter: Bojidar Marinov
>Priority: Major
> Fix For: python-0.5.0
>
> Attachments: repro.py
>
>
> When reading an object which has a CollectionObject field containing binary
> objects, the Python thin client fails to read the object with e.g.
>
> {noformat}
> pyignite.exceptions.ParseError: Can not query binary type -1322970774
> {noformat}
> The same occurs with ObjectArrayObject and MapObject fields.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14599) Add generic way to bootstrap configuration
[
https://issues.apache.org/jira/browse/IGNITE-14599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Gusakov reassigned IGNITE-14599:
---
Assignee: Kirill Gusakov (was: Alexander Lapin)
> Add generic way to bootstrap configuration
> ---
>
> Key: IGNITE-14599
> URL: https://issues.apache.org/jira/browse/IGNITE-14599
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexander Lapin
>Assignee: Kirill Gusakov
>Priority: Major
> Labels: iep-73
>
> Currently it's possible to bootstrap configuration only with json formatted
> string.
> {code:java}
> Ignite start(@Nullable String jsonStrBootstrapCfg);
> {code}
> Instead of given temporary solution some sort of generic implementation
> should be used, for example configuration file with set of formats: json,
> hocon.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14901) Document SSL metrics.
[ https://issues.apache.org/jira/browse/IGNITE-14901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Petrov updated IGNITE-14901: Summary: Document SSL metrics. (was: Documents SSL metrics.) > Document SSL metrics. > - > > Key: IGNITE-14901 > URL: https://issues.apache.org/jira/browse/IGNITE-14901 > Project: Ignite > Issue Type: Improvement >Reporter: Mikhail Petrov >Assignee: Mikhail Petrov >Priority: Major > > It is needed to document SSL metrics introduced by > https://issues.apache.org/jira/browse/IGNITE-14658 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14901) Documents SSL metrics.
Mikhail Petrov created IGNITE-14901: --- Summary: Documents SSL metrics. Key: IGNITE-14901 URL: https://issues.apache.org/jira/browse/IGNITE-14901 Project: Ignite Issue Type: Improvement Reporter: Mikhail Petrov Assignee: Mikhail Petrov It is needed to document SSL metrics introduced by https://issues.apache.org/jira/browse/IGNITE-14658 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14812) SQL statistics
[ https://issues.apache.org/jira/browse/IGNITE-14812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taras Ledkov updated IGNITE-14812: -- Fix Version/s: 2.12 > SQL statistics > -- > > Key: IGNITE-14812 > URL: https://issues.apache.org/jira/browse/IGNITE-14812 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Alexander Belyak >Assignee: Alexander Belyak >Priority: Major > Fix For: 2.12 > > Time Spent: 20m > Remaining Estimate: 0h > > Add statistics collection and usage. -- This message was sent by Atlassian Jira (v8.3.4#803005)
