[jira] [Created] (IGNITE-14348) Use classes with different version
Surkov Aleksandr created IGNITE-14348: - Summary: Use classes with different version Key: IGNITE-14348 URL: https://issues.apache.org/jira/browse/IGNITE-14348 Project: Ignite Issue Type: Bug Affects Versions: 2.9 Reporter: Surkov Aleksandr Attachments: use-different-classes.zip There may be a situation when the user saves objects with one version of the class, and receives with another version. For example, after adding or removing a field in the class, the value of the serialVersionUID field may changed. After that, two situations can occur: # if user save object as value(key - SomeObject) or map(key - Map) then there will be no errors; # if for value used list of SomeObject then there will be error; -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Azure Cloud IP Finder
Explanation of the design: The design follows a similar model to existing IP finders -- it either takes a pre-created container or creates a new container and creates entries in it for each IP address. I have tested it with a test account and the operation is fine. On Fri, Mar 19, 2021 at 10:23 AM Atri Sharma wrote: > > Thanks Denis. > > I have raised a PR for the same: > > https://github.com/apache/ignite/pull/8897 > > Regards, > > Atri > > On Wed, Mar 10, 2021 at 1:21 AM Denis Magda wrote: > > > > Atri, > > > > Let's discuss the subj together with the community. Ignite already supports > > AWS [1] and GCE [2] IP Finders out of the box, but the Azure one is still > > missing. I can confirm that the demand exists, and rather frequently, I see > > developers asking for an Azure-native IP finder for Ignite. > > > > Atri, could you please research how to implement the IP finder and suggest > > a solution in this discussion thread? See how it was done for AWS and GCE, > > we might go the same route or use a more contemporary and easy-to-configure > > approach for Azure. > > > > [1] > > https://ignite.apache.org/docs/latest/clustering/discovery-in-the-cloud#amazon-s3-ip-finder > > [2] > > https://ignite.apache.org/docs/latest/clustering/discovery-in-the-cloud#google-compute-discovery > > > > - > > Denis > > > > -- > Regards, > > Atri > Apache Concerted -- Regards, Atri Apache Concerted
[jira] [Created] (IGNITE-14349) Add query attributes to QueryHistoryTracker#qryHist and QueryHistory
Denis Mekhanikov created IGNITE-14349: - Summary: Add query attributes to QueryHistoryTracker#qryHist and QueryHistory Key: IGNITE-14349 URL: https://issues.apache.org/jira/browse/IGNITE-14349 Project: Ignite Issue Type: Improvement Components: sql Reporter: Denis Mekhanikov We want to see two additional metrics into an query history: enforceJoinOrder and lazy. Someone should add them to QueryHistoryTracker#qryHist and map to QueryHistory. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14350) Runtime change of CDC parameters
Nikolay Izhikov created IGNITE-14350: Summary: Runtime change of CDC parameters Key: IGNITE-14350 URL: https://issues.apache.org/jira/browse/IGNITE-14350 Project: Ignite Issue Type: New Feature Reporter: Nikolay Izhikov If CDC enabled for cluster nodes and CDC application is down for a long time it can lead to disk overflow and cluster instability. An administrator should be able to turn off the CDC feature in runtime -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14351) Runtime change of WAL force rollover parameters
Nikolay Izhikov created IGNITE-14351: Summary: Runtime change of WAL force rollover parameters Key: IGNITE-14351 URL: https://issues.apache.org/jira/browse/IGNITE-14351 Project: Ignite Issue Type: New Feature Reporter: Nikolay Izhikov If CDC enabled for cluster nodes and CDC application is down for a long time it can lead to disk overflow and cluster instability. An administrator should be able to turn off the CDC feature in runtime -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14352) Added the ability to check the consistency of individual cache groups in a snapshot.
Pavel Pereslegin created IGNITE-14352: - Summary: Added the ability to check the consistency of individual cache groups in a snapshot. Key: IGNITE-14352 URL: https://issues.apache.org/jira/browse/IGNITE-14352 Project: Ignite Issue Type: Improvement Reporter: Pavel Pereslegin IGNITE-13725 introduces a snapshot check command to check the whole snapshot consistency. But sometimes it's necessary only to check the consistency only of individual cache groups in the snapshot (for example in IGNITE-13805 - restore operation of the cache group). -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Access to Ignite Confluence
Hello Ilya, Thank you very much! Regards, Nikita чт, 18 мар. 2021 г. в 18:34, Ilya Kasnacheev : > Hello! > > I have granted you full edit rights on our Confluence space. > > TWIMC I have validated with Nikita that it's his actual email address. > > Regards, > -- > Ilya Kasnacheev > > > вт, 16 мар. 2021 г. в 22:28, Никита Сафонов : > > > Hi everyone, > > > > Could you please grant me the necessary rights to comment on the > confluence > > articles? > > > > My full name: Nikita Safonov > > Email: vlasovpavel2...@gmail.com > > > > Thank you! > > > > Regards, > > Nikita > > >
[jira] [Created] (IGNITE-14353) Ability to specify log file for IgniteLogger
Nikolay Izhikov created IGNITE-14353:
Summary: Ability to specify log file for IgniteLogger
Key: IGNITE-14353
URL: https://issues.apache.org/jira/browse/IGNITE-14353
Project: Ignite
Issue Type: New Feature
Reporter: Nikolay Izhikov
Right now, user can't change IgniteLogger file name.
CDC application should use it's own files for logging, something like
{{cdc-{cdc_consumer_id}.log}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14354) Regression when using SELECT (EXISTS (...))
Lukas Eder created IGNITE-14354:
---
Summary: Regression when using SELECT (EXISTS (...))
Key: IGNITE-14354
URL: https://issues.apache.org/jira/browse/IGNITE-14354
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.10
Reporter: Lukas Eder
This worked as expected in 2.9.1:
{code:java}
CREATE TABLE t (i int PRIMARY KEY, j int);
SELECT (EXISTS (SELECT 1 FROM t WHERE t.i = 1));
{code}
In version 2.10, I'm getting:
{code:java}
SQL Error [1001] [42000]: Failed to parse query. Column "EXISTS1" not found;
SQL statement:
SELECT
(EXISTS1)
FROM SYSTEM_RANGE(1, 1) __Z0
LEFT OUTER JOIN PUBLIC.T __Z1
ON __Z1.I = 1 [42122-197]{code}
The workaround is to project an asterisk:
{code:java}
SELECT (EXISTS (SELECT * FROM t WHERE t.i = 1));{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14355) CDC application metrics
Nikolay Izhikov created IGNITE-14355: Summary: CDC application metrics Key: IGNITE-14355 URL: https://issues.apache.org/jira/browse/IGNITE-14355 Project: Ignite Issue Type: New Feature Reporter: Nikolay Izhikov CDC application should provide metrics so administrator be able to observe * consume GAP * consumer info * committed offset * etc We should try to reuse IgniteMetrics for this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14356) Regression when using derived table in LEFT JOIN
Lukas Eder created IGNITE-14356:
---
Summary: Regression when using derived table in LEFT JOIN
Key: IGNITE-14356
URL: https://issues.apache.org/jira/browse/IGNITE-14356
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.10
Reporter: Lukas Eder
This used to work in 2.9.1 and no longer does in 2.10.0:
{code:java}
CREATE TABLE t (i int PRIMARY KEY, j int);
INSERT INTO t VALUES (1, 1);
SELECT *
FROM t AS t1
LEFT JOIN (SELECT * FROM t WHERE false) AS t2
ON t1.i = t2.i
{code}
It should result in 1 row as the LEFT JOIN should have no effect, but the
result set is empty as if t2 were inner joined.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14357) Regression when using derived table in LEFT JOIN
Lukas Eder created IGNITE-14357:
---
Summary: Regression when using derived table in LEFT JOIN
Key: IGNITE-14357
URL: https://issues.apache.org/jira/browse/IGNITE-14357
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.10
Reporter: Lukas Eder
This used to work in 2.9.1 and no longer does in 2.10.0:
{code:java}
CREATE TABLE t (i int PRIMARY KEY, j int);
INSERT INTO t VALUES (1, 1);
SELECT *
FROM t AS t1
LEFT JOIN (SELECT * FROM t WHERE false) AS t2
ON t1.i = t2.i
{code}
It should result in 1 row as the LEFT JOIN should have no effect, but the
result set is empty as if t2 were inner joined.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14358) Regression when referencing aliased constant from derived table
Lukas Eder created IGNITE-14358:
---
Summary: Regression when referencing aliased constant from derived
table
Key: IGNITE-14358
URL: https://issues.apache.org/jira/browse/IGNITE-14358
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.10
Reporter: Lukas Eder
This used to work in 2.9.1 but no longer does in 2.10.0:
{code:java}
CREATE TABLE t (i int PRIMARY KEY, j int);
INSERT INTO t VALUES (1, 1);
SELECT u.x
FROM (
SELECT 1 AS x
FROM t
) u;
{code}
The error I'm getting is:
{noformat}
SQL Error [1001] [42000]: Failed to parse query. Column "U__Z0.X" not found;
SQL statement:
SELECT
U__Z0.X
FROM PUBLIC.T U__Z0 [42122-197]{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14359) Illegal reflective access in JDBC driver to field java.nio.Buffer.address
Lukas Eder created IGNITE-14359:
---
Summary: Illegal reflective access in JDBC driver to field
java.nio.Buffer.address
Key: IGNITE-14359
URL: https://issues.apache.org/jira/browse/IGNITE-14359
Project: Ignite
Issue Type: Bug
Components: jdbc
Affects Versions: 2.10
Reporter: Lukas Eder
When starting up an application using the Ignite JDBC driver, the following
warning is logged on JDK 11:
{code:java}
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by
org.apache.ignite.internal.util.GridUnsafe$2
(file:/C:/Users/lukas/.m2/repository/org/apache/ignite/ignite-core/2.10.0/ignite-core-2.10.0.jar)
to field java.nio.Buffer.address
WARNING: Please consider reporting this to the maintainers of
org.apache.ignite.internal.util.GridUnsafe$2
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release{code}
This was already the case in 2.9.1
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14360) Refactor FileLockHolder for reusage
Nikolay Izhikov created IGNITE-14360:
Summary: Refactor FileLockHolder for reusage
Key: IGNITE-14360
URL: https://issues.apache.org/jira/browse/IGNITE-14360
Project: Ignite
Issue Type: Improvement
Reporter: Nikolay Izhikov
CDC application needs to reuse FileLockHolder.
But for now, it's private class in \{{GridCacheDatabaseSharedManager}}
Minor refactoring required to be able to reuse it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14361) Add WhiteSpace after checkstyle rule
Nikolay Izhikov created IGNITE-14361:
Summary: Add WhiteSpace after checkstyle rule
Key: IGNITE-14361
URL: https://issues.apache.org/jira/browse/IGNITE-14361
Project: Ignite
Issue Type: Improvement
Reporter: Nikolay Izhikov
Right now checkstyle plugin don't check whitespace after rule that allows the
following violation of Ignite code style
{code:java}
finish.apply(p.id,msg.result(), msg.error());
{code}
Need to add the following rule to prevent it:
{code:xml}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
