[jira] [Commented] (IGNITE-11326) SQL: Common parsing logic
[ https://issues.apache.org/jira/browse/IGNITE-11326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769026#comment-16769026 ] Vladimir Ozerov commented on IGNITE-11326: -- First test run: https://ci.ignite.apache.org/viewLog.html?buildId=3091527 > SQL: Common parsing logic > - > > Key: IGNITE-11326 > URL: https://issues.apache.org/jira/browse/IGNITE-11326 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11318) Web console: add viewport meta tag
[ https://issues.apache.org/jira/browse/IGNITE-11318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-11318: -- Fix Version/s: 2.8 > Web console: add viewport meta tag > -- > > Key: IGNITE-11318 > URL: https://issues.apache.org/jira/browse/IGNITE-11318 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > Attachments: no viewport meta tag.png, with tag.png > > Time Spent: 26m > Remaining Estimate: 0h > > Web console does not scale automatically on tablets, so I propose to add > [viewport meta > tag|https://developer.mozilla.org/en-US/docs/Mozilla/Mobile/Viewport_meta_tag]. > Obviously, all the screens will have to be updated to look better in narrow > viewports. > Profile screen without the tag: > !no viewport meta tag.png! > With viewport meta tag: > !with tag.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11326) SQL: Common parsing logic
[ https://issues.apache.org/jira/browse/IGNITE-11326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-11326: - Ignite Flags: (was: Docs Required) > SQL: Common parsing logic > - > > Key: IGNITE-11326 > URL: https://issues.apache.org/jira/browse/IGNITE-11326 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11326) SQL: Common parsing logic
[ https://issues.apache.org/jira/browse/IGNITE-11326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-11326: - Fix Version/s: 2.8 > SQL: Common parsing logic > - > > Key: IGNITE-11326 > URL: https://issues.apache.org/jira/browse/IGNITE-11326 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11279) SQL: Remove H2's "prepared" from DML and local query plans
[
https://issues.apache.org/jira/browse/IGNITE-11279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768953#comment-16768953
]
Ignite TC Bot commented on IGNITE-11279:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}ZooKeeper (Discovery) 4{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3087312]]
{color:#d04437}Continuous Query 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3087226]]
* IgniteCacheQuerySelfTestSuite4:
CacheContinuousQueryFailoverAtomicReplicatedSelfTest.testOneBackup - 0,0% fails
in last 405 master runs.
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3087331buildTypeId=IgniteTests24Java8_RunAll]
> SQL: Remove H2's "prepared" from DML and local query plans
> --
>
> Key: IGNITE-11279
> URL: https://issues.apache.org/jira/browse/IGNITE-11279
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently it is only used to get the list of participating tables. Instead,
> we should encapsulate this information into {{ParsingResultDml}}. Streamer
> methods should use our own parser as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11327) Console error with progress line component
Alexander Kalinin created IGNITE-11327: -- Summary: Console error with progress line component Key: IGNITE-11327 URL: https://issues.apache.org/jira/browse/IGNITE-11327 Project: Ignite Issue Type: Bug Reporter: Alexander Kalinin Assignee: Alexander Kalinin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9799) Web console: remove unused code
[ https://issues.apache.org/jira/browse/IGNITE-9799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Kalinin reassigned IGNITE-9799: - Assignee: Pavel Konstantinov (was: Alexander Kalinin) [~pkonstantinov] Fixed background, please test. > Web console: remove unused code > --- > > Key: IGNITE-9799 > URL: https://issues.apache.org/jira/browse/IGNITE-9799 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Pavel Konstantinov >Priority: Minor > Attachments: screenshot-1.png > > Original Estimate: 2h > Time Spent: 2h 17m > Remaining Estimate: 0h > > There's a bunch of legacy/unused code and dependencies, let's remove those. > Here's an incomplete list, feel free to add more items: > # angular-cookies dependency > # angular-ui-carousel > # angular-motion > # jasmine-core -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10214) Web console: dependency to open source JDBC driver is not generated in the project's pom file
[ https://issues.apache.org/jira/browse/IGNITE-10214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov reassigned IGNITE-10214: - Assignee: Vasiliy Sisko (was: Alexey Kuznetsov) [~vsisko], please, fix code duplication with JDBC drivers download links. You may move them to some JSON file for example or to some global constant. > Web console: dependency to open source JDBC driver is not generated in the > project's pom file > - > > Key: IGNITE-10214 > URL: https://issues.apache.org/jira/browse/IGNITE-10214 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko >Priority: Major > Attachments: mysql-connector-java-8.0.13.jar, screenshot-1.png > > > Steps to reproduce: > # import caches from for example MySql DB > # check generated pom file -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9799) Web console: remove unused code
[ https://issues.apache.org/jira/browse/IGNITE-9799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768885#comment-16768885 ] Pavel Konstantinov edited comment on IGNITE-9799 at 2/15/19 2:33 AM: - All confirmation appear on the black background !screenshot-1.png! was (Author: pkonstantinov): !screenshot-1.png! > Web console: remove unused code > --- > > Key: IGNITE-9799 > URL: https://issues.apache.org/jira/browse/IGNITE-9799 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Pavel Konstantinov >Priority: Minor > Attachments: screenshot-1.png > > Original Estimate: 2h > Time Spent: 1h 47m > Remaining Estimate: 13m > > There's a bunch of legacy/unused code and dependencies, let's remove those. > Here's an incomplete list, feel free to add more items: > # angular-cookies dependency > # angular-ui-carousel > # angular-motion > # jasmine-core -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9799) Web console: remove unused code
[ https://issues.apache.org/jira/browse/IGNITE-9799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768885#comment-16768885 ] Pavel Konstantinov edited comment on IGNITE-9799 at 2/15/19 2:33 AM: - All confirmations appear on the black background !screenshot-1.png! was (Author: pkonstantinov): All confirmation appear on the black background !screenshot-1.png! > Web console: remove unused code > --- > > Key: IGNITE-9799 > URL: https://issues.apache.org/jira/browse/IGNITE-9799 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Pavel Konstantinov >Priority: Minor > Attachments: screenshot-1.png > > Original Estimate: 2h > Time Spent: 1h 47m > Remaining Estimate: 13m > > There's a bunch of legacy/unused code and dependencies, let's remove those. > Here's an incomplete list, feel free to add more items: > # angular-cookies dependency > # angular-ui-carousel > # angular-motion > # jasmine-core -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9799) Web console: remove unused code
[ https://issues.apache.org/jira/browse/IGNITE-9799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov updated IGNITE-9799: --- Attachment: screenshot-1.png > Web console: remove unused code > --- > > Key: IGNITE-9799 > URL: https://issues.apache.org/jira/browse/IGNITE-9799 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Pavel Konstantinov >Priority: Minor > Attachments: screenshot-1.png > > Original Estimate: 2h > Time Spent: 1h 47m > Remaining Estimate: 13m > > There's a bunch of legacy/unused code and dependencies, let's remove those. > Here's an incomplete list, feel free to add more items: > # angular-cookies dependency > # angular-ui-carousel > # angular-motion > # jasmine-core -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9799) Web console: remove unused code
[ https://issues.apache.org/jira/browse/IGNITE-9799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov reassigned IGNITE-9799: -- Assignee: Alexander Kalinin (was: Pavel Konstantinov) > Web console: remove unused code > --- > > Key: IGNITE-9799 > URL: https://issues.apache.org/jira/browse/IGNITE-9799 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexander Kalinin >Priority: Minor > Attachments: screenshot-1.png > > Original Estimate: 2h > Time Spent: 1h 47m > Remaining Estimate: 13m > > There's a bunch of legacy/unused code and dependencies, let's remove those. > Here's an incomplete list, feel free to add more items: > # angular-cookies dependency > # angular-ui-carousel > # angular-motion > # jasmine-core -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9799) Web console: remove unused code
[ https://issues.apache.org/jira/browse/IGNITE-9799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768885#comment-16768885 ] Pavel Konstantinov commented on IGNITE-9799: !screenshot-1.png! > Web console: remove unused code > --- > > Key: IGNITE-9799 > URL: https://issues.apache.org/jira/browse/IGNITE-9799 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Pavel Konstantinov >Priority: Minor > Attachments: screenshot-1.png > > Original Estimate: 2h > Time Spent: 1h 47m > Remaining Estimate: 13m > > There's a bunch of legacy/unused code and dependencies, let's remove those. > Here's an incomplete list, feel free to add more items: > # angular-cookies dependency > # angular-ui-carousel > # angular-motion > # jasmine-core -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5983) REST: Memory policy metrics should be available via REST.
[ https://issues.apache.org/jira/browse/IGNITE-5983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768838#comment-16768838 ] Roman Shtykh commented on IGNITE-5983: -- [~amashenkov] Thank you for reviewing and further improving the tests! > REST: Memory policy metrics should be available via REST. > - > > Key: IGNITE-5983 > URL: https://issues.apache.org/jira/browse/IGNITE-5983 > Project: Ignite > Issue Type: Improvement > Components: cache >Reporter: Andrew Mashenkov >Assignee: Roman Shtykh >Priority: Major > Fix For: 2.8 > > Time Spent: 40m > Remaining Estimate: 0h > > For now it is possible to get some of cache metrics via REST, but not memory > metrics. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5569) TCP Discovery SPI allows multiple NODE_JOINED / NODE_FAILED leading to a cluster DDoS
[ https://issues.apache.org/jira/browse/IGNITE-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768745#comment-16768745 ] Dmitriy Govorukhin commented on IGNITE-5569: [~sergey-chugunov] LGTM, thanks for the contribution! Merged to master. > TCP Discovery SPI allows multiple NODE_JOINED / NODE_FAILED leading to a > cluster DDoS > - > > Key: IGNITE-5569 > URL: https://issues.apache.org/jira/browse/IGNITE-5569 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.7 >Reporter: Alexey Goncharuk >Assignee: Sergey Chugunov >Priority: Major > Fix For: 2.8 > > Time Spent: 0.5h > Remaining Estimate: 0h > > A firewall configuration issue may effectively lead to a cluster DDoS. The > scheme is as follows: > 1) A node G joins the cluster, and a firewall rule forbids incoming > connection from cluster to this node > 2) Cluster successfully processes NodeAddedMesage and fires a discovery > NODE_JOINED event (not sure why?) > 4) The last node in the ring fails to connect to the newly joined node and > generates NODE_FAILED event > 5) Coordinator drops the connection, joining node attempts to connect again > The issues I see here: > 1) Neither coordinator nor joining node print out the reason why the joining > node failed / did not join. A slight hint (failed to send message to the next > node) is printed on the node with the largest order (the one that attempted > to close the ring), but the root cause (connection refused) is also not > printed > 2) The joining node attempts to connect to the cluster with the same node ID. > This violates an invariant we heavily rely on that once a node ID leaves a > cluster, this ID never comes back again > 3) Each discovery event leads to a partition exchange which blocks all cache > operations for a time interval equal at least to the full ring latency time. > If several nodes are started on a malicious host, this may lead to almost > full cluster degradation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-5569) TCP Discovery SPI allows multiple NODE_JOINED / NODE_FAILED leading to a cluster DDoS
[
https://issues.apache.org/jira/browse/IGNITE-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768740#comment-16768740
]
Ignite TC Bot commented on IGNITE-5569:
---
{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=3085164buildTypeId=IgniteTests24Java8_RunAll]
> TCP Discovery SPI allows multiple NODE_JOINED / NODE_FAILED leading to a
> cluster DDoS
> -
>
> Key: IGNITE-5569
> URL: https://issues.apache.org/jira/browse/IGNITE-5569
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 1.7
>Reporter: Alexey Goncharuk
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> A firewall configuration issue may effectively lead to a cluster DDoS. The
> scheme is as follows:
> 1) A node G joins the cluster, and a firewall rule forbids incoming
> connection from cluster to this node
> 2) Cluster successfully processes NodeAddedMesage and fires a discovery
> NODE_JOINED event (not sure why?)
> 4) The last node in the ring fails to connect to the newly joined node and
> generates NODE_FAILED event
> 5) Coordinator drops the connection, joining node attempts to connect again
> The issues I see here:
> 1) Neither coordinator nor joining node print out the reason why the joining
> node failed / did not join. A slight hint (failed to send message to the next
> node) is printed on the node with the largest order (the one that attempted
> to close the ring), but the root cause (connection refused) is also not
> printed
> 2) The joining node attempts to connect to the cluster with the same node ID.
> This violates an invariant we heavily rely on that once a node ID leaves a
> cluster, this ID never comes back again
> 3) Each discovery event leads to a partition exchange which blocks all cache
> operations for a time interval equal at least to the full ring latency time.
> If several nodes are started on a malicious host, this may lead to almost
> full cluster degradation
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11326) SQL: Common parsing logic
Vladimir Ozerov created IGNITE-11326: Summary: SQL: Common parsing logic Key: IGNITE-11326 URL: https://issues.apache.org/jira/browse/IGNITE-11326 Project: Ignite Issue Type: Task Components: sql Reporter: Vladimir Ozerov Assignee: Vladimir Ozerov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6792) SQL fields query for huge replicated cache gives not correct count if rebalancing is in progress
[ https://issues.apache.org/jira/browse/IGNITE-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6792: Labels: (was: sql-stability) > SQL fields query for huge replicated cache gives not correct count if > rebalancing is in progress > > > Key: IGNITE-6792 > URL: https://issues.apache.org/jira/browse/IGNITE-6792 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.3 >Reporter: Dmitriy Pavlov >Assignee: Alexey Goncharuk >Priority: Major > Attachments: GridReplicatedCacheRebalancingWithPdsEnabled.java > > > According to recent user-list question > http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-3-replicated-cache-lost-data-after-restart-cluster-nodes-with-persistence-enabled-td17612.html > > reproducing test was created. > This test creates one grid and loads 1 000 000 records to replicated cache. > Persistent store is enabled. > Then second grid is connected and rebalancing is started. > We don't wait to rebalance is completely finished and run > select count(*) from Organization > and scan query. > Results returned by count in second node is less than initially loaded data > amount > At grid 0: Cache .size(): [512149], sql fields query count is [100], sql > scan query count is [100] > At grid 1: Cache .size(): [512149], sql fields query count is [44218], sql > scan query count is [44219] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda closed IGNITE-11155.
> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -
>
> Key: IGNITE-11155
> URL: https://issues.apache.org/jira/browse/IGNITE-11155
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Attachments: image.png, start-java11-2.png, start-java11.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Ignite examples or using Ignite Embedded mode (using direct
> Ignition.start() call from a user IDE), may fail with exceptions for JDKs
> newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to
> output message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled.
> See
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
> Ignite in embedded mode will show how to set up Application configuration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768631#comment-16768631
]
Denis Magda commented on IGNITE-11155:
--
Ah, I see, you mean that the exception will be thrown as soon as the JVM
process gets started. Understood, closing the ticket.
> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -
>
> Key: IGNITE-11155
> URL: https://issues.apache.org/jira/browse/IGNITE-11155
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Attachments: image.png, start-java11-2.png, start-java11.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Ignite examples or using Ignite Embedded mode (using direct
> Ignition.start() call from a user IDE), may fail with exceptions for JDKs
> newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to
> output message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled.
> See
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
> Ignite in embedded mode will show how to set up Application configuration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda resolved IGNITE-11155.
--
Resolution: Fixed
> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -
>
> Key: IGNITE-11155
> URL: https://issues.apache.org/jira/browse/IGNITE-11155
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Attachments: image.png, start-java11-2.png, start-java11.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Ignite examples or using Ignite Embedded mode (using direct
> Ignition.start() call from a user IDE), may fail with exceptions for JDKs
> newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to
> output message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled.
> See
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
> Ignite in embedded mode will show how to set up Application configuration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-11155:
-
Attachment: image.png
> Add JVM options analysis to Ignition.start() or handle and comment exceptions
> -
>
> Key: IGNITE-11155
> URL: https://issues.apache.org/jira/browse/IGNITE-11155
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Attachments: image.png, start-java11-2.png, start-java11.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In Ignite examples or using Ignite Embedded mode (using direct
> Ignition.start() call from a user IDE), may fail with exceptions for JDKs
> newer than 8.
> It may confuse the user. Instead of just logging an exception it is better to
> output message with advice on how to fix it. E.g.
> {noformat}
> Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled.
> See
> https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
> for more info
> {noformat}
> Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
> Ignite in embedded mode will show how to set up Application configuration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7822) SQL Query with union and left join produces "Column not found" error
[ https://issues.apache.org/jira/browse/IGNITE-7822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-7822: --- Assignee: (was: Taras Ledkov) > SQL Query with union and left join produces "Column not found" error > > > Key: IGNITE-7822 > URL: https://issues.apache.org/jira/browse/IGNITE-7822 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.1, 2.3 >Reporter: Pavel Vinokurov >Priority: Major > > > > Initial script: > > CREATE TABLE Person (id INTEGER PRIMARY KEY, company_id INTEGER, salary > DECIMAL); > CREATE TABLE Company (id INTEGER PRIMARY KEY, name VARCHAR); > CREATE TABLE Company_Value (id INTEGER PRIMARY KEY, company_id INTEGER, > market_value DECIMAL); > INSERT INTO Person (id, company_id, salary) VALUES (1, 1, 100), (2, 2, 200), > (3, 3, 300); > INSERT INTO Company (id, name) VALUES (1, 'n1'), (2, 'n2'), (3, 'n3'); > INSERT INTO Company_Value (id, company_id, market_value) VALUES (1, 1, > 1), (2, 2, 2), (3, 3, 3); CREATE TABLE Address (id INTEGER > PRIMARY KEY, person_id INTEGER, city VARCHAR);INSERT INTO Person (id, > company_id, salary) VALUES (1, 1, 100), (2, 2, 200), (3, 3, 300);INSERT INTO > Address (id, person_id, city) VALUES (1, 1, 'san francisco'), (2, 2, > 'paris'), (3, 3, 'new york');INSERT INTO Company (id, name) VALUES (1, 'n1'), > (2, 'n2'), (3, 'n3');INSERT INTO Company_Value (id, company_id, market_value) > VALUES (1, 1, 1), (2, 2, 2), (3, 3, 3); > > Query: > SELECT a.idFROM (SELECT p1.id as pid, p1.salary, p1.company_id > FROM Person p1 WHERE p1.id = 1 UNION SELECT p2.id as pid, > p2.salary, p2.company_id FROM Person p2 WHERE p2.id = 2) p LEFT > JOIN Company c ON p.company_id = c.id LEFT JOIN Company_Value cv ON c.id = > cv.company_id LEFT JOIN Address a ON a.person_id = p.pid; > > Result: > Exception:Caused by: org.h2.jdbc.JdbcSQLException: Column "P__Z2.ID" not > found; SQL statement:SELECTC__Z3.ID __C2_0FROM PUBLIC.COMPANY C__Z3 LEFT > OUTER JOIN PUBLIC.COMPANY_VALUE CV__Z4 ON C__Z3.ID = CV__Z4.COMPANY_ID LEFT > OUTER JOIN PUBLIC.ADDRESS A__Z5 ON A__Z5.PERSON_ID = P__Z2.IDORDER BY 1 > [42122-195] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9379) Ignite node hangs after OOM in a thread from thin client thread pool
[ https://issues.apache.org/jira/browse/IGNITE-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-9379: --- Assignee: (was: Taras Ledkov) > Ignite node hangs after OOM in a thread from thin client thread pool > > > Key: IGNITE-9379 > URL: https://issues.apache.org/jira/browse/IGNITE-9379 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.6 >Reporter: Taras Ledkov >Priority: Major > Fix For: 2.8 > > > OOM exception handler isn't set up for thin client thread pool. > The issue is described in details at the [dev > list|http://apache-ignite-evelopers.2346864.n4.nabble.com/Binary-Client-Protocol-client-hangs-in-case-of-OOM-on-server-td34224.html]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6792) SQL fields query for huge replicated cache gives not correct count if rebalancing is in progress
[ https://issues.apache.org/jira/browse/IGNITE-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6792: Component/s: (was: sql) cache > SQL fields query for huge replicated cache gives not correct count if > rebalancing is in progress > > > Key: IGNITE-6792 > URL: https://issues.apache.org/jira/browse/IGNITE-6792 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.3 >Reporter: Dmitriy Pavlov >Assignee: Alexey Goncharuk >Priority: Major > Labels: sql-stability > Attachments: GridReplicatedCacheRebalancingWithPdsEnabled.java > > > According to recent user-list question > http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-3-replicated-cache-lost-data-after-restart-cluster-nodes-with-persistence-enabled-td17612.html > > reproducing test was created. > This test creates one grid and loads 1 000 000 records to replicated cache. > Persistent store is enabled. > Then second grid is connected and rebalancing is started. > We don't wait to rebalance is completely finished and run > select count(*) from Organization > and scan query. > Results returned by count in second node is less than initially loaded data > amount > At grid 0: Cache .size(): [512149], sql fields query count is [100], sql > scan query count is [100] > At grid 1: Cache .size(): [512149], sql fields query count is [44218], sql > scan query count is [44219] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6792) SQL fields query for huge replicated cache gives not correct count if rebalancing is in progress
[ https://issues.apache.org/jira/browse/IGNITE-6792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768605#comment-16768605 ] Vladimir Ozerov commented on IGNITE-6792: - Changed componente to "cache" since the problem is reproducible for both SQL and scan queries and hence is outside of SQL logic. > SQL fields query for huge replicated cache gives not correct count if > rebalancing is in progress > > > Key: IGNITE-6792 > URL: https://issues.apache.org/jira/browse/IGNITE-6792 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.3 >Reporter: Dmitriy Pavlov >Assignee: Alexey Goncharuk >Priority: Major > Attachments: GridReplicatedCacheRebalancingWithPdsEnabled.java > > > According to recent user-list question > http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-3-replicated-cache-lost-data-after-restart-cluster-nodes-with-persistence-enabled-td17612.html > > reproducing test was created. > This test creates one grid and loads 1 000 000 records to replicated cache. > Persistent store is enabled. > Then second grid is connected and rebalancing is started. > We don't wait to rebalance is completely finished and run > select count(*) from Organization > and scan query. > Results returned by count in second node is less than initially loaded data > amount > At grid 0: Cache .size(): [512149], sql fields query count is [100], sql > scan query count is [100] > At grid 1: Cache .size(): [512149], sql fields query count is [44218], sql > scan query count is [44219] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10693) MVCC TX: Random server restart tests became failed
[ https://issues.apache.org/jira/browse/IGNITE-10693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-10693: - Component/s: (was: sql) > MVCC TX: Random server restart tests became failed > -- > > Key: IGNITE-10693 > URL: https://issues.apache.org/jira/browse/IGNITE-10693 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Igor Seliverstov >Assignee: Igor Seliverstov >Priority: Major > Labels: failover, mvcc_stabilization_stage_1 > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > [one|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7945125576049372508=%3Cdefault%3E=testDetails], > > [two|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=8412476034648229784=%3Cdefault%3E=testDetails], > > [three|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=254244004184327163=%3Cdefault%3E=testDetails], > all these tests became failed after IGNITE-9630 has been merged to master. > Seems there is an issue in partition calculating mechanism on unstable > topology. I suppose the algorithm uses partitions on nodes just become > primary while the partitions are in moving state. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11279) SQL: Remove H2's "prepared" from DML and local query plans
[
https://issues.apache.org/jira/browse/IGNITE-11279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768601#comment-16768601
]
Vladimir Ozerov commented on IGNITE-11279:
--
Test results were bad because I removed "start missing caches" code. Reverted
back. Re-run: https://ci.ignite.apache.org/viewQueued.html?itemId=3087331
> SQL: Remove H2's "prepared" from DML and local query plans
> --
>
> Key: IGNITE-11279
> URL: https://issues.apache.org/jira/browse/IGNITE-11279
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently it is only used to get the list of participating tables. Instead,
> we should encapsulate this information into {{ParsingResultDml}}. Streamer
> methods should use our own parser as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11325) SQL: Single place to start missing caches (H2Utils.checkAndStartNotStartedCache)
[
https://issues.apache.org/jira/browse/IGNITE-11325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-11325:
-
Ignite Flags: (was: Docs Required)
> SQL: Single place to start missing caches
> (H2Utils.checkAndStartNotStartedCache)
>
>
> Key: IGNITE-11325
> URL: https://issues.apache.org/jira/browse/IGNITE-11325
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Priority: Major
> Fix For: 2.8
>
>
> We need to start missing caches for the given SELECT/DML statement because we
> need affinity info during query planning which is only available for started
> caches.
> We need to do the following:
> # Move the method {{H2Utils.checkAndStartNotStartedCache}} to some common
> place, e.g. parser, so that it has one and only one usage all over the code
> base
> # Make sure that this method doesn't produce multiple network hops: missing
> caches should be started in a single request if possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11325) SQL: Single place to start missing caches (H2Utils.checkAndStartNotStartedCache)
Vladimir Ozerov created IGNITE-11325:
Summary: SQL: Single place to start missing caches
(H2Utils.checkAndStartNotStartedCache)
Key: IGNITE-11325
URL: https://issues.apache.org/jira/browse/IGNITE-11325
Project: Ignite
Issue Type: Task
Components: sql
Reporter: Vladimir Ozerov
Fix For: 2.8
We need to start missing caches for the given SELECT/DML statement because we
need affinity info during query planning which is only available for started
caches.
We need to do the following:
# Move the method {{H2Utils.checkAndStartNotStartedCache}} to some common
place, e.g. parser, so that it has one and only one usage all over the code base
# Make sure that this method doesn't produce multiple network hops: missing
caches should be started in a single request if possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11324) Getting Started Doc openweather API has changed
Greg created IGNITE-11324: - Summary: Getting Started Doc openweather API has changed Key: IGNITE-11324 URL: https://issues.apache.org/jira/browse/IGNITE-11324 Project: Ignite Issue Type: Task Components: documentation Affects Versions: 2.7 Environment: Ignite 2.7 Java 8.0.201 MacOS 10.14.3 Reporter: Greg Fix For: 2.8 In the Ignite Getting Started Guide ([https://apacheignite.readme.io/docs/getting-started)] the tutorial called First Ignite Grid Application makes use of a public API on samples.openweathermap.org. This URL is no longer valid and the new URL pattern is [http://api.openweathermap.org/.|http://api.openweathermap.org/] If the user calls getCurrentTemperature in WeatherServiceImpl, they will get the following error Weather forecast in London:301 Moved Permanently301 Moved Permanentlyopenresty/1.9.7.1 Please use the new URL for WEATHER_URL in WeatherServiceImpl private static final String WEATHER_URL = "http://api.openweathermap.org/data/2.5/weather?;; -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (IGNITE-11279) SQL: Remove H2's "prepared" from DML and local query plans
[
https://issues.apache.org/jira/browse/IGNITE-11279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-11279:
-
Comment: was deleted
(was: {panel:title=- Run :: IntelliJ IDEA Inspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *- Run :: IntelliJ IDEA Inspections*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3084866buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections])
> SQL: Remove H2's "prepared" from DML and local query plans
> --
>
> Key: IGNITE-11279
> URL: https://issues.apache.org/jira/browse/IGNITE-11279
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently it is only used to get the list of participating tables. Instead,
> we should encapsulate this information into {{ParsingResultDml}}. Streamer
> methods should use our own parser as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11279) SQL: Remove H2's "prepared" from DML and local query plans
[
https://issues.apache.org/jira/browse/IGNITE-11279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768580#comment-16768580
]
Ignite TC Bot commented on IGNITE-11279:
{panel:title=- Run :: IntelliJ IDEA Inspections: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *- Run :: IntelliJ IDEA Inspections*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3084866buildTypeId=IgniteTests24Java8_RunIntelliJIdeaInspections]
> SQL: Remove H2's "prepared" from DML and local query plans
> --
>
> Key: IGNITE-11279
> URL: https://issues.apache.org/jira/browse/IGNITE-11279
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently it is only used to get the list of participating tables. Instead,
> we should encapsulate this information into {{ParsingResultDml}}. Streamer
> methods should use our own parser as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11310) SQL: Remove special interaction between query parallelism and distributed joins
[ https://issues.apache.org/jira/browse/IGNITE-11310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768576#comment-16768576 ] Vladimir Ozerov commented on IGNITE-11310: -- All failures are unrelated. Merged. > SQL: Remove special interaction between query parallelism and distributed > joins > --- > > Key: IGNITE-11310 > URL: https://issues.apache.org/jira/browse/IGNITE-11310 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Fix For: 2.8 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently we enable so-called "local distributed joins" when query is > executed locally with enabled parallelism. This behavior is not needed and > needs to be removed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11310) SQL: Remove special interaction between query parallelism and distributed joins
[
https://issues.apache.org/jira/browse/IGNITE-11310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16768563#comment-16768563
]
Ignite TC Bot commented on IGNITE-11310:
{panel:title=-- Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 7{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3084680]]
* IgniteCacheTestSuite7:
TxRollbackAsyncWithPersistenceTest.testSynchronousRollback - 0,0% fails in last
417 master runs.
{color:#d04437}Cache (Failover) 3{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=3084668]]
* IgniteCacheFailoverTestSuite3:
IgniteCachePutRetryTransactionalSelfTest.testExplicitTransactionRetriesSingleValue
- 0,2% fails in last 414 master runs.
{color:#d04437}Thin client: Python{color} [[tests 95 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=3084703]]
*
tests.test_cache_class.test_cache_binary_get_put[None-None-localhost-_SSLMethod_PROTOCOL_TLSv1_1-None-None-10800-None-False-ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+HIGH:DH+HIGH:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+HIGH:RSA+3DES:!aNULL:!eNULL:!MD5-0-None]
*
tests.test_cache_class.test_cache_get_put[None-None-localhost-_SSLMethod_PROTOCOL_TLSv1_1-None-None-10800-None-False-ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+HIGH:DH+HIGH:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+HIGH:RSA+3DES:!aNULL:!eNULL:!MD5-0-None]
*
tests.test_cache_class.test_cache_scan[None-None-localhost-_SSLMethod_PROTOCOL_TLSv1_1-None-None-10800-None-False-ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+HIGH:DH+HIGH:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+HIGH:RSA+3DES:!aNULL:!eNULL:!MD5-0-None-1]
*
tests.test_cache_class.test_get_binary_type[None-None-localhost-_SSLMethod_PROTOCOL_TLSv1_1-None-None-10800-None-False-ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+HIGH:DH+HIGH:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+HIGH:RSA+3DES:!aNULL:!eNULL:!MD5-0-None]
*
tests.test_cache_class_sql.test_sql_fields[None-None-localhost-_SSLMethod_PROTOCOL_TLSv1_1-None-None-10800-None-False-ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+HIGH:DH+HIGH:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+HIGH:RSA+3DES:!aNULL:!eNULL:!MD5-0-None-1]
*
tests.test_cache_class.test_get_and_put_if_absent[None-None-localhost-_SSLMethod_PROTOCOL_TLSv1_1-None-None-10800-None-False-ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+HIGH:DH+HIGH:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+HIGH:RSA+3DES:!aNULL:!eNULL:!MD5-0-None]
*
tests.test_cache_config.test_get_configuration[None-None-localhost-_SSLMethod_PROTOCOL_TLSv1_1-None-None-10800-None-False-ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+HIGH:DH+HIGH:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+HIGH:RSA+3DES:!aNULL:!eNULL:!MD5-0-None]
*
tests.test_cache_class_sql.test_sql[None-None-localhost-_SSLMethod_PROTOCOL_TLSv1_1-None-None-10800-None-False-ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+HIGH:DH+HIGH:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+HIGH:RSA+3DES:!aNULL:!eNULL:!MD5-0-None-1]
*
tests.test_binary.test_sql_write_as_binary[None-None-localhost-_SSLMethod_PROTOCOL_TLSv1_1-None-None-10800-None-False-ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+HIGH:DH+HIGH:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+HIGH:RSA+3DES:!aNULL:!eNULL:!MD5-0-None]
*
tests.test_binary.test_sql_read_as_binary[None-None-localhost-_SSLMethod_PROTOCOL_TLSv1_1-None-None-10800-None-False-ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+HIGH:DH+HIGH:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+HIGH:RSA+3DES:!aNULL:!eNULL:!MD5-0-None]
*
tests.test_binary.test_add_schema_to_binary_object[None-None-localhost-_SSLMethod_PROTOCOL_TLSv1_1-None-None-10800-None-False-ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+HIGH:DH+HIGH:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+HIGH:RSA+3DES:!aNULL:!eNULL:!MD5-0-None]
*
tests.test_binary.test_nested_binary_objects[None-None-localhost-_SSLMethod_PROTOCOL_TLSv1_1-None-None-10800-None-False-ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+HIGH:DH+HIGH:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+HIGH:RSA+3DES:!aNULL:!eNULL:!MD5-0-None]
*
tests.test_cache_class.test_cache_remove[None-None-localhost-_SSLMethod_PROTOCOL_TLSv1_1-None-None-10800-None-False-ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+HIGH:DH+HIGH:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+HIGH:RSA+3DES:!aNULL:!eNULL:!MD5-0-None]
*
tests.test_cache_class.test_cache_create[None-None-localhost-_SSLMethod_PROTOCOL_TLSv1_1-None-None-10800-None-False-ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+HIGH:DH+HIGH:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+HIGH:RSA+3DES:!aNULL:!eNULL:!MD5-0-None]
*
[jira] [Resolved] (IGNITE-7602) SQL COPY: add tests for file reading and JDBC connection failures
[ https://issues.apache.org/jira/browse/IGNITE-7602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-7602. - Resolution: Won't Fix Not relevant at the moment. > SQL COPY: add tests for file reading and JDBC connection failures > - > > Key: IGNITE-7602 > URL: https://issues.apache.org/jira/browse/IGNITE-7602 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4 >Reporter: Kirill Shirokov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-6293) SQL: Support FOREIGN KEY constraint
[
https://issues.apache.org/jira/browse/IGNITE-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov closed IGNITE-6293.
---
> SQL: Support FOREIGN KEY constraint
> ---
>
> Key: IGNITE-6293
> URL: https://issues.apache.org/jira/browse/IGNITE-6293
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Priority: Major
> Labels: sql-engine
>
> We need to support {{FOREIGN KEY}} constraint. This is a complex, though
> achievable thing.
> 1) We need to check constraint during inserts and updates (from both SQL and
> cache API).
> 2) We need to support different modes of {{CASCADE}} actions - "remove", "set
> null".
> In general case it would require distributed operations, possibly with
> predicates. However, as a first iteration, it would be enough to support FK
> only for co-located data. In this case everything could be done locally.
> *Important*
> Implementation of FK typically depends heavily on underlying MVCC and
> transaction subsystems. That said, we should implement it after MVCC and
> transactional SQL.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7732) SQL COPY: ODBC support
[ https://issues.apache.org/jira/browse/IGNITE-7732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-7732: Component/s: (was: sql) > SQL COPY: ODBC support > -- > > Key: IGNITE-7732 > URL: https://issues.apache.org/jira/browse/IGNITE-7732 > Project: Ignite > Issue Type: Task > Components: odbc >Reporter: Vladimir Ozerov >Assignee: Igor Sapego >Priority: Major > > Support COPY command for ODBC driver in the same way it is done for JDBC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8598) SQL: ability to control partition pruning with explicit affinity column definition
[
https://issues.apache.org/jira/browse/IGNITE-8598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-8598.
-
Resolution: Duplicate
> SQL: ability to control partition pruning with explicit affinity column
> definition
> --
>
> Key: IGNITE-8598
> URL: https://issues.apache.org/jira/browse/IGNITE-8598
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Priority: Major
>
> Affinity functions are applicable to keys only. Sometimes users may have
> complex affinity calculation logic, so that partition pruning optimization is
> not applicable. E.g. this custom {{AffinityKeyMapper}}. However, there is a
> chance that partition could be calculated from some attribute of {{value}}.
> It would be nice to force our engine to treat some attribute as affinity key
> even though it is not marked as {{AffinityKeyMapped}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-7601) SQL COPY: add tests for implicit columns (_key, _val, _ver)
[ https://issues.apache.org/jira/browse/IGNITE-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-7601. - Resolution: Won't Fix Not relevant at the moment. > SQL COPY: add tests for implicit columns (_key, _val, _ver) > --- > > Key: IGNITE-7601 > URL: https://issues.apache.org/jira/browse/IGNITE-7601 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4 >Reporter: Kirill Shirokov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7724) SQL COPY: network performance improvements
[ https://issues.apache.org/jira/browse/IGNITE-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-7724. - Resolution: Won't Fix Not relevant at the moment. > SQL COPY: network performance improvements > -- > > Key: IGNITE-7724 > URL: https://issues.apache.org/jira/browse/IGNITE-7724 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.3, 2.4, 2.5 >Reporter: Kirill Shirokov >Assignee: Kirill Shirokov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7681) SQL COPY: local performance improvements
[ https://issues.apache.org/jira/browse/IGNITE-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-7681. --- > SQL COPY: local performance improvements > > > Key: IGNITE-7681 > URL: https://issues.apache.org/jira/browse/IGNITE-7681 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4, 2.5 >Reporter: Kirill Shirokov >Priority: Major > Attachments: ignite-7681-cache-putall-processor.diff, > ignite-7681-perf-test.diff > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8402) Long running transaction JMX
[ https://issues.apache.org/jira/browse/IGNITE-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-8402. --- > Long running transaction JMX > > > Key: IGNITE-8402 > URL: https://issues.apache.org/jira/browse/IGNITE-8402 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4 >Reporter: Ivan Kapralov >Priority: Major > > Facing necessity in Long Running Transactions JMX metric implementation. > Needed: transaction start time, node ID, duration, cache full qualified name, > originator ID. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7724) SQL COPY: network performance improvements
[ https://issues.apache.org/jira/browse/IGNITE-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-7724: --- Assignee: (was: Kirill Shirokov) > SQL COPY: network performance improvements > -- > > Key: IGNITE-7724 > URL: https://issues.apache.org/jira/browse/IGNITE-7724 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.3, 2.4, 2.5 >Reporter: Kirill Shirokov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7601) SQL COPY: add tests for implicit columns (_key, _val, _ver)
[ https://issues.apache.org/jira/browse/IGNITE-7601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-7601. --- > SQL COPY: add tests for implicit columns (_key, _val, _ver) > --- > > Key: IGNITE-7601 > URL: https://issues.apache.org/jira/browse/IGNITE-7601 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4 >Reporter: Kirill Shirokov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11323) Reduce boilerplate "System.setProperty" code in tests
[
https://issues.apache.org/jira/browse/IGNITE-11323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-11323:
---
Description:
There are many examples in tests where some property gets new value in
"beforeTestsStarted"/"beforeTest"/"beginning of test method" and then gets its
previous value in "afterTestsStopped"/"afterTest"/"finally block of test
method". This approach leads to excessive code that can be avoided.
I suggest implementing annotation "WithSystemProperty" (name is the subject to
discussion) that will allow us to write this:
{code:java}
@Test
@WithSystemProperty(key = IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK, value =
"true")
public void testSkipCheckConsistencyFlagEnabled() throws Exception {
...
}
{code}
instead of this:
{code:java}
@Test
public void testSkipCheckConsistencyFlagEnabled() throws Exception {
String backup =
System.setProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK, "true");
try {
...
}
finally {
if (backup != null)
System.setProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK,
backup);
else
System.clearProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK);
}
}
{code}
There also has to be ability to use this annotation on test class so new value
of system properties will be used in all of its test methods.
was:
There are many examples in tests where some property gets new value in
"beforeTestsStarted"/"beforeTest"/"beginning of test method" and then gets its
previous value in "afterTestsStopped"/"afterTest"/"finally block of test
method". This approach leads to excessive code that can be avoided.
I suggest implementing annotation "WithSystemProperty" (name is the subject to
discussion) that will allow us to write this:
{code:java}
@Test
@WithSystemProperty(key = IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK, value =
"true")
public void testSkipCheckConsistencyFlagEnabled() throws Exception {
...
}
{code}
instead of this:
{code:java}
@Test
public void testSkipCheckConsistencyFlagEnabled() throws Exception {
String backup =
System.setProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK, "true");
try {
...
}
finally {
if (backup != null)
System.setProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK,
backup);
else
System.clearProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK);
}
}
{code}
There's also has to be ability to use this annotation on test class so new
value of system properties will be used in all of its test methods.
> Reduce boilerplate "System.setProperty" code in tests
> -
>
> Key: IGNITE-11323
> URL: https://issues.apache.org/jira/browse/IGNITE-11323
> Project: Ignite
> Issue Type: Test
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
>
> There are many examples in tests where some property gets new value in
> "beforeTestsStarted"/"beforeTest"/"beginning of test method" and then gets
> its previous value in "afterTestsStopped"/"afterTest"/"finally block of test
> method". This approach leads to excessive code that can be avoided.
> I suggest implementing annotation "WithSystemProperty" (name is the subject
> to discussion) that will allow us to write this:
> {code:java}
> @Test
> @WithSystemProperty(key = IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK, value
> = "true")
> public void testSkipCheckConsistencyFlagEnabled() throws Exception {
> ...
> }
> {code}
> instead of this:
> {code:java}
> @Test
> public void testSkipCheckConsistencyFlagEnabled() throws Exception {
> String backup =
> System.setProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK, "true");
> try {
> ...
> }
> finally {
> if (backup != null)
> System.setProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK,
> backup);
> else
> System.clearProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK);
> }
> }
> {code}
>
> There also has to be ability to use this annotation on test class so new
> value of system properties will be used in all of its test methods.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-6903) Implement new JMX metrics for Indexing
[ https://issues.apache.org/jira/browse/IGNITE-6903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-6903. --- > Implement new JMX metrics for Indexing > -- > > Key: IGNITE-6903 > URL: https://issues.apache.org/jira/browse/IGNITE-6903 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Anton Vinogradov >Priority: Critical > Labels: iep-6, important > Fix For: 2.8 > > > These additional metrics and methods should be implemented: > - Space occupied by indexes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7724) SQL COPY: network performance improvements
[ https://issues.apache.org/jira/browse/IGNITE-7724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-7724. --- > SQL COPY: network performance improvements > -- > > Key: IGNITE-7724 > URL: https://issues.apache.org/jira/browse/IGNITE-7724 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.3, 2.4, 2.5 >Reporter: Kirill Shirokov >Assignee: Kirill Shirokov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7661) SQL COPY: provide more tests for national Unicode characters (including surrogates and 0x10000+ range)
[ https://issues.apache.org/jira/browse/IGNITE-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-7661. - Resolution: Won't Fix Not relevant at the moment. > SQL COPY: provide more tests for national Unicode characters (including > surrogates and 0x1+ range) > -- > > Key: IGNITE-7661 > URL: https://issues.apache.org/jira/browse/IGNITE-7661 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.5 >Reporter: Kirill Shirokov >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7681) SQL COPY: local performance improvements
[ https://issues.apache.org/jira/browse/IGNITE-7681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-7681. - Resolution: Won't Fix Not relevant at the moment. > SQL COPY: local performance improvements > > > Key: IGNITE-7681 > URL: https://issues.apache.org/jira/browse/IGNITE-7681 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4, 2.5 >Reporter: Kirill Shirokov >Priority: Major > Attachments: ignite-7681-cache-putall-processor.diff, > ignite-7681-perf-test.diff > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7605) SQL COPY: add more SQL parser tests for positive scenarios
[ https://issues.apache.org/jira/browse/IGNITE-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-7605. --- > SQL COPY: add more SQL parser tests for positive scenarios > -- > > Key: IGNITE-7605 > URL: https://issues.apache.org/jira/browse/IGNITE-7605 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4 >Reporter: Kirill Shirokov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7602) SQL COPY: add tests for file reading and JDBC connection failures
[ https://issues.apache.org/jira/browse/IGNITE-7602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-7602. --- > SQL COPY: add tests for file reading and JDBC connection failures > - > > Key: IGNITE-7602 > URL: https://issues.apache.org/jira/browse/IGNITE-7602 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4 >Reporter: Kirill Shirokov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7605) SQL COPY: add more SQL parser tests for positive scenarios
[ https://issues.apache.org/jira/browse/IGNITE-7605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-7605. - Resolution: Won't Fix Not relevant at the moment. > SQL COPY: add more SQL parser tests for positive scenarios > -- > > Key: IGNITE-7605 > URL: https://issues.apache.org/jira/browse/IGNITE-7605 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4 >Reporter: Kirill Shirokov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7661) SQL COPY: provide more tests for national Unicode characters (including surrogates and 0x10000+ range)
[ https://issues.apache.org/jira/browse/IGNITE-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-7661. --- > SQL COPY: provide more tests for national Unicode characters (including > surrogates and 0x1+ range) > -- > > Key: IGNITE-7661 > URL: https://issues.apache.org/jira/browse/IGNITE-7661 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.5 >Reporter: Kirill Shirokov >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-4575) Implement wrapper for enums based on H2 user value type
[ https://issues.apache.org/jira/browse/IGNITE-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-4575. --- > Implement wrapper for enums based on H2 user value type > --- > > Key: IGNITE-4575 > URL: https://issues.apache.org/jira/browse/IGNITE-4575 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Alexander Paschenko >Priority: Major > Labels: sql-engine > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8591) SQL: Sort links on index pages in physical page order before row access
[ https://issues.apache.org/jira/browse/IGNITE-8591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-8591. --- > SQL: Sort links on index pages in physical page order before row access > --- > > Key: IGNITE-8591 > URL: https://issues.apache.org/jira/browse/IGNITE-8591 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.5 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Labels: performance > > When index page match condition, we eagerly read all matched data rows. This > leads to a number of random disk reads.as Ignite use heap-organized storage. > We can pre-sort all matched row links in accordance to their physical > location, and then read them in batch. This will give us two important > advantages: > 1) Data reads will be more sequential, this is especially important for HDDs > 2) This could decrease number of page reads in case of dense data placement, > because there will be less evictions. > In future we should expand this optimization to several index pages in the > same way it is done in major databases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8600) SQL: lazy row materialization
[ https://issues.apache.org/jira/browse/IGNITE-8600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-8600. --- > SQL: lazy row materialization > - > > Key: IGNITE-8600 > URL: https://issues.apache.org/jira/browse/IGNITE-8600 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.5 >Reporter: Vladimir Ozerov >Priority: Major > Labels: performance > > Currently our index cursor materializes rows as soon as they are encountered > in an index page. This is necessary to protect ourselves from concurrent data > modification. However, materialized rows might be filtered out later due to > additional filters. In addition, there is a chance that only indexed fields > is needed by query. > We can do the following: > 1) Introduce new mode that will return partially materialized rows, with only > inline index fields initialized. When some non-initialized attribute is > requested, we go to data page and materialize the whole row > 2) Enable this mode for MVCC by default > 3) Optionally enable this mode for non-MVCC read-only mode through additional > flag. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11305) Support data page scan for ODBC
[ https://issues.apache.org/jira/browse/IGNITE-11305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-11305: - Component/s: (was: sql) odbc > Support data page scan for ODBC > --- > > Key: IGNITE-11305 > URL: https://issues.apache.org/jira/browse/IGNITE-11305 > Project: Ignite > Issue Type: Improvement > Components: odbc >Reporter: Pavel Kuznetsov >Priority: Major > Labels: performance > > Just like IGNITE-10937, we need the same for ODBC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10816) MVCC: create benchmarks for bulk update operations.
[ https://issues.apache.org/jira/browse/IGNITE-10816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-10816: - Component/s: (was: sql) > MVCC: create benchmarks for bulk update operations. > --- > > Key: IGNITE-10816 > URL: https://issues.apache.org/jira/browse/IGNITE-10816 > Project: Ignite > Issue Type: Task > Components: mvcc, yardstick >Reporter: Andrew Mashenkov >Priority: Major > > For now, we have no any benchmark for bulk update operations (putAll or > multiple SQL inserts within single transaction) that can be run in mvcc mode. > 1. We should adapt existed PutAllTx benchmarks as they can failed due to > write conflicts. > 2. We should add SQL benchmarks for batched insert\update operations within > same Tx similar to existed putAll benches. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10164) Support query cancel for ODBC and thin clients
[ https://issues.apache.org/jira/browse/IGNITE-10164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-10164: - Component/s: (was: sql) thin client odbc > Support query cancel for ODBC and thin clients > -- > > Key: IGNITE-10164 > URL: https://issues.apache.org/jira/browse/IGNITE-10164 > Project: Ignite > Issue Type: Task > Components: odbc, thin client >Reporter: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > > Need to support query cancel for ODBC and thin clients -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10166) JDBC session level IO stats ON/OFF
[ https://issues.apache.org/jira/browse/IGNITE-10166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-10166: - Component/s: (was: sql) jdbc > JDBC session level IO stats ON/OFF > -- > > Key: IGNITE-10166 > URL: https://issues.apache.org/jira/browse/IGNITE-10166 > Project: Ignite > Issue Type: Task > Components: jdbc >Reporter: Yury Gerzhedovich >Priority: Major > Labels: iep-29 > > IO stats could be enabled/disabled for the given session through SQL > commands, e.g. *_SET STATISTICS _* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (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:all-tabpanel ] Vladimir Ozerov updated IGNITE-11309: - Component/s: (was: sql) jdbc > 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 >Priority: Major > Labels: iep-23 > > 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] [Updated] (IGNITE-10937) Support data page scan for JDBC
[ https://issues.apache.org/jira/browse/IGNITE-10937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-10937: - Component/s: (was: sql) jdbc > Support data page scan for JDBC > --- > > Key: IGNITE-10937 > URL: https://issues.apache.org/jira/browse/IGNITE-10937 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Sergi Vladykin >Assignee: Pavel Kuznetsov >Priority: Major > Labels: performance > > In scope jdbc v2 and thin drivers > We need to add connection property that reflects states of data page scan > feature: enabled/disabled/not defined. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7743) JDBC driver allows to connect to non existent schema
[
https://issues.apache.org/jira/browse/IGNITE-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-7743:
Component/s: (was: sql)
> JDBC driver allows to connect to non existent schema
>
>
> Key: IGNITE-7743
> URL: https://issues.apache.org/jira/browse/IGNITE-7743
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>Priority: Major
> Labels: usability
>
> Currently, if one creates a cache without DDL (via {{QueryEntity}} or
> {{indexedTypes}}), separate schema for this cache is created. Schema name is
> case sensitive, so to connect to it with JDBC driver, it's required to
> provide the name in quotes. Here is how it looks like in SqlLine:
> {noformat}
> ./bin/sqlline.sh -u jdbc:ignite:thin://127.0.0.1/\"CacheQueryExamplePersons\"
> {noformat}
> However, if name is provided without quotes, driver still connects, but then
> fails with a very unclear exception when a query is executed:
> {noformat}
> ./bin/sqlline.sh -u
> jdbc:ignite:thin://127.0.0.1/CacheQueryExamplePersons{noformat}
> This is a huge usability issue. We should disallow connections to schema that
> does not exist, throw exception in this case. Exception should provide proper
> explanation how to connect properly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-6261) ODBC support for Mac OSX
[ https://issues.apache.org/jira/browse/IGNITE-6261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-6261: Component/s: (was: sql) > ODBC support for Mac OSX > > > Key: IGNITE-6261 > URL: https://issues.apache.org/jira/browse/IGNITE-6261 > Project: Ignite > Issue Type: Improvement > Components: odbc >Affects Versions: 2.1 > Environment: Analytics >Reporter: Pranas Baliuka >Assignee: Igor Sapego >Priority: Major > Labels: usability > > In order for Ignite to be useful in analytics environment (accessing data via > R / Most reporting engines), the ODBC access is required. > Analyst do use Mac OSX (not only Linux/Windows). > The current ODBC driver is not compilable on OSX due to 1-2 different kernel > API functions. > Similar incompatibility issues are already resolved in similar projects using > conditional macros in C language. i.e. it may not be a big challenge to make > it work. > Thanks for planning and considerations! > PS: > For my use case the issue is a Blocker, because rJAVA is dead (requires Java > 6 installation on Mac OSX) and even with rJAVA , the JDBC implementation is > not working for R (class cast exceptions). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7164) MVCC: Remap protocol
[ https://issues.apache.org/jira/browse/IGNITE-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-7164: Component/s: (was: sql) > MVCC: Remap protocol > > > Key: IGNITE-7164 > URL: https://issues.apache.org/jira/browse/IGNITE-7164 > Project: Ignite > Issue Type: Task > Components: mvcc >Reporter: Igor Seliverstov >Priority: Minor > Fix For: 2.8 > > > We need to provide remap protocol on topology changes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-7164) MVCC: Remap protocol
[ https://issues.apache.org/jira/browse/IGNITE-7164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-7164: Summary: MVCC: Remap protocol (was: SQL TX: Remap protocol) > MVCC: Remap protocol > > > Key: IGNITE-7164 > URL: https://issues.apache.org/jira/browse/IGNITE-7164 > Project: Ignite > Issue Type: Task > Components: mvcc, sql >Reporter: Igor Seliverstov >Priority: Minor > Fix For: 2.8 > > > We need to provide remap protocol on topology changes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-6196) SQL: verify usability of template-based CREATE TABLE operations
[
https://issues.apache.org/jira/browse/IGNITE-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-6196.
-
Resolution: Won't Fix
Not relevant at the moment. Will reopen if needed.
> SQL: verify usability of template-based CREATE TABLE operations
> ---
>
> Key: IGNITE-6196
> URL: https://issues.apache.org/jira/browse/IGNITE-6196
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Priority: Major
> Labels: usability
>
> We do not have enough tests and examples on cache template usage for {{CREATE
> TABLE}}. I found only one test which used not template, but existing cache as
> a base for new cache. Let's add more tests with real pre-configured templates
> and extend our documentation accordingly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9314) MVCC TX: Datastreamer operations
[
https://issues.apache.org/jira/browse/IGNITE-9314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-9314:
Component/s: (was: sql)
> MVCC TX: Datastreamer operations
>
>
> Key: IGNITE-9314
> URL: https://issues.apache.org/jira/browse/IGNITE-9314
> Project: Ignite
> Issue Type: Task
> Components: mvcc
>Reporter: Igor Seliverstov
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.8
>
>
> Need to change DataStreamer semantics (make it transactional)
> Currently clients can see DataStreamer partial writes and two subsequent
> selects, which are run in scope of one transaction at load time, may return
> different results.
> Related thread:
>
> [http://apache-ignite-developers.2346864.n4.nabble.com/MVCC-and-IgniteDataStreamer-td32340.html]
> Also there is a problem when {{DataStreamer}} with {{allowOverwrite ==
> false}} does not insert value when versions for entry exist but they all are
> aborted. Proper transactional semantics should developed for such case. After
> that attention should be put on Cache.size method behavior. Cache.size
> addressed in https://issues.apache.org/jira/browse/IGNITE-8149 could be
> decremented improperly in
> {{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll}}
> method (called during streamer processing) when all existing mvcc row
> versions are aborted or last committed one is _remove_ version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-6415) ALTER TABLE: investigate why descriptor is not updated from GridQueryProcessor#onLocalOperationFinished
[
https://issues.apache.org/jira/browse/IGNITE-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-6415.
-
Resolution: Won't Fix
Not relevant at the moment. Will reopen if needed.
> ALTER TABLE: investigate why descriptor is not updated from
> GridQueryProcessor#onLocalOperationFinished
> ---
>
> Key: IGNITE-6415
> URL: https://issues.apache.org/jira/browse/IGNITE-6415
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Priority: Major
>
> For {{CREATE INDEX}} and {{DROP INDEX}} our DDL engine works as follows:
> 1) Update H2 structures from DDL worker thread
> 2) Then update type descriptor from
> {{GridQueryProcessor#onLocalOperationFinished}}
> For some reason {{ALTER TABLE}} handled differently, and we first update
> descriptor, then update H2. See
> {{GridQueryProcessor#processSchemaOperationLocal}}.
> Two questions:
> 1) Why descriptor is updated before H2? In this case we may endup in
> inconsistent state if H2 failed for some reason
> 2) Why we decided not to follow {{CREATE/DROP INDEX}} approach?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-7188) MVCC: Retry strategy on lock conflicts
[ https://issues.apache.org/jira/browse/IGNITE-7188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-7188: Summary: MVCC: Retry strategy on lock conflicts (was: SQL TX: Retry strategy on lock conflicts) > MVCC: Retry strategy on lock conflicts > -- > > Key: IGNITE-7188 > URL: https://issues.apache.org/jira/browse/IGNITE-7188 > Project: Ignite > Issue Type: Task > Components: mvcc, sql >Reporter: Igor Seliverstov >Priority: Major > > We need to provide some strategy to avoid lock conflicts (deadlocks), detect > and hanle them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-8598) SQL: ability to control partition pruning with explicit affinity column definition
[
https://issues.apache.org/jira/browse/IGNITE-8598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov closed IGNITE-8598.
---
> SQL: ability to control partition pruning with explicit affinity column
> definition
> --
>
> Key: IGNITE-8598
> URL: https://issues.apache.org/jira/browse/IGNITE-8598
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Priority: Major
>
> Affinity functions are applicable to keys only. Sometimes users may have
> complex affinity calculation logic, so that partition pruning optimization is
> not applicable. E.g. this custom {{AffinityKeyMapper}}. However, there is a
> chance that partition could be calculated from some attribute of {{value}}.
> It would be nice to force our engine to treat some attribute as affinity key
> even though it is not marked as {{AffinityKeyMapped}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-8591) SQL: Sort links on index pages in physical page order before row access
[ https://issues.apache.org/jira/browse/IGNITE-8591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-8591. - Resolution: Won't Fix Not relevant at the moment. > SQL: Sort links on index pages in physical page order before row access > --- > > Key: IGNITE-8591 > URL: https://issues.apache.org/jira/browse/IGNITE-8591 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.5 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Major > Labels: performance > > When index page match condition, we eagerly read all matched data rows. This > leads to a number of random disk reads.as Ignite use heap-organized storage. > We can pre-sort all matched row links in accordance to their physical > location, and then read them in batch. This will give us two important > advantages: > 1) Data reads will be more sequential, this is especially important for HDDs > 2) This could decrease number of page reads in case of dense data placement, > because there will be less evictions. > In future we should expand this optimization to several index pages in the > same way it is done in major databases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10836) Add documentation for jdbc thin query cancel
[ https://issues.apache.org/jira/browse/IGNITE-10836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-10836: - Component/s: (was: sql) jdbc > Add documentation for jdbc thin query cancel > > > Key: IGNITE-10836 > URL: https://issues.apache.org/jira/browse/IGNITE-10836 > Project: Ignite > Issue Type: Task > Components: documentation, jdbc >Reporter: Alexander Lapin >Priority: Major > Fix For: 2.8 > > > Query cancel for jdbc thin was implemented. > At least error codes page > ([https://apacheignite-sql.readme.io/docs/error-codes-27)] should be updated, > cause new error code (57014 Query cancelled) was added. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10972) MERGE INTO hangs in MVCC mode with unsorted keys
[ https://issues.apache.org/jira/browse/IGNITE-10972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-10972: - Component/s: (was: sql) > MERGE INTO hangs in MVCC mode with unsorted keys > > > Key: IGNITE-10972 > URL: https://issues.apache.org/jira/browse/IGNITE-10972 > Project: Ignite > Issue Type: Task > Components: mvcc >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Priority: Major > Attachments: CacheMvccMergeConflictTest.java > > > right now, if you perform repeatedly > MERGE INTO T(K, V) VALUES(k1, v1), (k2, v2), (k3, v3); > and in parallel > MERGE INTO T(K, V) VALUES(k2, v2), (k1, v1); > you will eventually see a deadlock. This is expected behavior as per old > putAll behavior, but the expectation is that you should see "Cannot serialize > transaction" errors instead of deadlock when using MVCC. > When doing MERGE INTO with sorted keys you will not get deadlock but will see > a lot of "Cannot serialize transaction" exception with expectation that such > statements to not conflict instead since they are ordered. > Please see attached test and userlist discussion. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8582) MVCC TX: Cache store read-through support
[
https://issues.apache.org/jira/browse/IGNITE-8582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-8582:
Component/s: (was: sql)
> MVCC TX: Cache store read-through support
> -
>
> Key: IGNITE-8582
> URL: https://issues.apache.org/jira/browse/IGNITE-8582
> Project: Ignite
> Issue Type: Improvement
> Components: mvcc
>Reporter: Sergey Kalashnikov
>Priority: Major
>
> Add support for read-through cache store for mvcc caches.
> Attention should be put on Cache.size method behavior. Cache.size addressed
> in https://issues.apache.org/jira/browse/IGNITE-8149 could be decremented
> improperly in
> {{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManager#mvccRemoveAll}}
> method (called during load from store) when all existing mvcc row versions
> are aborted or last committed one is _remove_ version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-5652) Print slow query warnings on client node
[ https://issues.apache.org/jira/browse/IGNITE-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-5652. --- > Print slow query warnings on client node > > > Key: IGNITE-5652 > URL: https://issues.apache.org/jira/browse/IGNITE-5652 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Alexander Paschenko >Priority: Major > Labels: sql-stability, usability > > Currently, only worker (MAP) nodes of the query print long query execution > time warning to their console, for usability it would be nice to propagate > this to the client node as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7859) SQL streaming support via native API
[
https://issues.apache.org/jira/browse/IGNITE-7859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov closed IGNITE-7859.
---
> SQL streaming support via native API
>
>
> Key: IGNITE-7859
> URL: https://issues.apache.org/jira/browse/IGNITE-7859
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Alexander Paschenko
>Priority: Major
>
> In addition to streaming via thin JDBC driver, ability to run same {{SET
> STREAMING}} command should be added to cache API.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-5653) Add to query execution plan debug data for joins
[ https://issues.apache.org/jira/browse/IGNITE-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-5653. --- > Add to query execution plan debug data for joins > > > Key: IGNITE-5653 > URL: https://issues.apache.org/jira/browse/IGNITE-5653 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Alexander Paschenko >Priority: Major > Labels: sql-stability, usability > > Plan should output table type (replicated/partitioned) and colocation > information if possible. If we have this than we can warn (or throw > exception) if users try to join non colocated tables with local joins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-6903) Implement new JMX metrics for Indexing
[ https://issues.apache.org/jira/browse/IGNITE-6903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-6903. - Resolution: Won't Fix Not relevant at the moment. Will reopen if needed. > Implement new JMX metrics for Indexing > -- > > Key: IGNITE-6903 > URL: https://issues.apache.org/jira/browse/IGNITE-6903 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Anton Vinogradov >Priority: Critical > Labels: iep-6, important > Fix For: 2.8 > > > These additional metrics and methods should be implemented: > - Space occupied by indexes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-4575) Implement wrapper for enums based on H2 user value type
[ https://issues.apache.org/jira/browse/IGNITE-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-4575. - Resolution: Won't Fix Not relevant at the moment. Will reopen if needed. > Implement wrapper for enums based on H2 user value type > --- > > Key: IGNITE-4575 > URL: https://issues.apache.org/jira/browse/IGNITE-4575 > Project: Ignite > Issue Type: New Feature > Components: sql >Reporter: Alexander Paschenko >Priority: Major > Labels: sql-engine > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8402) Long running transaction JMX
[ https://issues.apache.org/jira/browse/IGNITE-8402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-8402. - Resolution: Won't Fix Not relevant at the moment. Will reopen if needed. > Long running transaction JMX > > > Key: IGNITE-8402 > URL: https://issues.apache.org/jira/browse/IGNITE-8402 > Project: Ignite > Issue Type: Improvement > Components: sql >Affects Versions: 2.4 >Reporter: Ivan Kapralov >Priority: Major > > Facing necessity in Long Running Transactions JMX metric implementation. > Needed: transaction start time, node ID, duration, cache full qualified name, > originator ID. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-5653) Add to query execution plan debug data for joins
[ https://issues.apache.org/jira/browse/IGNITE-5653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-5653. - Resolution: Won't Fix Not relevant at the moment. Will reopen if needed. > Add to query execution plan debug data for joins > > > Key: IGNITE-5653 > URL: https://issues.apache.org/jira/browse/IGNITE-5653 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Alexander Paschenko >Priority: Major > Labels: sql-stability, usability > > Plan should output table type (replicated/partitioned) and colocation > information if possible. If we have this than we can warn (or throw > exception) if users try to join non colocated tables with local joins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-8600) SQL: lazy row materialization
[ https://issues.apache.org/jira/browse/IGNITE-8600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-8600. - Resolution: Won't Fix Not relevant at the moment. Will reopen if needed. > SQL: lazy row materialization > - > > Key: IGNITE-8600 > URL: https://issues.apache.org/jira/browse/IGNITE-8600 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.5 >Reporter: Vladimir Ozerov >Priority: Major > Labels: performance > > Currently our index cursor materializes rows as soon as they are encountered > in an index page. This is necessary to protect ourselves from concurrent data > modification. However, materialized rows might be filtered out later due to > additional filters. In addition, there is a chance that only indexed fields > is needed by query. > We can do the following: > 1) Introduce new mode that will return partially materialized rows, with only > inline index fields initialized. When some non-initialized attribute is > requested, we go to data page and materialize the whole row > 2) Enable this mode for MVCC by default > 3) Optionally enable this mode for non-MVCC read-only mode through additional > flag. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-5951) DDL: Support CREATE VIEW
[ https://issues.apache.org/jira/browse/IGNITE-5951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-5951. --- > DDL: Support CREATE VIEW > > > Key: IGNITE-5951 > URL: https://issues.apache.org/jira/browse/IGNITE-5951 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vyacheslav Koptilin >Priority: Minor > Labels: sql-engine > > Ignite should support sql VIEW. > The issue was mentioned on Stack Overflow: > https://stackoverflow.com/questions/45542016/unable-to-create-a-view-in-apache-ignite/45543134 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7846) SQL: support COPY command by native SQL
[ https://issues.apache.org/jira/browse/IGNITE-7846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-7846. - Resolution: Won't Fix Assignee: (was: Taras Ledkov) > SQL: support COPY command by native SQL > --- > > Key: IGNITE-7846 > URL: https://issues.apache.org/jira/browse/IGNITE-7846 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.3 >Reporter: Taras Ledkov >Priority: Major > > The COPY command is supported only for JDBC client (IGNITE-6917). > It must be supported by native SQL API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-5652) Print slow query warnings on client node
[ https://issues.apache.org/jira/browse/IGNITE-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-5652. - Resolution: Won't Fix Not relevant at the moment. Will reopen if needed. > Print slow query warnings on client node > > > Key: IGNITE-5652 > URL: https://issues.apache.org/jira/browse/IGNITE-5652 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.0 >Reporter: Alexander Paschenko >Priority: Major > Labels: sql-stability, usability > > Currently, only worker (MAP) nodes of the query print long query execution > time warning to their console, for usability it would be nice to propagate > this to the client node as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7846) SQL: support COPY command by native SQL
[ https://issues.apache.org/jira/browse/IGNITE-7846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-7846. --- > SQL: support COPY command by native SQL > --- > > Key: IGNITE-7846 > URL: https://issues.apache.org/jira/browse/IGNITE-7846 > Project: Ignite > Issue Type: Task > Components: sql >Affects Versions: 2.3 >Reporter: Taras Ledkov >Priority: Major > > The COPY command is supported only for JDBC client (IGNITE-6917). > It must be supported by native SQL API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7734) SQL COPY: support single quotes for file name
[
https://issues.apache.org/jira/browse/IGNITE-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov closed IGNITE-7734.
---
> SQL COPY: support single quotes for file name
> -
>
> Key: IGNITE-7734
> URL: https://issues.apache.org/jira/browse/IGNITE-7734
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Priority: Major
>
> Currently file name is used in COPY command as follows: \{{"/path/to/file"}}.
> We need to support single-quoted case as well: \{{'/path/to/file'}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11323) Reduce boilerplate "System.setProperty" code in tests
Ivan Bessonov created IGNITE-11323:
--
Summary: Reduce boilerplate "System.setProperty" code in tests
Key: IGNITE-11323
URL: https://issues.apache.org/jira/browse/IGNITE-11323
Project: Ignite
Issue Type: Test
Reporter: Ivan Bessonov
Assignee: Ivan Bessonov
There are many examples in tests where some property gets new value in
"beforeTestsStarted"/"beforeTest"/"beginning of test method" and then gets its
previous value in "afterTestsStopped"/"afterTest"/"finally block of test
method". This approach leads to excessive code that can be avoided.
I suggest implementing annotation "WithSystemProperty" (name is the subject to
discussion) that will allow us to write this:
{code:java}
@Test
@WithSystemProperty(key = IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK, value =
"true")
public void testSkipCheckConsistencyFlagEnabled() throws Exception {
...
}
{code}
instead of this:
{code:java}
@Test
public void testSkipCheckConsistencyFlagEnabled() throws Exception {
String backup =
System.setProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK, "true");
try {
...
}
finally {
if (backup != null)
System.setProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK,
backup);
else
System.clearProperty(IGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK);
}
}
{code}
There's also has to be ability to use this annotation on test class so new
value of system properties will be used in all of its test methods.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-7236) SQL: create tests for optimized INSERT and MERGE operations
[
https://issues.apache.org/jira/browse/IGNITE-7236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-7236.
-
Resolution: Won't Fix
Not relevant at the moment. Will reopen if needed.
> SQL: create tests for optimized INSERT and MERGE operations
> ---
>
> Key: IGNITE-7236
> URL: https://issues.apache.org/jira/browse/IGNITE-7236
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Priority: Major
>
> Important optimization IGNITE-4490 was added to the product. However, it
> lacks excessive tests coverage. We need to test the following scenarios:
> 1) Various data types (especially dates)
> 2) Single updates vs batched updates
> 3) Constants and nulls (e.g. {{INSERT INTO ... VALUES (a, b)}})
> 4) Parameters (e.g. {{INSERT INTO ... VALUES (?, ?)}})
> 5) Multiple SQL statements at once (e.g. {{INSERT INTO ...; INSERT INTO ...}})
> 6) Insert multiple lines at once ({{INSERT INTO ... VALUES (a1, b1), (a2,
> b2)}})
> 7) Insert multiple lines with parameters
> 8) Invalid parameters count in different query types - need to make sure that
> we throw correct errors.
> All tests except of p.8 should check both correctness and the fact that query
> was executed without H2 involvement (e.g. using some code hack).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-7735) SQL COPY: expose streamer options to user
[ https://issues.apache.org/jira/browse/IGNITE-7735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-7735. - Resolution: Won't Fix Not relevant at the moment. Will reopen if needed. > SQL COPY: expose streamer options to user > - > > Key: IGNITE-7735 > URL: https://issues.apache.org/jira/browse/IGNITE-7735 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Priority: Major > > COPY command uses cache streamer underneath. We need to expose usual streamer > options (per-node-buffer-size, per-node-parallel-ops, allow-overwrite, etc) > to the user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-6318) SQL: Make sure that QueryTypeDescriptorImpl is used in thread-safe manner
[
https://issues.apache.org/jira/browse/IGNITE-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov closed IGNITE-6318.
---
> SQL: Make sure that QueryTypeDescriptorImpl is used in thread-safe manner
> -
>
> Key: IGNITE-6318
> URL: https://issues.apache.org/jira/browse/IGNITE-6318
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Priority: Major
>
> {{QueryTypeDescriptorImpl}} is mostly immutable structure. But as we add more
> and more DDL features, it becomes mutable. We need to make sure that it is
> still thread-safe.
> Specifically, when {{CREATE INDEX}} command was implemented, I guarded index
> collection with mutex. Now we added {{ALTER TABLE}} command, and it seems
> that thread-safety for columns was lost.
> I propose to re-use index mutex (rename it to {{stateMux}}) and make sure
> that column collections are also thread-safe. I would also propose to
> consider copy-on-write approach, as these collections are returned by some
> methods as is.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-7733) SQL COPY: native API support
[ https://issues.apache.org/jira/browse/IGNITE-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-7733. --- > SQL COPY: native API support > > > Key: IGNITE-7733 > URL: https://issues.apache.org/jira/browse/IGNITE-7733 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Priority: Major > > Currently COPY command can only be executed from within thin JDBC driver. > Need to add native API support as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (IGNITE-7236) SQL: create tests for optimized INSERT and MERGE operations
[
https://issues.apache.org/jira/browse/IGNITE-7236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov closed IGNITE-7236.
---
> SQL: create tests for optimized INSERT and MERGE operations
> ---
>
> Key: IGNITE-7236
> URL: https://issues.apache.org/jira/browse/IGNITE-7236
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Priority: Major
>
> Important optimization IGNITE-4490 was added to the product. However, it
> lacks excessive tests coverage. We need to test the following scenarios:
> 1) Various data types (especially dates)
> 2) Single updates vs batched updates
> 3) Constants and nulls (e.g. {{INSERT INTO ... VALUES (a, b)}})
> 4) Parameters (e.g. {{INSERT INTO ... VALUES (?, ?)}})
> 5) Multiple SQL statements at once (e.g. {{INSERT INTO ...; INSERT INTO ...}})
> 6) Insert multiple lines at once ({{INSERT INTO ... VALUES (a1, b1), (a2,
> b2)}})
> 7) Insert multiple lines with parameters
> 8) Invalid parameters count in different query types - need to make sure that
> we throw correct errors.
> All tests except of p.8 should check both correctness and the fact that query
> was executed without H2 involvement (e.g. using some code hack).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-6196) SQL: verify usability of template-based CREATE TABLE operations
[
https://issues.apache.org/jira/browse/IGNITE-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov closed IGNITE-6196.
---
> SQL: verify usability of template-based CREATE TABLE operations
> ---
>
> Key: IGNITE-6196
> URL: https://issues.apache.org/jira/browse/IGNITE-6196
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Priority: Major
> Labels: usability
>
> We do not have enough tests and examples on cache template usage for {{CREATE
> TABLE}}. I found only one test which used not template, but existing cache as
> a base for new cache. Let's add more tests with real pre-configured templates
> and extend our documentation accordingly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-7734) SQL COPY: support single quotes for file name
[
https://issues.apache.org/jira/browse/IGNITE-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-7734.
-
Resolution: Won't Fix
Not relevant at the moment. Will reopen if needed.
> SQL COPY: support single quotes for file name
> -
>
> Key: IGNITE-7734
> URL: https://issues.apache.org/jira/browse/IGNITE-7734
> Project: Ignite
> Issue Type: Task
> Components: sql
>Reporter: Vladimir Ozerov
>Priority: Major
>
> Currently file name is used in COPY command as follows: \{{"/path/to/file"}}.
> We need to support single-quoted case as well: \{{'/path/to/file'}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-6318) SQL: Make sure that QueryTypeDescriptorImpl is used in thread-safe manner
[
https://issues.apache.org/jira/browse/IGNITE-6318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-6318.
-
Resolution: Won't Fix
Not relevant at the moment. Will reopen if needed.
> SQL: Make sure that QueryTypeDescriptorImpl is used in thread-safe manner
> -
>
> Key: IGNITE-6318
> URL: https://issues.apache.org/jira/browse/IGNITE-6318
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Priority: Major
>
> {{QueryTypeDescriptorImpl}} is mostly immutable structure. But as we add more
> and more DDL features, it becomes mutable. We need to make sure that it is
> still thread-safe.
> Specifically, when {{CREATE INDEX}} command was implemented, I guarded index
> collection with mutex. Now we added {{ALTER TABLE}} command, and it seems
> that thread-safety for columns was lost.
> I propose to re-use index mutex (rename it to {{stateMux}}) and make sure
> that column collections are also thread-safe. I would also propose to
> consider copy-on-write approach, as these collections are returned by some
> methods as is.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-7735) SQL COPY: expose streamer options to user
[ https://issues.apache.org/jira/browse/IGNITE-7735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov closed IGNITE-7735. --- > SQL COPY: expose streamer options to user > - > > Key: IGNITE-7735 > URL: https://issues.apache.org/jira/browse/IGNITE-7735 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Priority: Major > > COPY command uses cache streamer underneath. We need to expose usual streamer > options (per-node-buffer-size, per-node-parallel-ops, allow-overwrite, etc) > to the user. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-7733) SQL COPY: native API support
[ https://issues.apache.org/jira/browse/IGNITE-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov resolved IGNITE-7733. - Resolution: Won't Fix Not relevant at the moment. Will reopen if needed. > SQL COPY: native API support > > > Key: IGNITE-7733 > URL: https://issues.apache.org/jira/browse/IGNITE-7733 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Vladimir Ozerov >Priority: Major > > Currently COPY command can only be executed from within thin JDBC driver. > Need to add native API support as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
