[jira] [Updated] (IGNITE-11509) Remove DistributedBaselineConfiguration and replace to methods on IgniteCluster
[ https://issues.apache.org/jira/browse/IGNITE-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-11509: Ignite Flags: (was: Docs Required) > Remove DistributedBaselineConfiguration and replace to methods on > IgniteCluster > --- > > Key: IGNITE-11509 > URL: https://issues.apache.org/jira/browse/IGNITE-11509 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Major > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11509) Remove DistributedBaselineConfiguration and replace to methods on IgniteCluster
[ https://issues.apache.org/jira/browse/IGNITE-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-11509: Fix Version/s: 2.8 > Remove DistributedBaselineConfiguration and replace to methods on > IgniteCluster > --- > > Key: IGNITE-11509 > URL: https://issues.apache.org/jira/browse/IGNITE-11509 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Major > Fix For: 2.8 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11509) Remove DistributedBaselineConfiguration and replace to methods on IgniteCluster
Dmitriy Govorukhin created IGNITE-11509: --- Summary: Remove DistributedBaselineConfiguration and replace to methods on IgniteCluster Key: IGNITE-11509 URL: https://issues.apache.org/jira/browse/IGNITE-11509 Project: Ignite Issue Type: Bug Reporter: Dmitriy Govorukhin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11227) SQL: Streamline DML execution logic
[
https://issues.apache.org/jira/browse/IGNITE-11227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787758#comment-16787758
]
Ignite TC Bot commented on IGNITE-11227:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Queries 1{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=3258778]]
* IgniteBinaryCacheQueryTestSuite: RunningQueriesTest.testQueryDmlUpdate - 0,0%
fails in last 431 master runs.
* IgniteBinaryCacheQueryTestSuite: RunningQueriesTest.testQueryDmlDelete - 0,0%
fails in last 431 master runs.
{color:#d04437}JDBC Driver{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=3258709]]
* IgniteJdbcDriverTestSuite:
JdbcThinDataPageScanPropertySelfTest.testDataPageScanBatching - 0,0% fails in
last 46 master runs.
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3258802&buildTypeId=IgniteTests24Java8_RunAll]
> SQL: Streamline DML execution logic
> ---
>
> Key: IGNITE-11227
> URL: https://issues.apache.org/jira/browse/IGNITE-11227
> 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 DML execution logic is overly complex with execution flow being
> transferred between indexing and DML processor back and forth. Need to
> simplify it as much as possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11509) Remove DistributedBaselineConfiguration and replace to methods on IgniteCluster
[ https://issues.apache.org/jira/browse/IGNITE-11509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin reassigned IGNITE-11509: --- Assignee: Dmitriy Govorukhin > Remove DistributedBaselineConfiguration and replace to methods on > IgniteCluster > --- > > Key: IGNITE-11509 > URL: https://issues.apache.org/jira/browse/IGNITE-11509 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11510) SQL: Rework running queries tests to make them stable to internal code changes
Vladimir Ozerov created IGNITE-11510:
Summary: SQL: Rework running queries tests to make them stable to
internal code changes
Key: IGNITE-11510
URL: https://issues.apache.org/jira/browse/IGNITE-11510
Project: Ignite
Issue Type: Task
Components: sql
Reporter: Vladimir Ozerov
See {{RunningQueriesTest}}. It hacks into {{IgniteH2Indexing.querySqlFields}}.
This is not resilent to internal code changes. We need to make sure that the
whole test use as less hacks as possible. E.g. we can hack into running queries
manager instead of indexing.
Several DML tests are muted due to changes introduced in IGNITE-11227.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11511) SQL: Possible bug with parameters passing for complex DML queries
Vladimir Ozerov created IGNITE-11511:
Summary: SQL: Possible bug with parameters passing for complex DML
queries
Key: IGNITE-11511
URL: https://issues.apache.org/jira/browse/IGNITE-11511
Project: Ignite
Issue Type: Bug
Components: sql
Reporter: Vladimir Ozerov
Assignee: Pavel Kuznetsov
Fix For: 2.8
See methods {{IgniteH2Indexing.executeSelectLocal}} and
{{IgniteH2Indexing.executeSelectForDml}}. They both could be invoked for
{{SELECT}} statements extracted from DML.
But notice how parameters are passed: it seems that we may pass parameters from
DML statement unchanged, which is illegal. E.g. consider the following DML:
{code}
UPDATE table SET x=? WHERE x=?
{code}
In this case SELECT statement should get only the second parameter.
Need to create tests to confirm that this is the case and make necessary fixes
if needed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11457) Prewarming of page memory after node restart
[ https://issues.apache.org/jira/browse/IGNITE-11457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16787867#comment-16787867 ] Ilya Lantukh commented on IGNITE-11457: --- [~cyberdemon], Thanks for the contribution! To me it makes more sense to pre-warm page memory based on physical records in last N WAL segments, without any LoadedPageTrackers.. What do you think? > Prewarming of page memory after node restart > > > Key: IGNITE-11457 > URL: https://issues.apache.org/jira/browse/IGNITE-11457 > Project: Ignite > Issue Type: New Feature >Reporter: Dmitriy Sorokin >Assignee: Dmitriy Sorokin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The essence of page memory prewarming feature is that after restarting the > node is to load into memory those pages that were loaded before last > shutdown. This approach allows to get fully prewarmed node or even cluster > just after one has been restarted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11468) System caches should not survive client reconnect
[ https://issues.apache.org/jira/browse/IGNITE-11468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin reassigned IGNITE-11468: --- Assignee: Dmitriy Govorukhin (was: Alexey Goncharuk) > System caches should not survive client reconnect > - > > Key: IGNITE-11468 > URL: https://issues.apache.org/jira/browse/IGNITE-11468 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Dmitriy Govorukhin >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > After IGNITE-10898 it became clear that system caches surviving client > reconnect lead are error-prone: there are too many specific code paths > leading to logic duplication and exclusions. At the same time, the benefit of > system caches survival is not tangible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11512) Add counter left partition for index rebuild in CacheGroupMetricsMXBean
Alexand Polyakov created IGNITE-11512: - Summary: Add counter left partition for index rebuild in CacheGroupMetricsMXBean Key: IGNITE-11512 URL: https://issues.apache.org/jira/browse/IGNITE-11512 Project: Ignite Issue Type: Improvement Components: general Affects Versions: 2.7 Reporter: Alexand Polyakov Assignee: Alexand Polyakov Now, if ran rebuild indexes, this can determined only on load CPU and thread dump. The presence of the "how many partitions left to index" metric will help determine whether the rebuilding is going on and on which cache, as well as the percentage of completion. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
