[MTCGA]: new failures in builds [2221154] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New stable failure of a flaky test in master IgniteWalFormatFileFailoverTest.testFailureHandlerTriggered https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-639422964459539=%3Cdefault%3E=testDetails Changes may lead to failure were done by - jokserfn http://ci.ignite.apache.org/viewModification.html?modId=837463=false - spiderru5597 http://ci.ignite.apache.org/viewModification.html?modId=837461=false - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 06:28:28 02-11-2018
Re: Ignite documentation process
Artem, Thanks for the update. Basically, it would be much better if you list the proposed changes here, so that everyone can share feedback without clicking the links ) -- Denis On Thu, Nov 1, 2018 at 7:36 AM Artem Budnikov wrote: > Hi Igniters, > > Please take a look at the changes in the "How to Contribute" procedure > [1] related to Ignite documentation. I just reflected there what we > discussed earlier about our documentation process. Please see this > thread for more information [2]. > > > [1]: > > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Documentingaticket > > [2]: > > apache-ignite-developers.2346864.n4.nabble.com/Re-Documenting-Ignite-tt32746.html > > > Cheers, > Artem > >
[jira] [Created] (IGNITE-10118) JDBC v2: metadata.getSchemas returns cache names instead of schema names
Pavel Kuznetsov created IGNITE-10118:
Summary: JDBC v2: metadata.getSchemas returns cache names instead
of schema names
Key: IGNITE-10118
URL: https://issues.apache.org/jira/browse/IGNITE-10118
Project: Ignite
Issue Type: Bug
Reporter: Pavel Kuznetsov
jdbc v2 returns list of cache names instead of list of schemas.
It is correct only if we have a cache and table created in it using cache API.
If we create tables using ddl we expect to see "PUBLIC" schema name in results
of {{connection.getMetadata().getSchemas()}} not "SQL_PUBLIC_TABLENAME"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] asfgit closed pull request #57: IGNITE-9849 Refactor Master trends
asfgit closed pull request #57: IGNITE-9849 Refactor Master trends
URL: https://github.com/apache/ignite-teamcity-bot/pull/57
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/db/DbMigrations.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/db/DbMigrations.java
index 824dc4a3..121f895e 100644
---
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/db/DbMigrations.java
+++
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/db/DbMigrations.java
@@ -66,6 +66,8 @@
private static final String BUILD_STATISTICS = "buildStatistics";
+private static final String BUILD_CONDITIONS_CACHE_NAME =
"buildConditions";
+
public static final String TESTS_COUNT_7700 = ",count:7700";
//V1 caches, 1024 parts
@@ -407,6 +409,7 @@ public void dataMigration(
applyDestroyIgnCacheMigration(TESTS);
applyDestroyIgnCacheMigration(STAT);
applyDestroyIgnCacheMigration(BUILD_STATISTICS);
+applyDestroyIgnCacheMigration(BUILD_CONDITIONS_CACHE_NAME);
applyDestroyCacheMigration(TEAMCITY_BUILD_CACHE_NAME_OLD,
TEAMCITY_BUILD_CACHE_NAME_OLD);
}
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/BuildRefCompacted.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/BuildRefCompacted.java
index a3aff88e..a0f6d369 100644
---
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/BuildRefCompacted.java
+++
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/BuildRefCompacted.java
@@ -140,7 +140,7 @@ public int branchName() {
}
/** */
-private int status() {
+public int status() {
return status;
}
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/BuildRefDao.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/BuildRefDao.java
index 0d7467a9..8a9a2643 100644
---
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/BuildRefDao.java
+++
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/BuildRefDao.java
@@ -34,6 +34,7 @@
import org.apache.ignite.ci.di.AutoProfiling;
import org.apache.ignite.ci.di.cache.GuavaCached;
import org.apache.ignite.ci.tcmodel.hist.BuildRef;
+import org.apache.ignite.ci.teamcity.ignited.fatbuild.FatBuildCompacted;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.internal.util.GridIntList;
import org.jetbrains.annotations.NotNull;
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/ITeamcityIgnited.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/ITeamcityIgnited.java
index cfdaa2eb..3e69094d 100644
---
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/ITeamcityIgnited.java
+++
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/ITeamcityIgnited.java
@@ -17,9 +17,10 @@
package org.apache.ignite.ci.teamcity.ignited;
import java.util.Collection;
+import java.util.Date;
import java.util.List;
import javax.annotation.Nullable;
-import org.apache.ignite.ci.tcbot.condition.BuildCondition;
+import org.apache.ignite.ci.teamcity.ignited.buildcondition.BuildCondition;
import org.apache.ignite.ci.tcmodel.hist.BuildRef;
import org.apache.ignite.ci.tcmodel.result.Build;
import org.apache.ignite.ci.teamcity.ignited.change.ChangeCompacted;
@@ -40,7 +41,7 @@
public String host();
/**
- * Retun all builds for branch and suite, without relation to its status.
+ * Return all builds for branch and suite, without relation to its status.
*
* @param buildTypeId Build type identifier.
* @param branchName Branch name.
@@ -50,7 +51,6 @@
@Nullable String buildTypeId,
@Nullable String branchName);
-
/**
* Retun all builds for branch and suite, without relation to its status.
*
@@ -62,6 +62,21 @@
@Nullable String buildTypeId,
@Nullable String branchName);
+/**
+ * Return all builds for branch and suite with finish status.
+ *
+ * @param buildTypeId Build type identifier.
+ * @param branchName Branch name.
+ * @param sinceDate Since date.
+ * @param untilDate Until date.
+ * @return list of builds in history in finish status.
+ */
+public List getFinishedBuildsCompacted(
+@Nullable String buildTypeId,
+@Nullable String branchName,
+@Nullable Date sinceDate,
+@Nullable Date untilDate);
+
/**
* Trigger build. Enforces TC Bot to load all builds related to this
[GitHub] ignite pull request #5067: IGNITE-9420 Logical recovery before PME
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5067 ---
[jira] [Created] (IGNITE-10117) Node is mistakenly excluded from history suppliers preventing historical rebalance.
Alexei Scherbakov created IGNITE-10117:
--
Summary: Node is mistakenly excluded from history suppliers
preventing historical rebalance.
Key: IGNITE-10117
URL: https://issues.apache.org/jira/browse/IGNITE-10117
Project: Ignite
Issue Type: Bug
Reporter: Alexei Scherbakov
Fix For: 2.8
This is because
org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager#reserveHistoryForExchange
is called before
org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager#beforeExchange,
which restores correct partition state.
{noformat}
public void testHistory() throws Exception {
IgniteEx crd = startGrid(0);
startGrid(1);
crd.cluster().active(true);
awaitPartitionMapExchange();
int part = 0;
List keys = loadDataToPartition(part, DEFAULT_CACHE_NAME, 100,
0, 1);
forceCheckpoint(); // Prevent IGNITE-10088
stopAllGrids();
awaitPartitionMapExchange();
List keys1 = loadDataToPartition(part, DEFAULT_CACHE_NAME,
100, 100, 1);
startGrid(0);
startGrid(1);
awaitPartitionMapExchange(); // grid0 will not provide history.
}
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #5199: ignite-10045 Strict bounds check
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5199 ---
Re: Abbreviation code-style requirement.
Ivan I removed "lic" from the list. Thanks for catch! Agree with Andrey. After several code reviews newcomers will get used to abbreviations. Andrey, try searching for "fut" and make sure to have "Word" checked. You will see plenty of usages. "f" is also ok for future in case it does not bring confusion and does not hurt readability. Let's keep using abbreviations and treat them as mandatory requirement. This is important for keeping our codebase consistent and tidy. --Yakov
Re: Abbreviation code-style requirement.
Ivan, I think it's harder to read others' code than write new code, so well known abbreviations may be helpful. As for writing, it's a matter of habit, and also abbeviation plugin is a good aid. I like current abbreviation list, except 'fut'. Never saw this before Ignite. 'f' or 'future' could look better to me. Also, futures often denote some asynchronous action, and it could be more expressive to use the name of the action as identifier instead of 'fut'. чт, 1 нояб. 2018 г. в 17:46, Павлухин Иван : > Hi Yakov and all, > > Recently I went through abbreviations list [1] to find items which are not > clear > for me. After the list was shortened by Yakov and others most of them have > gone. > But pay attention to "lic -> license". I cannot find usages of it in Ignite > codebase? > Could it be removed as well? > > And a little follow up. I worry how comfortable is contribution for an > external > contributor with presence of abbreviation rules. I always thought that long > names are common practice in Java world. And our abbreviations might > distract > a typical Java engineer. Does it make any sense? > > [1] > > https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules#AbbreviationRules-VariableAbbreviation > > чт, 1 нояб. 2018 г. в 17:33, Dmitriy Pavlov : > > > Hi Yakov, thank you for your efforts. > > > > I think no one is suggesting de-abbreviate, it would be no-sense work to > > do. I think the initial reason to start this discussion was the case when > > abbreviation seemed as hiding meaning, and multi-word. I'm glad we agree > > multiword complex variables may be non-abbreviated if it is meaningful. > > > > Vyacheslav D., > > > > could you please take a look and would you like to change abbrev plugin > > rules? > > > > Sincerely, > > Dmitriy Pavlov > > > > чт, 1 нояб. 2018 г. в 17:27, Yakov Zhdanov : > > > > > Igniters, > > > > > > I have shortened the list of abbreviation rules and edited our wiki > page > > - > > > https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules. > > > Thanks to Vladimir Ozerov and Alexey Goncharuk for their useful > feedback. > > > My idea was to leave only "common sense" abbreviations and those that > are > > > Ignite domain specific. > > > > > > I would also suggest that we treat names mentioned in the table on the > > page > > > as names that are required to be abbreviated. Please take this into > > account > > > when conducting code reviews. > > > > > > Thanks! > > > > > > --Yakov > > > > > > > > -- > Best regards, > Ivan Pavlukhin > -- Best regards, Andrey Kuznetsov.
Re: Abbreviation code-style requirement.
Hi Yakov and all, Recently I went through abbreviations list [1] to find items which are not clear for me. After the list was shortened by Yakov and others most of them have gone. But pay attention to "lic -> license". I cannot find usages of it in Ignite codebase? Could it be removed as well? And a little follow up. I worry how comfortable is contribution for an external contributor with presence of abbreviation rules. I always thought that long names are common practice in Java world. And our abbreviations might distract a typical Java engineer. Does it make any sense? [1] https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules#AbbreviationRules-VariableAbbreviation чт, 1 нояб. 2018 г. в 17:33, Dmitriy Pavlov : > Hi Yakov, thank you for your efforts. > > I think no one is suggesting de-abbreviate, it would be no-sense work to > do. I think the initial reason to start this discussion was the case when > abbreviation seemed as hiding meaning, and multi-word. I'm glad we agree > multiword complex variables may be non-abbreviated if it is meaningful. > > Vyacheslav D., > > could you please take a look and would you like to change abbrev plugin > rules? > > Sincerely, > Dmitriy Pavlov > > чт, 1 нояб. 2018 г. в 17:27, Yakov Zhdanov : > > > Igniters, > > > > I have shortened the list of abbreviation rules and edited our wiki page > - > > https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules. > > Thanks to Vladimir Ozerov and Alexey Goncharuk for their useful feedback. > > My idea was to leave only "common sense" abbreviations and those that are > > Ignite domain specific. > > > > I would also suggest that we treat names mentioned in the table on the > page > > as names that are required to be abbreviated. Please take this into > account > > when conducting code reviews. > > > > Thanks! > > > > --Yakov > > > -- Best regards, Ivan Pavlukhin
Re: Abbreviation code-style requirement.
Hi Dmitry, it's easy to update abbrev plugin rules. Once nobody has objections about updated abbreviations list I'll do it. On Thu, Nov 1, 2018 at 5:33 PM Dmitriy Pavlov wrote: > > Hi Yakov, thank you for your efforts. > > I think no one is suggesting de-abbreviate, it would be no-sense work to do. > I think the initial reason to start this discussion was the case when > abbreviation seemed as hiding meaning, and multi-word. I'm glad we agree > multiword complex variables may be non-abbreviated if it is meaningful. > > Vyacheslav D., > > could you please take a look and would you like to change abbrev plugin rules? > > Sincerely, > Dmitriy Pavlov > > чт, 1 нояб. 2018 г. в 17:27, Yakov Zhdanov : >> >> Igniters, >> >> I have shortened the list of abbreviation rules and edited our wiki page - >> https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules. >> Thanks to Vladimir Ozerov and Alexey Goncharuk for their useful feedback. >> My idea was to leave only "common sense" abbreviations and those that are >> Ignite domain specific. >> >> I would also suggest that we treat names mentioned in the table on the page >> as names that are required to be abbreviated. Please take this into account >> when conducting code reviews. >> >> Thanks! >> >> --Yakov -- Best Regards, Vyacheslav D.
Ignite documentation process
Hi Igniters, Please take a look at the changes in the "How to Contribute" procedure [1] related to Ignite documentation. I just reflected there what we discussed earlier about our documentation process. Please see this thread for more information [2]. [1]: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Documentingaticket [2]: apache-ignite-developers.2346864.n4.nabble.com/Re-Documenting-Ignite-tt32746.html Cheers, Artem
Re: Abbreviation code-style requirement.
Hi Yakov, thank you for your efforts. I think no one is suggesting de-abbreviate, it would be no-sense work to do. I think the initial reason to start this discussion was the case when abbreviation seemed as hiding meaning, and multi-word. I'm glad we agree multiword complex variables may be non-abbreviated if it is meaningful. Vyacheslav D., could you please take a look and would you like to change abbrev plugin rules? Sincerely, Dmitriy Pavlov чт, 1 нояб. 2018 г. в 17:27, Yakov Zhdanov : > Igniters, > > I have shortened the list of abbreviation rules and edited our wiki page - > https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules. > Thanks to Vladimir Ozerov and Alexey Goncharuk for their useful feedback. > My idea was to leave only "common sense" abbreviations and those that are > Ignite domain specific. > > I would also suggest that we treat names mentioned in the table on the page > as names that are required to be abbreviated. Please take this into account > when conducting code reviews. > > Thanks! > > --Yakov >
[GitHub] ignite pull request #5235: IGNITE-10115 Remove excessive "setAccessible(oldA...
GitHub user ibessonov opened a pull request: https://github.com/apache/ignite/pull/5235 IGNITE-10115 Remove excessive "setAccessible(oldAccessible)" in GridTestUtils You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10115 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5235.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 #5235 commit 47693921dcbd81709d68289eb6133bf17048928b Author: ibessonov Date: 2018-11-01T14:29:14Z IGNITE-10115 Removed excessive "setAccessible" invocations. ---
Re: Abbreviation code-style requirement.
Igniters, I have shortened the list of abbreviation rules and edited our wiki page - https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules. Thanks to Vladimir Ozerov and Alexey Goncharuk for their useful feedback. My idea was to leave only "common sense" abbreviations and those that are Ignite domain specific. I would also suggest that we treat names mentioned in the table on the page as names that are required to be abbreviated. Please take this into account when conducting code reviews. Thanks! --Yakov
[GitHub] ignite pull request #5234: IGNITE-10107 Cache 7 tests optimization
GitHub user ibessonov opened a pull request: https://github.com/apache/ignite/pull/5234 IGNITE-10107 Cache 7 tests optimization You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10107 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5234.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 #5234 commit 4e85c11c3a5781b88cf2e3ae2a70b033f66e6e5d Author: Alexey Platonov Date: 2018-10-29T13:59:05Z init commit commit 45076feec0dc4a26172eb79acb9dabcd1a8bab73 Author: Alexey Platonov Date: 2018-10-30T09:37:14Z add scale factor commit 907b19320d1bffbfbb9b3997201fd4b28718b2ee Author: Alexey Platonov Date: 2018-10-30T09:41:21Z remode useless code commit 8107297ea092d46c097b4575213deb593d7a0db4 Author: Alexey Platonov Date: 2018-10-30T10:08:55Z remove garbage commit 3ff73df5a016dcd6ea03d23ee4a2c8f0b37b0c2a Author: Alexey Platonov Date: 2018-10-30T10:18:56Z fix comments in code commit 0c0a043feaa1d4bcbf61bcc2137490cea41c7679 Author: ibessonov Date: 2018-11-01T14:09:55Z IGNITE-10107 Mainly "scale-factor" optimizations. Password hashing algorithm tweaked so authentication tests are much faster now in general. ---
Re: Contribution
Hi Pavel, Welcome to the Apache Software Foundation and to the Apache Ignite Community. I've added your account to the list of contributors. Now you should be able to assign an issue to yourself. Should you have any questions please do not hesitate to ask here. Looking forward to your contributions. Sincerely, Dmitriy Pavlov P.S. Additional references that should boost your onboarding. Please subscribe to both dev and user lists: https://ignite.apache.org/community/resources.html#mail-lists Instructions on how to contribute can be found here: https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Project setup in Intellij IDEA: https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup чт, 1 нояб. 2018 г. в 12:28, Paul NewMan : > Hello guys, > > My name is Pavel and I want to participate in the Ignite development > process. Could you please give me corresponding permissions to start on it? > My jira acc: inspaulation > > Best, > Pavel Istomin >
[jira] [Created] (IGNITE-10116) Document implemented design of Service Grid (redesign phase 1)
Vyacheslav Daradur created IGNITE-10116: --- Summary: Document implemented design of Service Grid (redesign phase 1) Key: IGNITE-10116 URL: https://issues.apache.org/jira/browse/IGNITE-10116 Project: Ignite Issue Type: Task Components: managed services Reporter: Vyacheslav Daradur Assignee: Vyacheslav Daradur Fix For: 2.8 It's necessary to document implemented design of Service Grid and publish in wiki. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10115) Remove excessive "setAccessible(oldAccessible)" in GridTestUtils
Ivan Bessonov created IGNITE-10115: -- Summary: Remove excessive "setAccessible(oldAccessible)" in GridTestUtils Key: IGNITE-10115 URL: https://issues.apache.org/jira/browse/IGNITE-10115 Project: Ignite Issue Type: Improvement Reporter: Ivan Bessonov Assignee: Ivan Bessonov Fix For: 2.8 Methods like org.apache.ignite.testframework.GridTestUtils#setFieldValue(java.lang.Object, java.lang.String, java.lang.Object) return old state of Field objects but that doesn't make any sense. Removing such actions will make code more clear and effective. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10114) Potential deadlock in GridDhtPartitionTopologyImpl
Roman Kondakov created IGNITE-10114:
---
Summary: Potential deadlock in GridDhtPartitionTopologyImpl
Key: IGNITE-10114
URL: https://issues.apache.org/jira/browse/IGNITE-10114
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Roman Kondakov
There are several methods in {{GridDhtPartitionTopologyImpl}} where correct
checkpoint and topology readlock order is violated: topology lock is obtained
first, and after this an initialization of {{CacheDataStore}} could be called
under the checkpoint lock.
Affected methods:
* {{GridDhtPartitionTopologyImpl#localUpdateCounters}}
* {{GridDhtPartitionTopologyImpl#partitionSizes}}
* {{GridDhtPartitionTopologyImpl#printMemoryStats}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10113) Failure during build index isn't handled by failure handler
Sergey Antonov created IGNITE-10113: --- Summary: Failure during build index isn't handled by failure handler Key: IGNITE-10113 URL: https://issues.apache.org/jira/browse/IGNITE-10113 Project: Ignite Issue Type: Bug Reporter: Sergey Antonov Assignee: Sergey Antonov Fix For: 2.8 Attachments: StopNodeOnRebuildIndexFailureTest.java If exception will be thrown during index build, failure handler doesn't handle this exception. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10112) Prioritize processing of tx finish=false message due to timeout
Alexei Scherbakov created IGNITE-10112: -- Summary: Prioritize processing of tx finish=false message due to timeout Key: IGNITE-10112 URL: https://issues.apache.org/jira/browse/IGNITE-10112 Project: Ignite Issue Type: Improvement Reporter: Alexei Scherbakov Fix For: 2.8 Currently tx rollback messages are processed in the same way as others. For forced rollback on example triggered by tx timeouts on PME (see org.apache.ignite.configuration.TransactionConfiguration#getTxTimeoutOnPartitionMapExchange) they should be prioritized to avoid timeout violation under load. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10111) Affinity doesn't recalculate after lost partitions
Anton Kalashnikov created IGNITE-10111: -- Summary: Affinity doesn't recalculate after lost partitions Key: IGNITE-10111 URL: https://issues.apache.org/jira/browse/IGNITE-10111 Project: Ignite Issue Type: Bug Reporter: Anton Kalashnikov Attachments: AffinityLostPartitionTest.java Case: 1)Start 3 data nodes and activate the cluster with cache with 1 backup and PartitionLossPolicy.READ_ONLY_SAFE. 2)Start client and add the data to your cache. Stop the client 3)Stop DN2 and clear it pds and val 4)Start DN2. Rebalance will start. 5)During rebalance stop DN3. At this moment some partitions from DN2 marked as LOST. 6)Start DN3. In fact all data was come back but affinity instead of DN3 use DN2 which have partitions(lost) with loss some data. Reproducer is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #5233: IGNITE-10092 Race in partition state when checkpo...
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/5233 IGNITE-10092 Race in partition state when checkpoint started at the m⦠â¦iddle of starts caches You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10092 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5233.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 #5233 commit e0ee0c765b9e51fbb412582eaa91e92dbd2f3342 Author: vd-pyatkov Date: 2018-11-01T11:19:01Z IGNITE-10092 Race in partition state when checkpoint started at the middle of starts caches ---
[GitHub] ignite pull request #5232: IGNITE-9420 Logical recovery (squash just for rev...
GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/5232 IGNITE-9420 Logical recovery (squash just for review) You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9420-squash-2 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5232.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 #5232 commit bfe7cd8a9d83092140b642505b880a8c7b369e2e Author: Pavel Kovalenko Date: 2018-11-01T10:10:40Z IGNITE-9420 Logical recovery (squash just for review) ---
[GitHub] ignite pull request #5016: IGNITE-9420 Logical recovery before PME
Github user Jokser closed the pull request at: https://github.com/apache/ignite/pull/5016 ---
[GitHub] ignite pull request #5212: IGNITE-9420 Logical recovery before PME
Github user Jokser closed the pull request at: https://github.com/apache/ignite/pull/5212 ---
[jira] [Created] (IGNITE-10110) SQL query with DISTINCT and JOIN in suquery produces "Column not found"
Pavel Vinokurov created IGNITE-10110: Summary: SQL query with DISTINCT and JOIN in suquery produces "Column not found" Key: IGNITE-10110 URL: https://issues.apache.org/jira/browse/IGNITE-10110 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.4 Reporter: Pavel Vinokurov Initial script: CREATE TABLE Person( person_id INTEGER PRIMARY KEY, company_id INTEGER, last_name VARCHAR(100) ); CREATE TABLE Company( company_id INTEGER PRIMARY KEY, location_id INTEGER ); CREATE TABLE Department( department_id INTEGER PRIMARY KEY, person_id INTEGER ); CREATE TABLE Organization( organization_id INTEGER PRIMARY KEY, company_id INTEGER ); Query: SELECT last_name FROM ( SELECT last_name, person_id, company_id FROM ( SELECT last_name, person_id, p.company_id as company_id FROM Person p INNER JOIN ( SELECT DISTINCT location_id, company_id FROM Company WHERE location_id = 1 ) cpy ON ( p.company_id = cpy.company_id ) ) a ) src INNER JOIN department dep ON src.person_id = dep.person_id LEFT JOIN organization og ON src.company_id = og.company_id Result: Caused by: org.h2.jdbc.JdbcSQLException: Column "SRC__Z4.COMPANY_ID" not found; SQL statement: SELECT DEP__Z5.PERSON_ID __C2_0 FROM PUBLIC.DEPARTMENT DEP__Z5 LEFT OUTER JOIN PUBLIC.ORGANIZATION OG__Z6 ON SRC__Z4.COMPANY_ID = OG__Z6.COMPANY_ID -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #5221: IGNITE-7926 Fixed incorrect classpath.
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5221 ---
Contribution
Hello guys, My name is Pavel and I want to participate in the Ignite development process. Could you please give me corresponding permissions to start on it? My jira acc: inspaulation Best, Pavel Istomin
[jira] [Created] (IGNITE-10109) MVCC TX: data become inconsistent after several updates
Igor Seliverstov created IGNITE-10109: - Summary: MVCC TX: data become inconsistent after several updates Key: IGNITE-10109 URL: https://issues.apache.org/jira/browse/IGNITE-10109 Project: Ignite Issue Type: Bug Components: mvcc Reporter: Igor Seliverstov Assignee: Igor Seliverstov Fix For: 2.7 see [TC test history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=4365543959682167276=testDetails] Here we do concurrent updates on several accounts (update their balances incrementing one and decrementing another), we expect consistent sum of all accounts at any time. The sum become inconsistent after while. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #5075: IGNITE-9988
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5075 ---
[jira] [Created] (IGNITE-10108) Non-static class is passed between cluster nodes
Vladislav Pyatkov created IGNITE-10108:
--
Summary: Non-static class is passed between cluster nodes
Key: IGNITE-10108
URL: https://issues.apache.org/jira/browse/IGNITE-10108
Project: Ignite
Issue Type: Bug
Reporter: Vladislav Pyatkov
Need to avoid passing anonymous classes on compute, because this lead to
serialize whole test-class context.
By the reason need to refactor that place
{code}
ignite.compute().withTimeout(5_000).broadcastAsync(new IgniteRunnable() {
...
});
{code}
in method \{{GridCommonAbstractTest#manualCacheRebalancing}} into private
static nested class.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10107) Cache 7 tests optimization
Ivan Bessonov created IGNITE-10107: -- Summary: Cache 7 tests optimization Key: IGNITE-10107 URL: https://issues.apache.org/jira/browse/IGNITE-10107 Project: Ignite Issue Type: Improvement Reporter: Ivan Bessonov Assignee: Ivan Bessonov Fix For: 2.8 These tests run over 1 minute each: Authentication1kUsersNodeRestartTest.test1kUsersNodeRestartServer TxRollbackAsyncWithPersistenceTest.testSynchronousRollback IgniteCacheStartWithLoadTest.testNoRebalanceDuringCacheStart WalModeChangeAdvancedSelfTest.testConcurrentOperations TxRollbackAsyncWithPersistenceTest.testMixedAsyncRollbackTypes GridCacheRebalancingWithAsyncClearingTest.testPartitionClearingNotBlockExchange WalModeChangeAdvancedSelfTest.testServerRestartNonCoordinator They should be either optimized or moved into overnight build (or both). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10106) Cache 5 test suite optimization
Alexey Platonov created IGNITE-10106: Summary: Cache 5 test suite optimization Key: IGNITE-10106 URL: https://issues.apache.org/jira/browse/IGNITE-10106 Project: Ignite Issue Type: Improvement Reporter: Alexey Platonov Assignee: Alexey Platonov We need to investigate how to optimize these tests: |CacheSerializableTransactionsTest.testGetRemoveTxNearCache2| |[CacheSerializableTransactionsTest.testGetRemoveTxNearCache1|https://ci.ignite.apache.org/viewLog.html?currentGroup=test=org.apache.ignite.testsuites.IgniteCacheTestSuite5%23teamcity%23org.apache.ignite.internal.processors.cache%23teamcity%23CacheSerializableTransactionsTest=1=DURATION_DESC=20===IgniteTests24Java8_Cache5=2160072=testsInfo]| |CacheSerializableTransactionsTest.testRandomOperations| |[CacheSerializableTransactionsTest.testIncrementTxRestart|https://ci.ignite.apache.org/viewLog.html?currentGroup=test=org.apache.ignite.testsuites.IgniteCacheTestSuite5%23teamcity%23org.apache.ignite.internal.processors.cache%23teamcity%23CacheSerializableTransactionsTest=1=DURATION_DESC=20===IgniteTests24Java8_Cache5=2160072=testsInfo]| |CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockNodeRestart| |[CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockFromClientsNodeRestart|https://ci.ignite.apache.org/viewLog.html?currentGroup=test=org.apache.ignite.testsuites.IgniteCacheTestSuite5%23teamcity%23org.apache.ignite.internal.processors.cache%23teamcity%23CacheSerializableTransactionsTest=1=DURATION_DESC=20===IgniteTests24Java8_Cache5=2160072=testsInfo]| |[CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockWithNonSerializable|https://ci.ignite.apache.org/viewLog.html?currentGroup=test=org.apache.ignite.testsuites.IgniteCacheTestSuite5%23teamcity%23org.apache.ignite.internal.processors.cache%23teamcity%23CacheSerializableTransactionsTest=1=DURATION_DESC=20===IgniteTests24Java8_Cache5=2160072=testsInfo]| |[CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockGetPut|https://ci.ignite.apache.org/viewLog.html?currentGroup=test=org.apache.ignite.testsuites.IgniteCacheTestSuite5%23teamcity%23org.apache.ignite.internal.processors.cache%23teamcity%23CacheSerializableTransactionsTest=1=DURATION_DESC=20===IgniteTests24Java8_Cache5=2160072=testsInfo]| |[CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockFromClients|https://ci.ignite.apache.org/viewLog.html?currentGroup=test=org.apache.ignite.testsuites.IgniteCacheTestSuite5%23teamcity%23org.apache.ignite.internal.processors.cache%23teamcity%23CacheSerializableTransactionsTest=1=DURATION_DESC=20===IgniteTests24Java8_Cache5=2160072=testsInfo]| |[CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlock|https://ci.ignite.apache.org/viewLog.html?currentGroup=test=org.apache.ignite.testsuites.IgniteCacheTestSuite5%23teamcity%23org.apache.ignite.internal.processors.cache%23teamcity%23CacheSerializableTransactionsTest=1=DURATION_DESC=20===IgniteTests24Java8_Cache5=2160072=testsInfo]| and optimize them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #5082: IGNITE-9986 TcpDiscoverySelfTest.testNodeShutdown...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5082 ---
[jira] [Created] (IGNITE-10105) AI 2.7: Prepare release notes
Vladimir Ozerov created IGNITE-10105: Summary: AI 2.7: Prepare release notes Key: IGNITE-10105 URL: https://issues.apache.org/jira/browse/IGNITE-10105 Project: Ignite Issue Type: Task Components: general Reporter: Vladimir Ozerov Fix For: 2.7 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10104) MVCC TX: client SFU doesn't work on replicated caches
Igor Seliverstov created IGNITE-10104:
-
Summary: MVCC TX: client SFU doesn't work on replicated caches
Key: IGNITE-10104
URL: https://issues.apache.org/jira/browse/IGNITE-10104
Project: Ignite
Issue Type: Bug
Components: mvcc, sql
Reporter: Igor Seliverstov
Fix For: 2.8
When select for update executes from client node the execution is sent to
random owning node. On that node dht enlist operation is started what causes an
assertion error because dht enlist operation implies that the node is primary
for all processed keys.
see {{CacheMvccReplicatedBackupsTest.testBackupsCoherenceWithLargeOperations}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] ignite pull request #5230: IGNITE-10103: Fix IgnitePersistentStoreDataStruct...
GitHub user pavlukhin opened a pull request: https://github.com/apache/ignite/pull/5230 IGNITE-10103: Fix IgnitePersistentStoreDataStructuresTest.testSequenceAfterAutoactivation You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-10103 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5230.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 #5230 commit 1caaeb65878f13cfb1fdd56e26d8a11cdda83652 Author: ipavlukhin Date: 2018-10-31T12:21:20Z access atomicSequence on auto-activating cluster with retries commit 2a2e9e38701f01761f34d0149de780dc9ea0163b Author: ipavlukhin Date: 2018-11-01T08:34:34Z check exception message in test ---
[GitHub] ignite pull request #5231: IGNITE-9720 Lazy free lists
GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/5231 IGNITE-9720 Lazy free lists You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9720 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5231.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 #5231 commit 057f4fdc7ede35779e98b09a7e9c7a7844f3d70e Author: sboikov Date: 2018-10-19T12:39:22Z ignite-9720 commit c6b0905111563473bcd4aabf53a1e620f62af190 Author: sboikov Date: 2018-10-22T10:33:01Z ignite-9720 commit 28a76b3bb60759f5d812e5333c1ab429b88b88e3 Author: sboikov Date: 2018-10-22T10:40:33Z ignite-9720 commit a6cd973a2b80d3bb1b6ead420b4d9d7d2afc9084 Author: sboikov Date: 2018-10-22T15:15:20Z Merge remote-tracking branch 'remotes/origin/master' into ignite-9720 commit 144ca212edf6dfcbd93feca5bc4c1244fb4edc5e Author: sboikov Date: 2018-10-23T07:56:08Z ignite-9720 commit 9c330467687078438b3cd89527c9a4e0cb55af4b Author: sboikov Date: 2018-10-23T09:32:26Z Attempt to make ttl tests more robust. commit 23d4f72176febac0be9c97ed020d00ffa81461e6 Author: sboikov Date: 2018-10-23T12:27:29Z ignite-9720 commit d98bfd955d3188c1685be42e842e806347ab0bb7 Author: sboikov Date: 2018-10-23T12:27:56Z Merge remote-tracking branch 'remotes/origin/master' into ignite-9720 commit 2a52875facdb5e8e20b65f0e4a742be394145099 Author: sboikov Date: 2018-10-24T06:05:30Z Merge remote-tracking branch 'remotes/origin/master' into ignite-9720 commit 8464bd1976641bd35ac0de20d01e270d47726012 Author: sboikov Date: 2018-10-24T06:17:54Z ignite-9720 commit 36d3169fa2b6aec10e8fb19e15741c9b7675bdb5 Author: Alexey Goncharuk Date: 2018-11-01T08:31:40Z Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite into ignite-9720 Conflicts: modules/core/src/test/java/org/apache/ignite/testsuites/IgnitePdsTestSuite4.java ---
[GitHub] ignite pull request #5222: IGNITE-8987: Fix testSequenceAfterAutoactivation
Github user pavlukhin closed the pull request at: https://github.com/apache/ignite/pull/5222 ---
[GitHub] ignite pull request #5229: IGNITE-9730 Lazy free lists
Github user agoncharuk closed the pull request at: https://github.com/apache/ignite/pull/5229 ---
[GitHub] ignite pull request #5229: IGNITE-9730 Lazy free lists
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/5229
IGNITE-9730 Lazy free lists
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9720
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5229.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 #5229
commit 5e989bddbef04f4d70d7ab361634f7000fe21ec0
Author: Andrei Aleksandrov
Date: 2018-10-24T09:01:00Z
IGNITE-9914 Use correct subject ID for TaskEvents for remote clients -
Fixes #5030.
Signed-off-by: Alexey Goncharuk
commit 0d7535340b61df0c327fd6afe9d3519a248ee350
Author: Denis Mekhanikov
Date: 2018-10-24T09:24:46Z
IGNITE-9899 Notify CQ filter on backups - Fixes #5011.
Signed-off-by: Alexey Goncharuk
commit ff29b679174b19c6372ec3f84bde937c45fa0a3a
Author: Andrei Aleksandrov
Date: 2018-10-24T09:39:19Z
IGNITE-9881 Added events for management tasks - Fixes #5006.
Signed-off-by: Alexey Goncharuk
commit 92306fde44ee8eed7ad92dea0237db92cbbb4723
Author: Maxim Muzafarov
Date: 2018-10-24T11:17:14Z
IGNITE-9923: fix unused imports - Fixes #5023.
Signed-off-by: Nikolay Izhikov
commit e8d7cf9726e11554ebfdf5f8144e5bcaab7e221f
Author: Dmitrii Ryabov
Date: 2018-10-24T15:41:23Z
IGNITE-9961 GridMessageListenSelfTest#testNullTopic() duplicates
#testNonNullTopic() - Fixes #5048.
Signed-off-by: Alexey Goncharuk
commit e7a93fcc1383003596370aa65efdce053f0f2b48
Author: Alexey Kuznetsov
Date: 2018-10-25T03:37:36Z
IGNITE-9938 Updated ScalaTest version and introduced
"${scala.test.version}" variable.
commit a61e4a394af649a146a3f43489181db6fd991967
Author: Sergey Antonov
Date: 2018-10-25T04:23:58Z
IGNITE-9853 control.sh: Added output of cache configurations. Fixes #4956.
commit a18f71ce5c89465e7b32fca71755208ac8976128
Author: Sergey Antonov
Date: 2018-10-25T11:10:13Z
IGNITE-9853 control.sh: Added output of cache configurations. Fixes #4956.
commit 67d4941f349e2a4af9ae5d04bc12d5f56b94a952
Author: Pavel Kuznetsov
Date: 2018-10-25T11:40:49Z
IGNITE-9637: Yardstick: upload benchmarks. This closes #4796.
commit 0a92c25e66b363db26c6b5681188cdf6384bb66a
Author: Pavel Kuznetsov
Date: 2018-10-25T11:49:23Z
IGNITE-9447: Yardstick: fixed logic which waits for necessary number of
server nodes to be available which otherwise led to benchmark hangs. This
closes #4879.
commit 18c02b5fee82a88608df8aeb4ad3ca9886a2657d
Author: Pavel Kuznetsov
Date: 2018-10-25T11:58:38Z
IGNITE-6881: JDBC Thin Driver: Do not throw an exception in case of attempt
to execute empty batch. This closes #5051.
commit 610b96ddd1352ad645306b2bfae50107e8ee8ab1
Author: Pavel Kuznetsov
Date: 2018-10-25T12:31:57Z
IGNITE-9655: Yardstick: cleanup in DML benchmarks. This closes #4821.
commit b94efd5114467075dcff057a2c896491976c617b
Author: Aleksey Plekhanov
Date: 2018-10-25T13:50:56Z
IGNITE-9780: SQL: Add IGNITE.CACHE_GROUPS view. This closes #4985.
commit 1f3648b75d36bd8a601b1860c98a1a917b442620
Author: Ilya Kasnacheev
Date: 2018-10-26T08:31:51Z
IGNITE-9454: Fixed SecurityPermissionSetBuilder. This closes #5066.
commit 797e7af77247f2e350d539d082ed25cd0f939a98
Author: Maxim Muzafarov
Date: 2018-10-26T08:47:30Z
IGNITE-9983: Add an inspection configuration for TC suite with enabled
short list of rules - Fixes #5059.
Signed-off-by: Nikolay Izhikov
commit 51d8c9f72a0553397d4f471f81f926e498f21114
Author: Alexander Kalinin
Date: 2018-10-26T09:42:39Z
IGNITE-10016 Web Console: ClusterLoginService should return "Credentials"
modal as singleton.
commit 28e3dec5b4c9bffcca5391cac8bee824973fc7a4
Author: Aleksei Scherbakov
Date: 2018-10-26T10:00:22Z
IGNITE-8873 Added methods to preload partitions to page memory - Fixes
#5053.
Signed-off-by: Alexey Goncharuk
commit c7449f6c6a318debce84883aba69e6c028af5e48
Author: Maxim Muzafarov
Date: 2018-10-26T12:16:40Z
IGNITE-7196 Restore binary state before node join to topology - Fixes #4520.
Signed-off-by: Dmitriy Govorukhin
commit 370cd3e1d60237e4a238c1c789cddbd1164e57e6
Author: zaleslaw
Date: 2018-10-26T13:06:42Z
IGNITE-9910: [ML] Move the static copy-pasted datasets from examples
to special Util class
this closes #5028
commit 11e142da3730b7f61b1b66749c4a2d77631fdaf1
Author: YuriBabak
Date: 2018-10-26T15:26:18Z
IGNITE-10026: [ML] Broken example: GaussianNaiveBayesTrainerExample
this closes #5090
commit ad99fbae735307e56ea6c78dcbd88fa1454ecee2
Author: Aleksei Scherbakov
Date: 2018-10-27T08:45:32Z
IGNITE-8873 Fixed tests - Fixes #5091.
Signed-off-by: Alexey Goncharuk
commit e111d895e7f7f32d6f764683ba8412d61d370455
[jira] [Created] (IGNITE-10103) Fix IgnitePersistentStoreDataStructuresTest.testSequenceAfterAutoactivation
Ivan Pavlukhin created IGNITE-10103: --- Summary: Fix IgnitePersistentStoreDataStructuresTest.testSequenceAfterAutoactivation Key: IGNITE-10103 URL: https://issues.apache.org/jira/browse/IGNITE-10103 Project: Ignite Issue Type: Bug Components: cache Reporter: Ivan Pavlukhin Assignee: Ivan Pavlukhin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #5224: IGNITE-10064 Fixed examples pom files
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5224 ---
[jira] [Created] (IGNITE-10102) Import from database dialog does not show list of tables
Vasiliy Sisko created IGNITE-10102: -- Summary: Import from database dialog does not show list of tables Key: IGNITE-10102 URL: https://issues.apache.org/jira/browse/IGNITE-10102 Project: Ignite Issue Type: Bug Reporter: Vasiliy Sisko Does not work in common and demo mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] ignite pull request #4827: IGNITE-9418 initialize cache persistent storage c...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/4827 ---
[jira] [Created] (IGNITE-10101) Filed to get cache list on Query page.
Vasiliy Sisko created IGNITE-10101: -- Summary: 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: Alexander Kalinin 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)
