[jira] [Commented] (IGNITE-8386) SQL: Make sure PK index do not use wrapped object
[
https://issues.apache.org/jira/browse/IGNITE-8386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683343#comment-16683343
]
Vladimir Ozerov commented on IGNITE-8386:
-
[~jooger], two comments from my side:
1) Please provide TC Bot visa confirming that there are no new failures
2) I noticed that we use different set of columns for PK index. However, we use
the same set of columns for both "old" and "new" modes for secondary indexes.
Shouldn't we unwrap secondary index columns as well? We can do that in separate
ticket, but chances that changes will be minimal, provided that we already have
all necessary infrastructure.
> SQL: Make sure PK index do not use wrapped object
> -
>
> Key: IGNITE-8386
> URL: https://issues.apache.org/jira/browse/IGNITE-8386
> Project: Ignite
> Issue Type: Task
> Components: sql
>Affects Versions: 2.4
>Reporter: Vladimir Ozerov
>Assignee: Yury Gerzhedovich
>Priority: Major
> Labels: iep-19, performance
> Fix For: 2.8
>
>
> Currently PK may be built over the whole {{_KEY}} column, i.e. the whole
> binary object. This could happen in two cases:
> 1) Composite PK
> 2) Plain PK but with {{WRAP_KEY}} option.
> This is critical performance issue for two reasons:
> 1) This index is effectively useless and cannot be used in any sensible
> queries; it just wastes space and makes updates slower
> 2) Binary object typically has common header bytes what may lead to excessive
> number of comparisons during index update.
> To mitigate the problem we need to ensure that index is *never* built over
> {{_KEY}}, Instead, we must always extract target columns and build normal
> index over them.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9274) Pass transaction label to cache events
[
https://issues.apache.org/jira/browse/IGNITE-9274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683335#comment-16683335
]
Vladimir Ozerov commented on IGNITE-9274:
-
And one more run: https://ci.ignite.apache.org/viewQueued.html?itemId=2297887
> Pass transaction label to cache events
> --
>
> Key: IGNITE-9274
> URL: https://issues.apache.org/jira/browse/IGNITE-9274
> Project: Ignite
> Issue Type: Task
> Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Yury Gerzhedovich
>Priority: Major
> Fix For: 2.8
>
>
> It is possible to set transaction label - \{{IgniteTransactions.withLabel}}.
> We need to pass this label to related cache and transaction events:
> 1) EVT_TX_STARTED, EVT_TX_COMMITTED, EVT_TX_ROLLED_BACK, EVT_TX_SUSPENDED,
> EVT_TX_RESUMED
> 2) EVT_CACHE_OBJECT_READ, EVT_CACHE_OBJECT_PUT, EVT_CACHE_OBJECT_REMOVED
> For TX events most probably everything is already passed (see
> \{{TransactionStateChangedEvent}}), we only need to add tests.
> For put/remove events we need to investigate correct messages to pass label,
> prepare requests appear to be good candidates for this.
> For read operation we may need to add pass label to get/lock requests
> ({{GridNearLockRequest}}, {{GridNearGetRequest}},
> {{GridNearSingleGetRequest}}).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9897) Quering with PDO returns null for all column values except the 1st one
[
https://issues.apache.org/jira/browse/IGNITE-9897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683332#comment-16683332
]
Vladimir Ozerov commented on IGNITE-9897:
-
[~isapego], looks good to me.
> Quering with PDO returns null for all column values except the 1st one
> --
>
> Key: IGNITE-9897
> URL: https://issues.apache.org/jira/browse/IGNITE-9897
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 2.6
> Environment: CentOS
>Reporter: Roman Shtykh
>Assignee: Igor Sapego
>Priority: Major
> Attachments: odbc.log, phpPDO2.out, phpPdo.out, unixOdbc.log
>
>
> Using _odbc_connect_ returns all column values, but with _PDO_ only the 1st
> one – all the rest are null.
> Reproduced on CentOS.
> # Start a server node with Ignite CPP
> # Run odbc-example (which will create two tables)
> # Run a simple PHP script
> {code:php}
> try {
> echo PHP_EOL,PHP_EOL,"# Using PDO",PHP_EOL;
> $dbh = new PDO('odbc:ApacheIgnite');
> $dbh->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
> $sql = 'SELECT * FROM "Person".Person';
> $data = $dbh->query($sql);
> foreach($data as $row) {
> var_export($row);
> }
> echo PHP_EOL,PHP_EOL,"# Using odbc_*( ) Functions",PHP_EOL;
>
> $conn = odbc_connect('ApacheIgnite','','');
> $rs = odbc_exec($conn, $sql);
>
> while($row = odbc_fetch_array($rs)) {
> var_export($row);
> }
>
> } catch (PDOException $e) {
> print "Error!: " . $e->getMessage() . "\n";
> die();
> }
> ?>
> {code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10009) ODBC: SQLColumns does not work for tables with escape sequences in name
[
https://issues.apache.org/jira/browse/IGNITE-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683330#comment-16683330
]
Vladimir Ozerov commented on IGNITE-10009:
--
[~isapego], looks good to me.
> ODBC: SQLColumns does not work for tables with escape sequences in name
> ---
>
> Key: IGNITE-10009
> URL: https://issues.apache.org/jira/browse/IGNITE-10009
> Project: Ignite
> Issue Type: Bug
> Components: odbc
>Affects Versions: 2.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: odbc
> Fix For: 2.8
>
>
> Table names with escaped underscore '\_' or percent '\%' characters is not
> recognized by the ODBC driver. I.e. the following table pattern:
> {noformat}
> TEST\_TABLE
> {noformat}
> Should match the following table:
> {noformat}
> TEST_TABLE
> {noformat}
> But currently it does not. Needs to be fixed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10053) IgniteAbstractBenchmark: NPE in waitForNodes
[
https://issues.apache.org/jira/browse/IGNITE-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-10053:
-
Fix Version/s: 2.8
> IgniteAbstractBenchmark: NPE in waitForNodes
>
>
> Key: IGNITE-10053
> URL: https://issues.apache.org/jira/browse/IGNITE-10053
> Project: Ignite
> Issue Type: Bug
> Components: yardstick
>Reporter: Pavel Kuznetsov
>Assignee: Pavel Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> {noformat}
> <14:58:02> Failed to set up benchmark drivers (will shutdown
> and exit).
> java.lang.NullPointerException
> <-->at
> org.apache.ignite.yardstick.IgniteAbstractBenchmark.topologyContainsId(IgniteAbstractBenchmark.java:182)
> <-->at
> org.apache.ignite.yardstick.IgniteAbstractBenchmark.nodesStarted(IgniteAbstractBenchmark.java:169)
> <-->at
> org.apache.ignite.yardstick.IgniteAbstractBenchmark.waitForNodes(IgniteAbstractBenchmark.java:144)
> <-->at
> org.apache.ignite.yardstick.IgniteAbstractBenchmark.setUp(IgniteAbstractBenchmark.java:68)
> <-->at
> org.apache.ignite.yardstick.cache.IgniteCacheAbstractBenchmark.setUp(IgniteCacheAbstractBenchmark.java:108)
> <-->at
> org.yardstickframework.BenchmarkDriverStartUp.main(BenchmarkDriverStartUp.java:130
> {noformat}
> 1) Given 4 server nodes in the cluster
> 2) Cluster gets activated
> 3) client nodes join topology and start waiting for nodes
> 4) on one node NPE is thrown
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9904) CPP Thin: Implement atomic part of Cache API for C++ thin client
[
https://issues.apache.org/jira/browse/IGNITE-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683325#comment-16683325
]
Vladimir Ozerov commented on IGNITE-9904:
-
[~isapego], looks good to me.
> CPP Thin: Implement atomic part of Cache API for C++ thin client
>
>
> Key: IGNITE-9904
> URL: https://issues.apache.org/jira/browse/IGNITE-9904
> Project: Ignite
> Issue Type: New Feature
> Components: thin client
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Labels: cpp
> Fix For: 2.8
>
>
> Need to implement atomic part of cache API:
> # {{ReplaceIfEquals}}
> # {{RemoveIfEquals}}
> # {{GetAndPut}}
> # {{GetAndRemove}}
> # {{GetAndReplace}}
> # {{PutIfAbsent}}
> # {{GetAndPutIfAbsent}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10053) IgniteAbstractBenchmark: NPE in waitForNodes
[
https://issues.apache.org/jira/browse/IGNITE-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov updated IGNITE-10053:
-
Ignite Flags: (was: Docs Required)
> IgniteAbstractBenchmark: NPE in waitForNodes
>
>
> Key: IGNITE-10053
> URL: https://issues.apache.org/jira/browse/IGNITE-10053
> Project: Ignite
> Issue Type: Bug
> Components: yardstick
>Reporter: Pavel Kuznetsov
>Assignee: Pavel Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> {noformat}
> <14:58:02> Failed to set up benchmark drivers (will shutdown
> and exit).
> java.lang.NullPointerException
> <-->at
> org.apache.ignite.yardstick.IgniteAbstractBenchmark.topologyContainsId(IgniteAbstractBenchmark.java:182)
> <-->at
> org.apache.ignite.yardstick.IgniteAbstractBenchmark.nodesStarted(IgniteAbstractBenchmark.java:169)
> <-->at
> org.apache.ignite.yardstick.IgniteAbstractBenchmark.waitForNodes(IgniteAbstractBenchmark.java:144)
> <-->at
> org.apache.ignite.yardstick.IgniteAbstractBenchmark.setUp(IgniteAbstractBenchmark.java:68)
> <-->at
> org.apache.ignite.yardstick.cache.IgniteCacheAbstractBenchmark.setUp(IgniteCacheAbstractBenchmark.java:108)
> <-->at
> org.yardstickframework.BenchmarkDriverStartUp.main(BenchmarkDriverStartUp.java:130
> {noformat}
> 1) Given 4 server nodes in the cluster
> 2) Cluster gets activated
> 3) client nodes join topology and start waiting for nodes
> 4) on one node NPE is thrown
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9996) Investigate possible performance drop in FSYNC mode for ignite-2.7 compared to ignite-2.6
[ https://issues.apache.org/jira/browse/IGNITE-9996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683313#comment-16683313 ] ASF GitHub Bot commented on IGNITE-9996: GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/5362 IGNITE-9996: comment out pageSize for encmgr You can merge this pull request into a Git repository by running: $ git pull https://github.com/nizhikov/ignite IGNITE-9996-2 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5362.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5362 commit 9ca5037f696d83989e336d0c1d4066830ab14bb4 Author: Nikolay Izhikov Date: 2018-11-12T07:07:25Z IGNITE-9996: comment out pageSize for encmgr > Investigate possible performance drop in FSYNC mode for ignite-2.7 compared > to ignite-2.6 > - > > Key: IGNITE-9996 > URL: https://issues.apache.org/jira/browse/IGNITE-9996 > Project: Ignite > Issue Type: Task >Reporter: Alexey Goncharuk >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.7 > > Attachments: Screen Shot 2018-10-29 at 3.30.51 PM.png, Screen Shot > 2018-10-31 at 10.30.26 AM.png, Screen Shot 2018-11-08 at 2.38.06 PM.png > > > As per the latest reports we probably have a performance drop around 5-8% on > write benchmarks in FSYNC mode. The cause needs to be investigated and fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10196) Change scope of kafka-clients-*-test dependency to test
[ https://issues.apache.org/jira/browse/IGNITE-10196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683301#comment-16683301 ] ASF GitHub Bot commented on IGNITE-10196: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5356 > Change scope of kafka-clients-*-test dependency to test > --- > > Key: IGNITE-10196 > URL: https://issues.apache.org/jira/browse/IGNITE-10196 > Project: Ignite > Issue Type: Bug > Components: build >Affects Versions: 2.7 >Reporter: Sergey Kozlov >Assignee: Maxim Pudov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8871) TDE - Phase-1. Documentation
[ https://issues.apache.org/jira/browse/IGNITE-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-8871: -- Assignee: Artem Budnikov (was: Nikolay Izhikov) > TDE - Phase-1. Documentation > > > Key: IGNITE-8871 > URL: https://issues.apache.org/jira/browse/IGNITE-8871 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 2.5 >Reporter: Nikolay Izhikov >Assignee: Artem Budnikov >Priority: Major > Labels: documentation > Fix For: 2.7 > > > TDE feature should be documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10196) Change scope of kafka-clients-*-test dependency to test
[ https://issues.apache.org/jira/browse/IGNITE-10196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-10196: - Ignite Flags: (was: Docs Required) > Change scope of kafka-clients-*-test dependency to test > --- > > Key: IGNITE-10196 > URL: https://issues.apache.org/jira/browse/IGNITE-10196 > Project: Ignite > Issue Type: Bug > Components: build >Affects Versions: 2.7 >Reporter: Sergey Kozlov >Assignee: Maxim Pudov >Priority: Major > Fix For: 2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8871) TDE - Phase-1. Documentation
[ https://issues.apache.org/jira/browse/IGNITE-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683283#comment-16683283 ] Artem Budnikov commented on IGNITE-8871: [~pgarg] please review the page: [https://apacheignite.readme.io/v2.6/docs/transparent-data-encryption] > TDE - Phase-1. Documentation > > > Key: IGNITE-8871 > URL: https://issues.apache.org/jira/browse/IGNITE-8871 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 2.5 >Reporter: Nikolay Izhikov >Assignee: Artem Budnikov >Priority: Major > Labels: documentation > Fix For: 2.7 > > > TDE feature should be documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-8871) TDE - Phase-1. Documentation
[ https://issues.apache.org/jira/browse/IGNITE-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reassigned IGNITE-8871: -- Assignee: Prachi Garg (was: Artem Budnikov) > TDE - Phase-1. Documentation > > > Key: IGNITE-8871 > URL: https://issues.apache.org/jira/browse/IGNITE-8871 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 2.5 >Reporter: Nikolay Izhikov >Assignee: Prachi Garg >Priority: Major > Labels: documentation > Fix For: 2.7 > > > TDE feature should be documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (IGNITE-8871) TDE - Phase-1. Documentation
[ https://issues.apache.org/jira/browse/IGNITE-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Artem Budnikov reopened IGNITE-8871: > TDE - Phase-1. Documentation > > > Key: IGNITE-8871 > URL: https://issues.apache.org/jira/browse/IGNITE-8871 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Affects Versions: 2.5 >Reporter: Nikolay Izhikov >Assignee: Artem Budnikov >Priority: Major > Labels: documentation > Fix For: 2.7 > > > TDE feature should be documented. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6600) Web Console: Make a design of 403 and 404 pages
[ https://issues.apache.org/jira/browse/IGNITE-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683271#comment-16683271 ] Alexander Kalinin commented on IGNITE-6600: --- [~Klaster_1] I've made changes upon review. Please check and ping [~kuaw26] if everything is ok. > Web Console: Make a design of 403 and 404 pages > --- > > Key: IGNITE-6600 > URL: https://issues.apache.org/jira/browse/IGNITE-6600 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.8 > > Attachments: 403-page.png, 404-page.png > > Original Estimate: 8h > Time Spent: 8h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-10101) Web Console: Filed to get cache list on Query page.
[ https://issues.apache.org/jira/browse/IGNITE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Konstantinov resolved IGNITE-10101. - Resolution: Fixed Assignee: Alexey Kuznetsov (was: Pavel Konstantinov) > Web Console: Filed to get cache list on Query page. > --- > > Key: IGNITE-10101 > URL: https://issues.apache.org/jira/browse/IGNITE-10101 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.8 >Reporter: Vasiliy Sisko >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > Attachments: ignite-10101.png > > > On opening of Queries page: > # For scan query field with cache selection is empty > # For query list of caches is empty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10101) Web Console: Filed to get cache list on Query page.
[ https://issues.apache.org/jira/browse/IGNITE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683256#comment-16683256 ] Pavel Konstantinov commented on IGNITE-10101: - The initial error on Query screen is fixed. The error with demo mode needs to be extracted to the separated issue. > Web Console: Filed to get cache list on Query page. > --- > > Key: IGNITE-10101 > URL: https://issues.apache.org/jira/browse/IGNITE-10101 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.8 >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > Attachments: ignite-10101.png > > > On opening of Queries page: > # For scan query field with cache selection is empty > # For query list of caches is empty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10101) Web Console: Filed to get cache list on Query page.
[ https://issues.apache.org/jira/browse/IGNITE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reassigned IGNITE-10101: --- Assignee: Pavel Konstantinov (was: Andrey Novikov) > Web Console: Filed to get cache list on Query page. > --- > > Key: IGNITE-10101 > URL: https://issues.apache.org/jira/browse/IGNITE-10101 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.8 >Reporter: Vasiliy Sisko >Assignee: Pavel Konstantinov >Priority: Major > Fix For: 2.8 > > Attachments: ignite-10101.png > > > On opening of Queries page: > # For scan query field with cache selection is empty > # For query list of caches is empty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10101) Web Console: Filed to get cache list on Query page.
[ https://issues.apache.org/jira/browse/IGNITE-10101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683207#comment-16683207 ] Andrey Novikov commented on IGNITE-10101: - [~pkonstantinov], I can't reproduce this problem on master locally. Please attach more detailed steps or create reproducible example. > Web Console: Filed to get cache list on Query page. > --- > > Key: IGNITE-10101 > URL: https://issues.apache.org/jira/browse/IGNITE-10101 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.8 >Reporter: Vasiliy Sisko >Assignee: Andrey Novikov >Priority: Major > Fix For: 2.8 > > Attachments: ignite-10101.png > > > On opening of Queries page: > # For scan query field with cache selection is empty > # For query list of caches is empty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-6600) Web Console: Make a design of 403 and 404 pages
[ https://issues.apache.org/jira/browse/IGNITE-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683205#comment-16683205 ] Alexey Kuznetsov commented on IGNITE-6600: -- [~alexdel], Looks good to me, but I think that [~Klaster_1] should also take a look. > Web Console: Make a design of 403 and 404 pages > --- > > Key: IGNITE-6600 > URL: https://issues.apache.org/jira/browse/IGNITE-6600 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.8 > > Attachments: 403-page.png, 404-page.png > > Original Estimate: 8h > Time Spent: 8h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-6600) Web Console: Make a design of 403 and 404 pages
[ https://issues.apache.org/jira/browse/IGNITE-6600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-6600: - Fix Version/s: 2.8 > Web Console: Make a design of 403 and 404 pages > --- > > Key: IGNITE-6600 > URL: https://issues.apache.org/jira/browse/IGNITE-6600 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Minor > Fix For: 2.8 > > Attachments: 403-page.png, 404-page.png > > Original Estimate: 8h > Time Spent: 8h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10213) Add eclipse-link JPA implementation for L2 cache
[ https://issues.apache.org/jira/browse/IGNITE-10213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Li Xu updated IGNITE-10213: --- Description: Sometime JavaEE applications with JPA that using eclipse-link want to use Ignite as a L2 cache, but only Hibernates and MyBatis was implemented currently. Add the L2 cache implementation of eclipse-link will be welcomed. was: Several JavaEE applications with JPA that using eclipse-link want to use Ignite as a L2 cache, but only Hibernates and MyBatis was implemented currently. Add the L2 cache implementation of eclipse-link will be welcomed. > Add eclipse-link JPA implementation for L2 cache > > > Key: IGNITE-10213 > URL: https://issues.apache.org/jira/browse/IGNITE-10213 > Project: Ignite > Issue Type: New Feature >Reporter: Li Xu >Priority: Major > Labels: L2Cache, features > > Sometime JavaEE applications with JPA that using eclipse-link want to use > Ignite as a L2 cache, but only Hibernates and MyBatis was implemented > currently. > Add the L2 cache implementation of eclipse-link will be welcomed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10214) Web console: dependency to open source JDBS 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 ] Vasiliy Sisko reassigned IGNITE-10214: -- Assignee: Vasiliy Sisko > Web console: dependency to open source JDBS 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 > > 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] [Created] (IGNITE-10214) Web console: dependency to open source JDBS driver is not generated in the project's pom file
Pavel Konstantinov created IGNITE-10214: --- Summary: Web console: dependency to open source JDBS 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 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] [Created] (IGNITE-10213) Add eclipse-link JPA implementation for L2 cache
Li Xu created IGNITE-10213: -- Summary: Add eclipse-link JPA implementation for L2 cache Key: IGNITE-10213 URL: https://issues.apache.org/jira/browse/IGNITE-10213 Project: Ignite Issue Type: New Feature Reporter: Li Xu Several JavaEE applications with JPA that using eclipse-link want to use Ignite as a L2 cache, but only Hibernates and MyBatis was implemented currently. Add the L2 cache implementation of eclipse-link will be welcomed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10207) Missed loss policy checks
[ https://issues.apache.org/jira/browse/IGNITE-10207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683044#comment-16683044 ] ASF GitHub Bot commented on IGNITE-10207: - GitHub user dgovorukhin opened a pull request: https://github.com/apache/ignite/pull/5360 IGNITE-10207 Fix missed loss policy checks You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10207 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5360.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #5360 commit 162e57381f1edd3f3b3a252894fe40231c332474 Author: Dmitriy Govorukhin Date: 2018-11-09T22:09:12Z IGNITE-10207 rework lossPolicy tests Signed-off-by: Dmitriy Govorukhin commit 19d8d902f6ee2fb77244549a1a891a901ea2386d Author: Dmitriy Govorukhin Date: 2018-11-11T22:16:18Z IGNITE-10207 fix checking lost partition for many cases Signed-off-by: Dmitriy Govorukhin > Missed loss policy checks > - > > Key: IGNITE-10207 > URL: https://issues.apache.org/jira/browse/IGNITE-10207 > Project: Ignite > Issue Type: Bug > Components: cache >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.8 > > > In some cases (client reconnect, new client join, etc) PartitionLossPolicy > may incorrectly validate operation. Return null for READ_ONLY_SAFE for loss > partition. > To reproduce run CacheResultIsNotNullOnPartitionLossTest (1000 times) with > random node stop. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10212) Add information about topology version in all messages related with PME
Sergey Antonov created IGNITE-10212: --- Summary: Add information about topology version in all messages related with PME Key: IGNITE-10212 URL: https://issues.apache.org/jira/browse/IGNITE-10212 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Fix For: 2.8 We need to see topology version in all messages related with partitions map exchange. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8717) Move persisted cache configuration to metastore
[ https://issues.apache.org/jira/browse/IGNITE-8717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683013#comment-16683013 ] Alexei Scherbakov commented on IGNITE-8717: --- [~antonovsergey93], I left review comments in PR, please address them. > Move persisted cache configuration to metastore > --- > > Key: IGNITE-8717 > URL: https://issues.apache.org/jira/browse/IGNITE-8717 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Sergey Antonov >Priority: Major > > Currently, we persist cache configuration to local files which resulted in > several inconsistencies when a node misses configuration update (create > index, cache destroy, etc). > I think the cache configuration should be saved to the metastore the same way > as baseline topology is saved. Same mechanics should be used for conflicting > configuration updates resolution. > Along with cache configuration, it also makes sense to move marshaller and > binary metadata to the metastore. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10209) some tests in IgniteExamplesMLTestSuite fail with FileNotFoundException at SandboxMLCache#fillCacheWith(MLSandboxDatasets)
[
https://issues.apache.org/jira/browse/IGNITE-10209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683003#comment-16683003
]
ASF GitHub Bot commented on IGNITE-10209:
-
Github user oignatenko closed the pull request at:
https://github.com/apache/ignite/pull/5359
> some tests in IgniteExamplesMLTestSuite fail with FileNotFoundException at
> SandboxMLCache#fillCacheWith(MLSandboxDatasets)
> --
>
> Key: IGNITE-10209
> URL: https://issues.apache.org/jira/browse/IGNITE-10209
> Project: Ignite
> Issue Type: Bug
> Components: ml
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.8
>
>
> Tests for examples that use
> {{SandboxMLCache#fillCacheWith(MLSandboxDatasets)}} fail with FNFE:
> {noformat}
> [ERROR] Tests run: 34, Failures: 0, Errors: 13, Skipped: 0, Time elapsed:
> 638.752 s <<< FAILURE! - in
> org.apache.ignite.testsuites.IgniteExamplesMLTestSuite
> [ERROR]
> testExample(org.apache.ignite.examples.ml.KMeansClusterizationExampleSelfName)
> Time elapsed: 21.701 s <<< ERROR!
> java.io.FileNotFoundException:
> examples\src\main\resources\datasets\two_classed_iris.csv (Системе не удается
> найти указанный путь)
> at
> org.apache.ignite.examples.ml.KMeansClusterizationExampleSelfName.testExample(KMeansClusterizationExampleSelfName.java)
> [ERROR]
> testExample(org.apache.ignite.examples.ml.KNNClassificationExampleSelfName)
> Time elapsed: 13.81 s <<< ERROR!
> java.io.FileNotFoundException: examples\src\main\resources\datasets\iris.txt
> (Системе не удается найти указанный путь)
> at
> org.apache.ignite.examples.ml.KNNClassificationExampleSelfName.testExample(KNNClassificationExampleSelfName.java)
> [ERROR]
> testExample(org.apache.ignite.examples.ml.KNNRegressionExampleSelfName) Time
> elapsed: 13.633 s <<< ERROR!
> java.io.FileNotFoundException:
> examples\src\main\resources\datasets\cleared_machines.csv (Системе не удается
> найти указанный путь)
> at
> org.apache.ignite.examples.ml.KNNRegressionExampleSelfName.testExample(KNNRegressionExampleSelfName.java)
> [ERROR]
> testExample(org.apache.ignite.examples.ml.LinearRegressionLSQRTrainerExampleSelfName)
> Time elapsed: 13.71 s <<< ERROR!
> java.io.FileNotFoundException:
> examples\src\main\resources\datasets\mortalitydata.csv (Системе не удается
> найти указанный путь)
> at
> org.apache.ignite.examples.ml.LinearRegressionLSQRTrainerExampleSelfName.testExample(LinearRegressionLSQRTrainerExampleSelfName.java)
> [ERROR]
> testExample(org.apache.ignite.examples.ml.LinearRegressionLSQRTrainerWithMinMaxScalerExampleSelfName)
> Time elapsed: 13.728 s <<< ERROR!
> java.io.FileNotFoundException:
> examples\src\main\resources\datasets\mortalitydata.csv (Системе не удается
> найти указанный путь)
> at
> org.apache.ignite.examples.ml.LinearRegressionLSQRTrainerWithMinMaxScalerExampleSelfName.testExample(LinearRegressionLSQRTrainerWithMinMaxScalerExampleSelfName.java)
> [ERROR]
> testExample(org.apache.ignite.examples.ml.LinearRegressionSGDTrainerExampleSelfName)
> Time elapsed: 13.874 s <<< ERROR!
> java.io.FileNotFoundException:
> examples\src\main\resources\datasets\mortalitydata.csv (Системе не удается
> найти указанный путь)
> at
> org.apache.ignite.examples.ml.LinearRegressionSGDTrainerExampleSelfName.testExample(LinearRegressionSGDTrainerExampleSelfName.java)
> [ERROR]
> testExample(org.apache.ignite.examples.ml.LogisticRegressionSGDTrainerExampleSelfName)
> Time elapsed: 13.694 s <<< ERROR!
> java.io.FileNotFoundException:
> examples\src\main\resources\datasets\two_classed_iris.csv (Системе не удается
> найти указанный путь)
> at
> org.apache.ignite.examples.ml.LogisticRegressionSGDTrainerExampleSelfName.testExample(LogisticRegressionSGDTrainerExampleSelfName.java)
> [ERROR]
> testExample(org.apache.ignite.examples.ml.LogRegressionMultiClassClassificationExampleSelfName)
> Time elapsed: 13.823 s <<< ERROR!
> java.io.FileNotFoundException:
> examples\src\main\resources\datasets\glass_identification.csv (Системе не
> удается найти указанный путь)
> at
> org.apache.ignite.examples.ml.LogRegressionMultiClassClassificationExampleSelfName.testExample(LogRegressionMultiClassClassificationExampleSelfName.java)
> [ERROR]
> testExample(org.apache.ignite.examples.ml.TrainTestDatasetSplitterExampleSelfName)
> Time elapsed: 12.875 s <<< ERROR!
> java.io.FileNotFoundException:
> examples\src\main\resources\datasets\mortalitydata.csv (Системе не удается
> найти указанный путь)
> at
>
[jira] [Commented] (IGNITE-9558) Avoid changing AffinityTopologyVersion on client connect when possible
[ https://issues.apache.org/jira/browse/IGNITE-9558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682961#comment-16682961 ] Ilya Lantukh commented on IGNITE-9558: -- [~agoncharuk], thanks for uncovering that issue! I've fixed it, please review my PR again. > Avoid changing AffinityTopologyVersion on client connect when possible > -- > > Key: IGNITE-9558 > URL: https://issues.apache.org/jira/browse/IGNITE-9558 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Alexey Goncharuk >Assignee: Ilya Lantukh >Priority: Major > Fix For: 2.8 > > > Currently a client join event changes discovery topology version which, in > turn, changes AffinityTopologyVersion. > When a client maps transaction on new AffinityTopologyVersion, corresponding > message is not processed on remote node until remote node receives the > corresponding discovery event. If discovery event delivery is delayed for > some reason, this will result in transaction stalls on client joins. > Since the client node does not change partition affinity, we can safely map > transactions on the previous topology version and do not change the affinity > topology version at all. > Some cases need special care and probably do not qualify for this > optimization, such as when client has near cache or client hosts partition > for REPLICATED cache. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10209) some tests in IgniteExamplesMLTestSuite fail with FileNotFoundException at SandboxMLCache#fillCacheWith(MLSandboxDatasets)
[
https://issues.apache.org/jira/browse/IGNITE-10209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16682810#comment-16682810
]
Ignite TC Bot commented on IGNITE-10209:
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2291160buildTypeId=IgniteTests24Java8_RunAll]
> some tests in IgniteExamplesMLTestSuite fail with FileNotFoundException at
> SandboxMLCache#fillCacheWith(MLSandboxDatasets)
> --
>
> Key: IGNITE-10209
> URL: https://issues.apache.org/jira/browse/IGNITE-10209
> Project: Ignite
> Issue Type: Bug
> Components: ml
>Affects Versions: 2.8
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.8
>
>
> Tests for examples that use
> {{SandboxMLCache#fillCacheWith(MLSandboxDatasets)}} fail with FNFE:
> {noformat}
> [ERROR] Tests run: 34, Failures: 0, Errors: 13, Skipped: 0, Time elapsed:
> 638.752 s <<< FAILURE! - in
> org.apache.ignite.testsuites.IgniteExamplesMLTestSuite
> [ERROR]
> testExample(org.apache.ignite.examples.ml.KMeansClusterizationExampleSelfName)
> Time elapsed: 21.701 s <<< ERROR!
> java.io.FileNotFoundException:
> examples\src\main\resources\datasets\two_classed_iris.csv (Системе не удается
> найти указанный путь)
> at
> org.apache.ignite.examples.ml.KMeansClusterizationExampleSelfName.testExample(KMeansClusterizationExampleSelfName.java)
> [ERROR]
> testExample(org.apache.ignite.examples.ml.KNNClassificationExampleSelfName)
> Time elapsed: 13.81 s <<< ERROR!
> java.io.FileNotFoundException: examples\src\main\resources\datasets\iris.txt
> (Системе не удается найти указанный путь)
> at
> org.apache.ignite.examples.ml.KNNClassificationExampleSelfName.testExample(KNNClassificationExampleSelfName.java)
> [ERROR]
> testExample(org.apache.ignite.examples.ml.KNNRegressionExampleSelfName) Time
> elapsed: 13.633 s <<< ERROR!
> java.io.FileNotFoundException:
> examples\src\main\resources\datasets\cleared_machines.csv (Системе не удается
> найти указанный путь)
> at
> org.apache.ignite.examples.ml.KNNRegressionExampleSelfName.testExample(KNNRegressionExampleSelfName.java)
> [ERROR]
> testExample(org.apache.ignite.examples.ml.LinearRegressionLSQRTrainerExampleSelfName)
> Time elapsed: 13.71 s <<< ERROR!
> java.io.FileNotFoundException:
> examples\src\main\resources\datasets\mortalitydata.csv (Системе не удается
> найти указанный путь)
> at
> org.apache.ignite.examples.ml.LinearRegressionLSQRTrainerExampleSelfName.testExample(LinearRegressionLSQRTrainerExampleSelfName.java)
> [ERROR]
> testExample(org.apache.ignite.examples.ml.LinearRegressionLSQRTrainerWithMinMaxScalerExampleSelfName)
> Time elapsed: 13.728 s <<< ERROR!
> java.io.FileNotFoundException:
> examples\src\main\resources\datasets\mortalitydata.csv (Системе не удается
> найти указанный путь)
> at
> org.apache.ignite.examples.ml.LinearRegressionLSQRTrainerWithMinMaxScalerExampleSelfName.testExample(LinearRegressionLSQRTrainerWithMinMaxScalerExampleSelfName.java)
> [ERROR]
> testExample(org.apache.ignite.examples.ml.LinearRegressionSGDTrainerExampleSelfName)
> Time elapsed: 13.874 s <<< ERROR!
> java.io.FileNotFoundException:
> examples\src\main\resources\datasets\mortalitydata.csv (Системе не удается
> найти указанный путь)
> at
> org.apache.ignite.examples.ml.LinearRegressionSGDTrainerExampleSelfName.testExample(LinearRegressionSGDTrainerExampleSelfName.java)
> [ERROR]
> testExample(org.apache.ignite.examples.ml.LogisticRegressionSGDTrainerExampleSelfName)
> Time elapsed: 13.694 s <<< ERROR!
> java.io.FileNotFoundException:
> examples\src\main\resources\datasets\two_classed_iris.csv (Системе не удается
> найти указанный путь)
> at
> org.apache.ignite.examples.ml.LogisticRegressionSGDTrainerExampleSelfName.testExample(LogisticRegressionSGDTrainerExampleSelfName.java)
> [ERROR]
> testExample(org.apache.ignite.examples.ml.LogRegressionMultiClassClassificationExampleSelfName)
> Time elapsed: 13.823 s <<< ERROR!
> java.io.FileNotFoundException:
> examples\src\main\resources\datasets\glass_identification.csv (Системе не
> удается найти указанный путь)
> at
> org.apache.ignite.examples.ml.LogRegressionMultiClassClassificationExampleSelfName.testExample(LogRegressionMultiClassClassificationExampleSelfName.java)
> [ERROR]
> testExample(org.apache.ignite.examples.ml.TrainTestDatasetSplitterExampleSelfName)
> Time elapsed: 12.875 s <<< ERROR!
> java.io.FileNotFoundException:
> examples\src\main\resources\datasets\mortalitydata.csv (Системе не удается
> найти указанный
