[jira] [Created] (IGNITE-12692) Calcite integration. DML. Skip reducer optimization.
Igor Seliverstov created IGNITE-12692: - Summary: Calcite integration. DML. Skip reducer optimization. Key: IGNITE-12692 URL: https://issues.apache.org/jira/browse/IGNITE-12692 Project: Ignite Issue Type: Improvement Reporter: Igor Seliverstov Having plan tree we easily can check whether a final modification may be executed on data nodes directly or not. We should implement such kind of optimization. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12691) .NET: Native Near Cache
Pavel Tupitsyn created IGNITE-12691: --- Summary: .NET: Native Near Cache Key: IGNITE-12691 URL: https://issues.apache.org/jira/browse/IGNITE-12691 Project: Ignite Issue Type: New Feature Components: platforms Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 2.9 Implement native .NET Near Cache, which stores deserialized cache data on CLR heap. Right now every cache.Get, every scan query, etc, cause repeated copy and deserialization of data from JVM, even for primary keys or near cache entries. This often becomes a bottleneck. Keeping up-to-date deserialized values in CLR memory can greatly improve performance and reduce latency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12690) Remove deprecation from DataRegionMetrics and mark metrics API with IgniteExperimental
[ https://issues.apache.org/jira/browse/IGNITE-12690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12690: - Summary: Remove deprecation from DataRegionMetrics and mark metrics API with IgniteExperimental (was: Remove deprecation from DataRegionMetrics and mark ReadOnlyMetricRegistry with IgniteExperimental) > Remove deprecation from DataRegionMetrics and mark metrics API with > IgniteExperimental > -- > > Key: IGNITE-12690 > URL: https://issues.apache.org/jira/browse/IGNITE-12690 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Blocker > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > According to the vote [1] results and the discussion thread [2] the following > needs to be done: > 1. Remove @deprecated from DataRegionMetric > 2. Mark new metrics API with @IgniteExperimental > [1] > http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Allow-or-prohibit-a-joint-use-of-deprecated-and-IgniteExperimental-td45863.html > [2] > http://apache-ignite-developers.2346864.n4.nabble.com/Internal-classes-are-exposed-in-public-API-td45146.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-7276) .NET: Enable/disable cache statistics in runtime
[
https://issues.apache.org/jira/browse/IGNITE-7276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-7276:
---
Ignite Flags: Release Notes Required
Release Note: Added ICache.EnableStatistics, ICluster.EnableStatistics.
> .NET: Enable/disable cache statistics in runtime
>
>
> Key: IGNITE-7276
> URL: https://issues.apache.org/jira/browse/IGNITE-7276
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Sergey Stronchinskiy
>Priority: Major
> Labels: .NET, newbie
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {{ICache.EnableStatistics}}, {{ICluster.EnableStatistics}}.
> See IGNITE-369.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-7276) .NET: Enable/disable cache statistics in runtime
[
https://issues.apache.org/jira/browse/IGNITE-7276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038557#comment-17038557
]
Pavel Tupitsyn commented on IGNITE-7276:
[~GuruStron] checked the PR, looks good in general, please see a few comments
on GitHub.
> .NET: Enable/disable cache statistics in runtime
>
>
> Key: IGNITE-7276
> URL: https://issues.apache.org/jira/browse/IGNITE-7276
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Sergey Stronchinskiy
>Priority: Major
> Labels: .NET, newbie
> Time Spent: 40m
> Remaining Estimate: 0h
>
> {{ICache.EnableStatistics}}, {{ICluster.EnableStatistics}}.
> See IGNITE-369.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12638) Classes persisted by DistributedMetaStorage are not IgniteDTO
[ https://issues.apache.org/jira/browse/IGNITE-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038540#comment-17038540 ] Maxim Muzafarov commented on IGNITE-12638: -- I've cherry-picked to 2.8 > Classes persisted by DistributedMetaStorage are not IgniteDTO > - > > Key: IGNITE-12638 > URL: https://issues.apache.org/jira/browse/IGNITE-12638 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Fix For: 2.8 > > Time Spent: 1h > Remaining Estimate: 0h > > This has to be fixed to simplify future modification of component. > DistributedMetaStorageHistoryItem and DistributedMetaStorageVersion will be > persisted on disc so we need to have a reliable way to read them even when > classes will be updated in the future. IgniteDataTransferObject is the > standard option for such cases - it allows versioning of serialization format. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12690) Remove deprecation from DataRegionMetrics and mark ReadOnlyMetricRegistry with IgniteExperimental
[ https://issues.apache.org/jira/browse/IGNITE-12690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12690: - Priority: Blocker (was: Major) > Remove deprecation from DataRegionMetrics and mark ReadOnlyMetricRegistry > with IgniteExperimental > - > > Key: IGNITE-12690 > URL: https://issues.apache.org/jira/browse/IGNITE-12690 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Blocker > Fix For: 2.8 > > > According to the vote [1] results and the discussion thread [2] the following > needs to be done: > 1. Remove @deprecated from DataRegionMetric > 2. Mark new metrics API with @IgniteExperimental > [1] > http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Allow-or-prohibit-a-joint-use-of-deprecated-and-IgniteExperimental-td45863.html > [2] > http://apache-ignite-developers.2346864.n4.nabble.com/Internal-classes-are-exposed-in-public-API-td45146.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12690) Remove deprecation from DataRegionMetrics and mark ReadOnlyMetricRegistry with IgniteExperimental
Maxim Muzafarov created IGNITE-12690: Summary: Remove deprecation from DataRegionMetrics and mark ReadOnlyMetricRegistry with IgniteExperimental Key: IGNITE-12690 URL: https://issues.apache.org/jira/browse/IGNITE-12690 Project: Ignite Issue Type: Task Reporter: Maxim Muzafarov Assignee: Maxim Muzafarov Fix For: 2.8 According to the vote [1] results and the discussion thread [2] the following needs to be done: 1. Remove @deprecated from DataRegionMetric 2. Mark new metrics API with @IgniteExperimental [1] http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Allow-or-prohibit-a-joint-use-of-deprecated-and-IgniteExperimental-td45863.html [2] http://apache-ignite-developers.2346864.n4.nabble.com/Internal-classes-are-exposed-in-public-API-td45146.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12690) Remove deprecation from DataRegionMetrics and mark ReadOnlyMetricRegistry with IgniteExperimental
[ https://issues.apache.org/jira/browse/IGNITE-12690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12690: - Ignite Flags: (was: Docs Required,Release Notes Required) > Remove deprecation from DataRegionMetrics and mark ReadOnlyMetricRegistry > with IgniteExperimental > - > > Key: IGNITE-12690 > URL: https://issues.apache.org/jira/browse/IGNITE-12690 > Project: Ignite > Issue Type: Task >Reporter: Maxim Muzafarov >Assignee: Maxim Muzafarov >Priority: Blocker > Fix For: 2.8 > > > According to the vote [1] results and the discussion thread [2] the following > needs to be done: > 1. Remove @deprecated from DataRegionMetric > 2. Mark new metrics API with @IgniteExperimental > [1] > http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Allow-or-prohibit-a-joint-use-of-deprecated-and-IgniteExperimental-td45863.html > [2] > http://apache-ignite-developers.2346864.n4.nabble.com/Internal-classes-are-exposed-in-public-API-td45146.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12686) Deprecate obsolete configuration properties
[
https://issues.apache.org/jira/browse/IGNITE-12686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038495#comment-17038495
]
Ivan Pavlukhin commented on IGNITE-12686:
-
Same {{PDS (Indexing)}} failure as in master.
> Deprecate obsolete configuration properties
> ---
>
> Key: IGNITE-12686
> URL: https://issues.apache.org/jira/browse/IGNITE-12686
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: newbie
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Following properties were discovered as obsolete (no usages in codebase):
> * TransactionConfiguration.PessimisticTxLogSize
> * TransactionConfiguration.PessimisticTxLogLinger
> * CacheConfiguration.DefaultLockTimeout
> Let's deprecate them.
> Note that we are not going to remove them at this stage to avoid possible
> compatibility issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12686) Deprecate obsolete configuration properties
[
https://issues.apache.org/jira/browse/IGNITE-12686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038493#comment-17038493
]
Ignite TC Bot commented on IGNITE-12686:
{panel:title=Branch: [pull/7438/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5057756]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5057313buildTypeId=IgniteTests24Java8_RunAll]
> Deprecate obsolete configuration properties
> ---
>
> Key: IGNITE-12686
> URL: https://issues.apache.org/jira/browse/IGNITE-12686
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Labels: newbie
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Following properties were discovered as obsolete (no usages in codebase):
> * TransactionConfiguration.PessimisticTxLogSize
> * TransactionConfiguration.PessimisticTxLogLinger
> * CacheConfiguration.DefaultLockTimeout
> Let's deprecate them.
> Note that we are not going to remove them at this stage to avoid possible
> compatibility issues.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12689) Partitions should become owned after a checkpoint, regardless of a topology change. Nevertheless a rebalance is not required.
Vladislav Pyatkov created IGNITE-12689:
--
Summary: Partitions should become owned after a checkpoint,
regardless of a topology change. Nevertheless a rebalance is not required.
Key: IGNITE-12689
URL: https://issues.apache.org/jira/browse/IGNITE-12689
Project: Ignite
Issue Type: Bug
Reporter: Vladislav Pyatkov
After checkpoint completed we try to own all partitions of rebalanced cache
(see WalStateManager#onGroupRebalanceFinished):
{code}
cpFut.futureFor(FINISHED).listen(new IgniteInClosureX() {
@Override public void applyx(IgniteInternalFuture future) {
if (X.hasCause(future.error(), NodeStoppingException.class))
return;
for (Integer grpId0 : groupsToEnable) {
try {
cctx.database().walEnabled(grpId0, true, true);
}
catch (Exception e) {
if (!X.hasCause(e, NodeStoppingException.class))
throw e;
}
CacheGroupContext grp = cctx.cache().cacheGroup(grpId0);
if (grp != null)
grp.topology().ownMoving(lastGroupTop);
else if (log.isDebugEnabled())
log.debug("Cache group was destroyed before checkpoint
finished, [grpId=" + grpId0 + ']');
}
if (log.isDebugEnabled())
log.debug("Refresh partitions due to rebalance finished");
// Trigger exchange for switching to ideal assignment when all nodes
are ready.
cctx.exchange().refreshPartitions();
}
});
{code}
But in case of topology changes during checkpoint pass, we are need to invoke
rebalance manually (see GridDhtPartitionTopologyImpl#ownMoving):
{code}
if (lastAffChangeVer.compareTo(rebFinishedTopVer) > 0) {
if (log.isInfoEnabled()) {
log.info("Affinity topology changed, no MOVING partitions will be owned
" +
"[rebFinishedTopVer=" + rebFinishedTopVer +
", lastAffChangeVer=" + lastAffChangeVer + "]");
}
{code}
That will be hardly ever happends, but if it was we restarted whole rebalance
(over all partitions).I am advice start rebalance only when it needed and mark
partitions as own if it definitely not need (when change of topology does not
fluent to assignment).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12433) Possible to create table with duplicate definition of column
[
https://issues.apache.org/jira/browse/IGNITE-12433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038393#comment-17038393
]
Sergey Uttsel commented on IGNITE-12433:
[~jooger], OK, done.
> Possible to create table with duplicate definition of column
>
>
> Key: IGNITE-12433
> URL: https://issues.apache.org/jira/browse/IGNITE-12433
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.8
>Reporter: Ilya Kasnacheev
>Assignee: Sergey Uttsel
>Priority: Minor
> Labels: newbie
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> {code}
> sqlline version 1.3.0
> sqlline> !connect jdbc:ignite:thin://localhost
> Enter username for jdbc:ignite:thin://localhost:
> Enter password for jdbc:ignite:thin://localhost:
> 0: jdbc:ignite:thin://localhost> CREATE TABLE Person(ID INTEGER PRIMARY KEY,
> NAME VARCHAR(100), NAME
> . . . . . . . . . . . . . . . .> VARCHAR(100), AGE INTEGER (64));
> No rows affected (0,229 seconds)
> 0: jdbc:ignite:thin://localhost> select * from person;
> ++++
> | ID | NAME |
>AGE |
> ++++
> ++++
> No rows selected (0,073 seconds)
> {code}
> This is on master branch. "NAME VARCHAR(100)" twice.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11147) Re-balance cancellation occur by non-affected event
[ https://issues.apache.org/jira/browse/IGNITE-11147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038356#comment-17038356 ] Alexey Scherbakov commented on IGNITE-11147: [~v.pyatkov] Check my comments under the PR. > Re-balance cancellation occur by non-affected event > --- > > Key: IGNITE-11147 > URL: https://issues.apache.org/jira/browse/IGNITE-11147 > Project: Ignite > Issue Type: Test > Components: cache >Affects Versions: 2.7 >Reporter: Sergey Antonov >Assignee: Vladislav Pyatkov >Priority: Critical > Fix For: 2.9 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > Re-balance cancels by non-affected events, for examples: > 1) joining non affinity node > 2) stating snapshot > 3) starting/stopping other cache > Try to skip as more as possible events instead of cancellation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11451) SQL system view for IO indexes statistics
[ https://issues.apache.org/jira/browse/IGNITE-11451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038347#comment-17038347 ] Nikolay Izhikov commented on IGNITE-11451: -- > 2) View INDEXES contains only static information. New one contain dynamic > changed information. Dynamic changes in the SYS.metrics. > Is it reasonable? Can we add columns to the existing SYS.INDEXES view? That contains metric values for the corresponding indexes. It seems the most natural improvement for me. > SQL system view for IO indexes statistics > - > > Key: IGNITE-11451 > URL: https://issues.apache.org/jira/browse/IGNITE-11451 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Priority: Major > Labels: IEP-35, iep-29, newbie > Fix For: 3.0, 2.9 > > > Need to expose system SQL views to be able view IO statistics for SQL indexes. > Start point to register new views is > org.apache.ignite.internal.processors.query.h2.SchemaManager#SchemaManager > Need to expose information which registered in GridMetricManager at > org.apache.ignite.internal.metric.IoStatisticsHolderIndex > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11451) SQL system view for IO indexes statistics
[ https://issues.apache.org/jira/browse/IGNITE-11451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038339#comment-17038339 ] Yury Gerzhedovich commented on IGNITE-11451: [~nizhikov], there at least two reasons to have separate view for index IO statistics: 1) It common approach for other vendors (see https://cwiki.apache.org/confluence/display/IGNITE/IEP-27%3A+Page+IO+statistics) 2) View INDEXES contains only static information. New one contain dynamic changed information. WDYT? Is it reasonable? > SQL system view for IO indexes statistics > - > > Key: IGNITE-11451 > URL: https://issues.apache.org/jira/browse/IGNITE-11451 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Yury Gerzhedovich >Priority: Major > Labels: IEP-35, iep-29, newbie > Fix For: 3.0, 2.9 > > > Need to expose system SQL views to be able view IO statistics for SQL indexes. > Start point to register new views is > org.apache.ignite.internal.processors.query.h2.SchemaManager#SchemaManager > Need to expose information which registered in GridMetricManager at > org.apache.ignite.internal.metric.IoStatisticsHolderIndex > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11147) Re-balance cancellation occur by non-affected event
[ https://issues.apache.org/jira/browse/IGNITE-11147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038329#comment-17038329 ] Maxim Muzafarov commented on IGNITE-11147: -- Folks, I'll take a look at these changes soon. Please, do not hurry with the merge. > Re-balance cancellation occur by non-affected event > --- > > Key: IGNITE-11147 > URL: https://issues.apache.org/jira/browse/IGNITE-11147 > Project: Ignite > Issue Type: Test > Components: cache >Affects Versions: 2.7 >Reporter: Sergey Antonov >Assignee: Vladislav Pyatkov >Priority: Critical > Fix For: 2.9 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Re-balance cancels by non-affected events, for examples: > 1) joining non affinity node > 2) stating snapshot > 3) starting/stopping other cache > Try to skip as more as possible events instead of cancellation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12433) Possible to create table with duplicate definition of column
[
https://issues.apache.org/jira/browse/IGNITE-12433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038328#comment-17038328
]
Yury Gerzhedovich commented on IGNITE-12433:
[~Sergey Uttsel], thanks. Seems will be better to return your first SQL error
code for the case. It's general error which we found during parsing. Everything
else looks good.
> Possible to create table with duplicate definition of column
>
>
> Key: IGNITE-12433
> URL: https://issues.apache.org/jira/browse/IGNITE-12433
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.8
>Reporter: Ilya Kasnacheev
>Assignee: Sergey Uttsel
>Priority: Minor
> Labels: newbie
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> {code}
> sqlline version 1.3.0
> sqlline> !connect jdbc:ignite:thin://localhost
> Enter username for jdbc:ignite:thin://localhost:
> Enter password for jdbc:ignite:thin://localhost:
> 0: jdbc:ignite:thin://localhost> CREATE TABLE Person(ID INTEGER PRIMARY KEY,
> NAME VARCHAR(100), NAME
> . . . . . . . . . . . . . . . .> VARCHAR(100), AGE INTEGER (64));
> No rows affected (0,229 seconds)
> 0: jdbc:ignite:thin://localhost> select * from person;
> ++++
> | ID | NAME |
>AGE |
> ++++
> ++++
> No rows selected (0,073 seconds)
> {code}
> This is on master branch. "NAME VARCHAR(100)" twice.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12663) Let's limit all thread pools' sizes to 5 in tests
[ https://issues.apache.org/jira/browse/IGNITE-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038302#comment-17038302 ] Stanilovsky Evgeny commented on IGNITE-12663: - [~ilyak] we need i.e. some kind of starvations in common tests coverage, does this fix not a simple masquerade of such a problems? > Let's limit all thread pools' sizes to 5 in tests > - > > Key: IGNITE-12663 > URL: https://issues.apache.org/jira/browse/IGNITE-12663 > Project: Ignite > Issue Type: Test >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The rationale is, it is very painful shoving through thread dumps of test > with N CPU threads in every pool. > Why 5? Rebalance thread pool is 4 by default, and system pool has to be bigger -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12687) Sqline throws unexpected exceptions on few specific arguments to !describe and !primarykeys
[
https://issues.apache.org/jira/browse/IGNITE-12687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038298#comment-17038298
]
Andrey Mashenkov commented on IGNITE-12687:
---
[~korlov], PR LGTM.
> Sqline throws unexpected exceptions on few specific arguments to !describe
> and !primarykeys
> ---
>
> Key: IGNITE-12687
> URL: https://issues.apache.org/jira/browse/IGNITE-12687
> Project: Ignite
> Issue Type: Bug
>Reporter: Konstantin Orlov
>Assignee: Konstantin Orlov
>Priority: Major
>
> %subj
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> !describe '
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1967)
> at sqlline.SqlLine.dequote(SqlLine.java:1322)
> at sqlline.SqlLine.split(SqlLine.java:1335)
> at sqlline.SqlLine.split(SqlLine.java:1154)
> at
> sqlline.AbstractCommandHandler.matches(AbstractCommandHandler.java:65)
> at sqlline.SqlLine.dispatch(SqlLine.java:774)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {noformat}
> when at least one table was created, following command also fails:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> !describe ?
> [17:19:31,763][SEVERE][client-connector-#110][JdbcRequestHandler] Failed to
> get columns metadata [reqId=108, req=JdbcMetaColumnsRequest [schemaName=null,
> tblName=?, colName=%]]
> java.util.regex.PatternSyntaxException: Dangling meta character '?' near
> index 0
> ?
> ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.sequence(Pattern.java:2123)
> at java.util.regex.Pattern.expr(Pattern.java:1996)
> at java.util.regex.Pattern.compile(Pattern.java:1696)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at java.util.regex.Pattern.matches(Pattern.java:1133)
> at java.lang.String.matches(String.java:2121)
> at
> org.apache.ignite.internal.processors.query.QueryUtils.matches(QueryUtils.java:1547)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcMetadataInfo.getColumnsMeta(JdbcMetadataInfo.java:170)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.getColumnsMeta(JdbcRequestHandler.java:1089)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:332)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:241)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:180)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:47)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:278)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:108)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:96)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at
> org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:69)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> Error: Dangling meta character '?' near index 0
> ?
> ^ (state=5,code=1)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12663) Let's limit all thread pools' sizes to 5 in tests
[ https://issues.apache.org/jira/browse/IGNITE-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-12663: - Summary: Let's limit all thread pools' sizes to 5 in tests (was: Let's limit all thread pools' sizes to 3 in tests) > Let's limit all thread pools' sizes to 5 in tests > - > > Key: IGNITE-12663 > URL: https://issues.apache.org/jira/browse/IGNITE-12663 > Project: Ignite > Issue Type: Test >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The rationale is, it is very painful shoving through thread dumps of test > with N CPU threads in every pool. > Why 3? It should allow all kinds of race conditions to still happen. Of > course, we should allow specific tests to override this value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12663) Let's limit all thread pools' sizes to 5 in tests
[ https://issues.apache.org/jira/browse/IGNITE-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-12663: - Description: The rationale is, it is very painful shoving through thread dumps of test with N CPU threads in every pool. Why 5? Rebalance thread pool is 4 by default, and system pool has to be bigger was: The rationale is, it is very painful shoving through thread dumps of test with N CPU threads in every pool. Why 3? It should allow all kinds of race conditions to still happen. Of course, we should allow specific tests to override this value. > Let's limit all thread pools' sizes to 5 in tests > - > > Key: IGNITE-12663 > URL: https://issues.apache.org/jira/browse/IGNITE-12663 > Project: Ignite > Issue Type: Test >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The rationale is, it is very painful shoving through thread dumps of test > with N CPU threads in every pool. > Why 5? Rebalance thread pool is 4 by default, and system pool has to be bigger -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12687) Sqline throws unexpected exceptions on few specific arguments to !describe and !primarykeys
[
https://issues.apache.org/jira/browse/IGNITE-12687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038290#comment-17038290
]
Konstantin Orlov commented on IGNITE-12687:
---
Pull request: https://github.com/apache/ignite/pull/7439
> Sqline throws unexpected exceptions on few specific arguments to !describe
> and !primarykeys
> ---
>
> Key: IGNITE-12687
> URL: https://issues.apache.org/jira/browse/IGNITE-12687
> Project: Ignite
> Issue Type: Bug
>Reporter: Konstantin Orlov
>Assignee: Konstantin Orlov
>Priority: Major
>
> %subj
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> !describe '
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1967)
> at sqlline.SqlLine.dequote(SqlLine.java:1322)
> at sqlline.SqlLine.split(SqlLine.java:1335)
> at sqlline.SqlLine.split(SqlLine.java:1154)
> at
> sqlline.AbstractCommandHandler.matches(AbstractCommandHandler.java:65)
> at sqlline.SqlLine.dispatch(SqlLine.java:774)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> {noformat}
> when at least one table was created, following command also fails:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> !describe ?
> [17:19:31,763][SEVERE][client-connector-#110][JdbcRequestHandler] Failed to
> get columns metadata [reqId=108, req=JdbcMetaColumnsRequest [schemaName=null,
> tblName=?, colName=%]]
> java.util.regex.PatternSyntaxException: Dangling meta character '?' near
> index 0
> ?
> ^
> at java.util.regex.Pattern.error(Pattern.java:1955)
> at java.util.regex.Pattern.sequence(Pattern.java:2123)
> at java.util.regex.Pattern.expr(Pattern.java:1996)
> at java.util.regex.Pattern.compile(Pattern.java:1696)
> at java.util.regex.Pattern.(Pattern.java:1351)
> at java.util.regex.Pattern.compile(Pattern.java:1028)
> at java.util.regex.Pattern.matches(Pattern.java:1133)
> at java.lang.String.matches(String.java:2121)
> at
> org.apache.ignite.internal.processors.query.QueryUtils.matches(QueryUtils.java:1547)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcMetadataInfo.getColumnsMeta(JdbcMetadataInfo.java:170)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.getColumnsMeta(JdbcRequestHandler.java:1089)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:332)
> at
> org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:241)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:180)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:47)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:278)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:108)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:96)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
> at
> org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:69)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> Error: Dangling meta character '?' near index 0
> ?
> ^ (state=5,code=1)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12688) Improve performance of index inline JAVA_OBJECT fields
Konstantin Orlov created IGNITE-12688: - Summary: Improve performance of index inline JAVA_OBJECT fields Key: IGNITE-12688 URL: https://issues.apache.org/jira/browse/IGNITE-12688 Project: Ignite Issue Type: Bug Reporter: Konstantin Orlov Assignee: Konstantin Orlov Inline JAVA_OBJECT may be reason of performance drop on index creation. The *root cause* is the low selectivity of current part of JAVA_OBJECT that is inlined. Now first N bytes of binary view of object is placed into inline space of the index. But the first offset where the two objects with the same type may be different is 8 (HASH_CODE_POS). With default inline = 10 we NEVER inline it: Inline format: 1 byte - type, 2 bytes - size >> 7 bytes - data; *My proposal:* - For metapage v4 (BPlusMetaIO) add flag *inlineObjectHash*; - use this flag to work in compatibility mode. - inline ONLY hash for JAVA_OBJECT fields for new indexes; Also this approach solves the inconsistent between comparison JAVA_OBJECT by inline and full value, because value comparator uses hash to compare object before compare byte arrays. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-10698) Get rid of @MXBeanParametersNames and @MXBeanParametersDescriptions
[
https://issues.apache.org/jira/browse/IGNITE-10698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038262#comment-17038262
]
Andrey N. Gura commented on IGNITE-10698:
-
[~l4ndsc4pe] Thanks for your effort. Tests set is impressive ) Nevertheless, I
have comments to PR (most of them just cosmetic). Could you please fix them?
Also I found that new tests expect {{AssertionError}} which will not be thrown
if assertions are disabled (it's default). I believe it is out of scope and
could be solved as separate issue if you wish.
> Get rid of @MXBeanParametersNames and @MXBeanParametersDescriptions
> ---
>
> Key: IGNITE-10698
> URL: https://issues.apache.org/jira/browse/IGNITE-10698
> Project: Ignite
> Issue Type: Task
>Reporter: Yakov Zhdanov
>Assignee: Lev Kiselev
>Priority: Major
> Labels: newbie, usability
> Fix For: 2.9
>
> Time Spent: 11h 50m
> Remaining Estimate: 0h
>
> {noformat}
> @MXBeanDescription("Returns or kills transactions matching the filter
> conditions.")
> @MXBeanParametersNames(
> {
> "minDuration",
> "minSize",
> "prj",
> "consistentIds",
> "xid",
> "lbRegex",
> "limit",
> "order",
> "detailed",
> "kill"
> }
> )
> @MXBeanParametersDescriptions(
> {
> "Minimum duration (seconds).",
> "Minimum size.",
> "Projection (servers|clients).",
> "Consistent ids (separated by comma).",
> "Transaction XID.",
> "Label regexp.",
> "Limit a number of transactions collected on each node.",
> "Order by DURATION|SIZE.",
> "Show detailed description, otherwise only count.",
> "Kill matching transactions (be careful)."
> }
> )
> {noformat}
> Above looks pretty ugly and is very error prone due to messing names and
> descr order or number of strings.
> I would suggest to introduce individual parameters annotations and get them
> via mtd.getParamterAnnotations() at runtime.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12687) Sqline throws unexpected exceptions on few specific arguments to !describe and !primarykeys
Konstantin Orlov created IGNITE-12687:
-
Summary: Sqline throws unexpected exceptions on few specific
arguments to !describe and !primarykeys
Key: IGNITE-12687
URL: https://issues.apache.org/jira/browse/IGNITE-12687
Project: Ignite
Issue Type: Bug
Reporter: Konstantin Orlov
Assignee: Konstantin Orlov
%subj
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> !describe '
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1967)
at sqlline.SqlLine.dequote(SqlLine.java:1322)
at sqlline.SqlLine.split(SqlLine.java:1335)
at sqlline.SqlLine.split(SqlLine.java:1154)
at
sqlline.AbstractCommandHandler.matches(AbstractCommandHandler.java:65)
at sqlline.SqlLine.dispatch(SqlLine.java:774)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
{noformat}
when at least one table was created, following command also fails:
{noformat}
0: jdbc:ignite:thin://127.0.0.1/> !describe ?
[17:19:31,763][SEVERE][client-connector-#110][JdbcRequestHandler] Failed to get
columns metadata [reqId=108, req=JdbcMetaColumnsRequest [schemaName=null,
tblName=?, colName=%]]
java.util.regex.PatternSyntaxException: Dangling meta character '?' near index 0
?
^
at java.util.regex.Pattern.error(Pattern.java:1955)
at java.util.regex.Pattern.sequence(Pattern.java:2123)
at java.util.regex.Pattern.expr(Pattern.java:1996)
at java.util.regex.Pattern.compile(Pattern.java:1696)
at java.util.regex.Pattern.(Pattern.java:1351)
at java.util.regex.Pattern.compile(Pattern.java:1028)
at java.util.regex.Pattern.matches(Pattern.java:1133)
at java.lang.String.matches(String.java:2121)
at
org.apache.ignite.internal.processors.query.QueryUtils.matches(QueryUtils.java:1547)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcMetadataInfo.getColumnsMeta(JdbcMetadataInfo.java:170)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.getColumnsMeta(JdbcRequestHandler.java:1089)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:332)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:241)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:180)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:47)
at
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:278)
at
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:108)
at
org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:96)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119)
at
org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:69)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
Error: Dangling meta character '?' near index 0
?
^ (state=5,code=1)
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-11422) Remove H2 console from documentation
[ https://issues.apache.org/jira/browse/IGNITE-11422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov resolved IGNITE-11422. - Resolution: Fixed > Remove H2 console from documentation > > > Key: IGNITE-11422 > URL: https://issues.apache.org/jira/browse/IGNITE-11422 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > > H2 console was deprecated as a part of IGNITE-11333. Need to remove all > mentions of "H2 console" from documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11422) Remove H2 console from documentation
[ https://issues.apache.org/jira/browse/IGNITE-11422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038217#comment-17038217 ] Artem Budnikov commented on IGNITE-11422: - removed H2 Console section from https://apacheignite-sql.readme.io/docs/performance-and-debugging > Remove H2 console from documentation > > > Key: IGNITE-11422 > URL: https://issues.apache.org/jira/browse/IGNITE-11422 > Project: Ignite > Issue Type: Task > Components: documentation >Reporter: Vladimir Ozerov >Assignee: Artem Budnikov >Priority: Major > > H2 console was deprecated as a part of IGNITE-11333. Need to remove all > mentions of "H2 console" from documentation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11847) Change note on the capacity planning page about memory usage
[ https://issues.apache.org/jira/browse/IGNITE-11847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038210#comment-17038210 ] Artem Budnikov commented on IGNITE-11847: - [~ezhuravl] What is the correct value? Or should this statement be removed completely? > Change note on the capacity planning page about memory usage > > > Key: IGNITE-11847 > URL: https://issues.apache.org/jira/browse/IGNITE-11847 > Project: Ignite > Issue Type: Bug > Components: documentation >Affects Versions: 2.7 >Reporter: Evgenii Zhuravlev >Assignee: Artem Budnikov >Priority: Major > > https://apacheignite.readme.io/docs/capacity-planning#calculating-memory-usage > It says that "Apache Ignite will typically add around 200 bytes overhead to > each entry.", but it's not true, I think it was applicable only for 1.x > versions, where everything was stored in heap -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12638) Classes persisted by DistributedMetaStorage are not IgniteDTO
[ https://issues.apache.org/jira/browse/IGNITE-12638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038202#comment-17038202 ] Maxim Muzafarov commented on IGNITE-12638: -- [~agura], [~ibessonov] Thank you, I'll cherry-pick the issue today to 2.8 > Classes persisted by DistributedMetaStorage are not IgniteDTO > - > > Key: IGNITE-12638 > URL: https://issues.apache.org/jira/browse/IGNITE-12638 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Fix For: 2.8 > > Time Spent: 1h > Remaining Estimate: 0h > > This has to be fixed to simplify future modification of component. > DistributedMetaStorageHistoryItem and DistributedMetaStorageVersion will be > persisted on disc so we need to have a reliable way to read them even when > classes will be updated in the future. IgniteDataTransferObject is the > standard option for such cases - it allows versioning of serialization format. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12663) Let's limit all thread pools' sizes to 3 in tests
[
https://issues.apache.org/jira/browse/IGNITE-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038201#comment-17038201
]
Ignite TC Bot commented on IGNITE-12663:
{panel:title=Branch: [pull/7429/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5050920buildTypeId=IgniteTests24Java8_RunAll]
> Let's limit all thread pools' sizes to 3 in tests
> -
>
> Key: IGNITE-12663
> URL: https://issues.apache.org/jira/browse/IGNITE-12663
> Project: Ignite
> Issue Type: Test
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The rationale is, it is very painful shoving through thread dumps of test
> with N CPU threads in every pool.
> Why 3? It should allow all kinds of race conditions to still happen. Of
> course, we should allow specific tests to override this value.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12384) [ML] Add an Encoder examples for all supported versions
[ https://issues.apache.org/jira/browse/IGNITE-12384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lev Kiselev reassigned IGNITE-12384: Assignee: Lev Kiselev > [ML] Add an Encoder examples for all supported versions > --- > > Key: IGNITE-12384 > URL: https://issues.apache.org/jira/browse/IGNITE-12384 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Alexey Zinoviev >Assignee: Lev Kiselev >Priority: Major > Labels: examples, newbie > > We have a few Encoders like OHE, StringIndexer and so on. > Please provide separate examples to illustrate the power of different encoders -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-11147) Re-balance cancellation occur by non-affected event
[ https://issues.apache.org/jira/browse/IGNITE-11147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Scherbakov updated IGNITE-11147: --- Reviewer: Alexey Scherbakov > Re-balance cancellation occur by non-affected event > --- > > Key: IGNITE-11147 > URL: https://issues.apache.org/jira/browse/IGNITE-11147 > Project: Ignite > Issue Type: Test > Components: cache >Affects Versions: 2.7 >Reporter: Sergey Antonov >Assignee: Vladislav Pyatkov >Priority: Critical > Fix For: 2.9 > > Time Spent: 20m > Remaining Estimate: 0h > > Re-balance cancels by non-affected events, for examples: > 1) joining non affinity node > 2) stating snapshot > 3) starting/stopping other cache > Try to skip as more as possible events instead of cancellation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12590) MERGE INTO query is failing on Ignite client node
[
https://issues.apache.org/jira/browse/IGNITE-12590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038173#comment-17038173
]
Taras Ledkov commented on IGNITE-12590:
---
The review issues are fixed.
[~amashenkov], please review and merge the patch.
> MERGE INTO query is failing on Ignite client node
> -
>
> Key: IGNITE-12590
> URL: https://issues.apache.org/jira/browse/IGNITE-12590
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Precondition: server nodes (any amount), webconsole is running.
> 1. Create the table as following:
> CREATE TABLE USERPUBSTATICDATA (BOOK VARCHAR, DESK VARCHAR, TRADERS VARCHAR,
> REGION VARCHAR, LOB VARCHAR, EXCLUDE VARCHAR, TRANSIT VARCHAR,
> MAPBOOKTOTHISBOOK VARCHAR, CONSTRAINT USERPUBSTATICDATA_PK PRIMARY KEY
> (BOOK,DESK)) WITH "template=replicated"
> 2. Execute merge into query:
> MERGE INTO USERPUBSTATICDATA(BOOK, DESK, TRADERS, REGION, LOB, EXCLUDE,
> TRANSIT, MAPBOOKTOTHISBOOK) VALUES('CADOIS', 'FRT TOR', 'Robin Das/Dave
> Carlson', 'Toronto', 'FRT', null, null, 'CADOIS');
> Step 2 is successfull on Web Console and called on IgniteCache from the
> server node, but fails when called from the Ignite client node with exception:
> {code}
> javax.cache.CacheException: Invalid column name in KEYS clause of MERGE - it
> may include only key and/or affinity columns: BOOK
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12433) Possible to create table with duplicate definition of column
[
https://issues.apache.org/jira/browse/IGNITE-12433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038160#comment-17038160
]
Sergey Uttsel commented on IGNITE-12433:
[~jooger], please review new changes.
> Possible to create table with duplicate definition of column
>
>
> Key: IGNITE-12433
> URL: https://issues.apache.org/jira/browse/IGNITE-12433
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.8
>Reporter: Ilya Kasnacheev
>Assignee: Sergey Uttsel
>Priority: Minor
> Labels: newbie
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> {code}
> sqlline version 1.3.0
> sqlline> !connect jdbc:ignite:thin://localhost
> Enter username for jdbc:ignite:thin://localhost:
> Enter password for jdbc:ignite:thin://localhost:
> 0: jdbc:ignite:thin://localhost> CREATE TABLE Person(ID INTEGER PRIMARY KEY,
> NAME VARCHAR(100), NAME
> . . . . . . . . . . . . . . . .> VARCHAR(100), AGE INTEGER (64));
> No rows affected (0,229 seconds)
> 0: jdbc:ignite:thin://localhost> select * from person;
> ++++
> | ID | NAME |
>AGE |
> ++++
> ++++
> No rows selected (0,073 seconds)
> {code}
> This is on master branch. "NAME VARCHAR(100)" twice.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12433) Possible to create table with duplicate definition of column
[
https://issues.apache.org/jira/browse/IGNITE-12433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038161#comment-17038161
]
Ignite TC Bot commented on IGNITE-12433:
{panel:title=Branch: [pull/7404/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5050660buildTypeId=IgniteTests24Java8_RunAll]
> Possible to create table with duplicate definition of column
>
>
> Key: IGNITE-12433
> URL: https://issues.apache.org/jira/browse/IGNITE-12433
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.8
>Reporter: Ilya Kasnacheev
>Assignee: Sergey Uttsel
>Priority: Minor
> Labels: newbie
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> {code}
> sqlline version 1.3.0
> sqlline> !connect jdbc:ignite:thin://localhost
> Enter username for jdbc:ignite:thin://localhost:
> Enter password for jdbc:ignite:thin://localhost:
> 0: jdbc:ignite:thin://localhost> CREATE TABLE Person(ID INTEGER PRIMARY KEY,
> NAME VARCHAR(100), NAME
> . . . . . . . . . . . . . . . .> VARCHAR(100), AGE INTEGER (64));
> No rows affected (0,229 seconds)
> 0: jdbc:ignite:thin://localhost> select * from person;
> ++++
> | ID | NAME |
>AGE |
> ++++
> ++++
> No rows selected (0,073 seconds)
> {code}
> This is on master branch. "NAME VARCHAR(100)" twice.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-9325) Add an ability to make a sound after a complete execution to all command-line utilities
[ https://issues.apache.org/jira/browse/IGNITE-9325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-9325: - Summary: Add an ability to make a sound after a complete execution to all command-line utilities (was: Add to all command-line utility ability to make sound after complite execution) > Add an ability to make a sound after a complete execution to all command-line > utilities > --- > > Key: IGNITE-9325 > URL: https://issues.apache.org/jira/browse/IGNITE-9325 > Project: Ignite > Issue Type: Improvement > Components: examples >Affects Versions: 2.5 >Reporter: ARomantsov >Assignee: Artsiom Panko >Priority: Major > Labels: command-line, newbie > Fix For: 2.9 > > > Often I work simultaneously on several clusters over ssh and there are > situations when I forget to check that the first cluster has completed the > command (for example, activation), while working on the second. > It would be great if there was an option to ignite command-line utilities > that would allow some sort of sound (or system beep) to be played after the > command got executed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9325) Add to all command-line utility ability to make sound after complite execution
[ https://issues.apache.org/jira/browse/IGNITE-9325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-9325: - Description: Often I work simultaneously on several clusters over ssh and there are situations when I forget to check that the first cluster has completed the command (for example, activation), while working on the second. It would be great if there was an option to ignite command-line utilities that would allow some sort of sound (or system beep) to be played after the command got executed. was: Often I work simultaneously on several clusters over ssh and there are situations when I forget to check that the first cluster has completed the command (for example, activation), while working on the second. Because of this, I would like to have same functionality in the product > Add to all command-line utility ability to make sound after complite execution > -- > > Key: IGNITE-9325 > URL: https://issues.apache.org/jira/browse/IGNITE-9325 > Project: Ignite > Issue Type: Improvement > Components: examples >Affects Versions: 2.5 >Reporter: ARomantsov >Assignee: Artsiom Panko >Priority: Major > Labels: command-line, newbie > Fix For: 2.9 > > > Often I work simultaneously on several clusters over ssh and there are > situations when I forget to check that the first cluster has completed the > command (for example, activation), while working on the second. > It would be great if there was an option to ignite command-line utilities > that would allow some sort of sound (or system beep) to be played after the > command got executed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-9325) Add to all command-line utility ability to make sound after complite execution
[ https://issues.apache.org/jira/browse/IGNITE-9325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17038152#comment-17038152 ] Ilya Kasnacheev commented on IGNITE-9325: - [~artsiom_panko] you don't need to reproduce this. Have you checked the title of this ticket? I think it's self-explanatory. > Add to all command-line utility ability to make sound after complite execution > -- > > Key: IGNITE-9325 > URL: https://issues.apache.org/jira/browse/IGNITE-9325 > Project: Ignite > Issue Type: Improvement > Components: examples >Affects Versions: 2.5 >Reporter: ARomantsov >Assignee: Artsiom Panko >Priority: Major > Labels: command-line, newbie > Fix For: 2.9 > > > Often I work simultaneously on several clusters over ssh and there are > situations when I forget to check that the first cluster has completed the > command (for example, activation), while working on the second. > Because of this, I would like to have same functionality in the product -- This message was sent by Atlassian Jira (v8.3.4#803005)
