[jira] [Updated] (IGNITE-17612) Sql. Fix TableScanNode rows propagation.
[ https://issues.apache.org/jira/browse/IGNITE-17612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-17612: - Fix Version/s: 3.0.0-beta1 > Sql. Fix TableScanNode rows propagation. > > > Key: IGNITE-17612 > URL: https://issues.apache.org/jira/browse/IGNITE-17612 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta1 > > Time Spent: 10m > Remaining Estimate: 0h > > Because of a poor performance of current transactional protocol, several sql > tests was disabled under this ticked. Need to enable those tests after new > protocol will be merged to main. Also seems we have bug in TableScanNode > implementation, no rows are propagated while it still needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17612) Sql. Fix TableScanNode rows propagation.
[ https://issues.apache.org/jira/browse/IGNITE-17612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-17612: Description: Because of a poor performance of current transactional protocol, several sql tests was disabled under this ticked. Need to enable those tests after new protocol will be merged to main. Also seems we have bug in TableScanNode implementation, no rows are propagated while it still needed. (was: Because of a poor performance of current transactional protocol, several sql tests was disabled under this ticked. Need to enable those tests after new protocol will be merged to main.) > Sql. Fix TableScanNode rows propagation. > > > Key: IGNITE-17612 > URL: https://issues.apache.org/jira/browse/IGNITE-17612 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > > Because of a poor performance of current transactional protocol, several sql > tests was disabled under this ticked. Need to enable those tests after new > protocol will be merged to main. Also seems we have bug in TableScanNode > implementation, no rows are propagated while it still needed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17612) Sql. Fix TableScanNode rows propagation.
[ https://issues.apache.org/jira/browse/IGNITE-17612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgeny Stanilovsky updated IGNITE-17612: Summary: Sql. Fix TableScanNode rows propagation. (was: Sql. Unmute sql tests) > Sql. Fix TableScanNode rows propagation. > > > Key: IGNITE-17612 > URL: https://issues.apache.org/jira/browse/IGNITE-17612 > Project: Ignite > Issue Type: Improvement > Components: sql >Reporter: Konstantin Orlov >Assignee: Evgeny Stanilovsky >Priority: Major > Labels: ignite-3 > > Because of a poor performance of current transactional protocol, several sql > tests was disabled under this ticked. Need to enable those tests after new > protocol will be merged to main. -- This message was sent by Atlassian Jira (v8.20.10#820010)
