[jira] [Created] (IGNITE-12921) System view design leads to bad user expirience.

Andrey N. Gura created IGNITE-12921: --- Summary: System view design leads to bad user expirience. Key: IGNITE-12921 URL: https://issues.apache.org/jira/browse/IGNITE-12921 Project: Ignite

[GitHub] [ignite-website] dmagda commented on a change in pull request #6: SEO changes to several urls and some contents on Data Grid page

dmagda commented on a change in pull request #6: URL: https://github.com/apache/ignite-website/pull/6#discussion_r411562399 ## File path: use-cases/in-memory-data-grid.html ## @@ -58,60 +57,60 @@ In-Memory Data Grid with Apache Ignite -Apache

Re: IGNITE-12702 - Discussion

Hello Igniters, I have created pull request for IGNITE-12702. Can someone review this? https://github.com/apache/ignite/pull/7663 regards, Kartik On Mon, Mar 23, 2020 at 11:28 PM Denis Magda wrote: > Hi Kartik, > > Actually, it means quite the opposite. You should fill in the release notes >

[MTCGA]: new failures in builds [5240319] 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

Re: [DISCUSSION] Pull-request checks on GitHub

Pavel, 1. Agree here. What if we create a default template pull request description with all the links required by our development process? [1] It's will be friendly for contributors to have everything they need in the PR. 2. [1]

Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]

Hello, Igniters. I perform cherry-pick for most commits targeted for 2.8.1 release. TC bot results - https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull%2F7690%2Fhead=Latest=pull%2F7102%2Fhead I need help with cherry picking the following commits: - 4e6cd2ce04

Re: [DISCUSSION] Pull-request checks on GitHub

Maxim, pull request template is a great idea. We can put a checklist there along with the links to the guidelines, something like this: [ ] Coding Guidelines are followed [ ] TeamCity build passes [ ] JIRA ticked is in Patch Available state, review has been requested in comments [ ] Something

Re: No commits to Ignite website: migration from SVN to Git is in progress

Saikat, now I see your point, thanks for breaking it down. As of now, there is no need for those scripts, at least, for the website repository. It's easy to review and merge changes using GitHub built-in capabilities and controls with all the changes propagated to ASF's repos. - Denis On Sun,

[jira] [Created] (IGNITE-12922) SqlViewMetricExporterSpi is redundant entity

Andrey N. Gura created IGNITE-12922: --- Summary: SqlViewMetricExporterSpi is redundant entity Key: IGNITE-12922 URL: https://issues.apache.org/jira/browse/IGNITE-12922 Project: Ignite Issue

Re: [DISCUSSION] Pull-request checks on GitHub

Maxim, Good news, thank you. However, I see two issues with this: 1. False sense of a ready-to-merge PR Now that we have a reassuring green checkmark on the PR, contributors might think that build passes and all is well. But this is not true - we only check that the code compiles. TeamCity run

Re: [DISCUSSION] Pull-request checks on GitHub

Pavel, Sorry for the incomplete message. 2. I mentioned it too. Hopefully, builds > 4 hrs would not be too often. The reason - there are limited job-workers shared between all the Apache projects. I found some details here [1] [2]. [1]

[jira] [Created] (IGNITE-12923) web-* docker images on Docker Hub are out of date

Zaar Hai created IGNITE-12923: - Summary: web-* docker images on Docker Hub are out of date Key: IGNITE-12923 URL: https://issues.apache.org/jira/browse/IGNITE-12923 Project: Ignite Issue Type:

Re: [DISCUSSION] Hot cache backup

Maxim, I've reviewed your PR and it looks good to me. Good job! пт, 10 апр. 2020 г. в 19:43, Alexey Goncharuk : > Maxim, > > Thanks for raising this PR. I will do a review during next week. > > --AG >

[DISCUSSION] Separate code sanity check and build task

Igniters, Currently we have code sanity checks [1][2] integrated within a build task [3]. Do we really need to fail the build (and therefore the other tasks) if there is a minor flaw like a missing line at the end of a file or an unused import? As for me it could be separated from the build

[jira] [Created] (IGNITE-12917) SQL: print warning log message when query's result is big

Taras Ledkov created IGNITE-12917: - Summary: SQL: print warning log message when query's result is big Key: IGNITE-12917 URL: https://issues.apache.org/jira/browse/IGNITE-12917 Project: Ignite

Re: [DISCUSSION] Hot cache backup

Alex P, Thank you for the great sophisticated review. Alexey G, Will you take a look at my changes[1]? The fresh TC.Bot visa attached. [1] https://issues.apache.org/jira/browse/IGNITE-11073 On Mon, 20 Apr 2020 at 11:54, Alex Plehanov wrote: > > Maxim, I've reviewed your PR and it looks good

[jira] [Created] (IGNITE-12919) Not all GridUuid renamed to IgniteUuid

Amelchev Nikita created IGNITE-12919: Summary: Not all GridUuid renamed to IgniteUuid Key: IGNITE-12919 URL: https://issues.apache.org/jira/browse/IGNITE-12919 Project: Ignite Issue

Re: [DISCUSSION] Pull-request checks on GitHub

Igniters, The Travis-ci build configured for running on the Apache Ignite PRs and the master branch [1] [2]. Build run under: openjdk8 openjdk11 Example of PR: https://github.com/apache/ignite/pull/7695 [1] https://travis-ci.org/github/apache/ignite [2]

[jira] [Created] (IGNITE-12918) .NET: Add dotnet build to travis-ci

Pavel Tupitsyn created IGNITE-12918: --- Summary: .NET: Add dotnet build to travis-ci Key: IGNITE-12918 URL: https://issues.apache.org/jira/browse/IGNITE-12918 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-12920) Static hierarchy in jmx tree

Igor Akkuratov created IGNITE-12920: --- Summary: Static hierarchy in jmx tree Key: IGNITE-12920 URL: https://issues.apache.org/jira/browse/IGNITE-12920 Project: Ignite Issue Type: