Nikita Safonov created IGNITE-14271:
---
Summary: Update Metrics page descriptions
Key: IGNITE-14271
URL: https://issues.apache.org/jira/browse/IGNITE-14271
Project: Ignite
Issue Type: Improve
Alexey Goncharuk created IGNITE-14272:
-
Summary: Merge modules/DEVNOTES.txt and DEVNOTES.txt
Key: IGNITE-14272
URL: https://issues.apache.org/jira/browse/IGNITE-14272
Project: Ignite
Issu
Thanks for joining us yesterday and for the inspiring Q&A session. Here are
the materials:
Alliedium app: https://alliedium.alliedtesting.com/
Slides with all the links: t.ly/9BOf
Video: https://youtu.be/BvpF68NWOao
An article about this case:
https://medium.com/alliedium/boosting-jira-cloud-ap
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New Critical Failure in master [Build]
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_BuildApacheIgnite?branch=%3Cdefault%3E
No changes in the build
- H
Maxim Muzafarov created IGNITE-14273:
Summary: ignite-extensions: Export data from snapshot to custom
format
Key: IGNITE-14273
URL: https://issues.apache.org/jira/browse/IGNITE-14273
Project: Igni
Hi Petr! My proposal is:
1. Create a parameter in [Build] TC suite - MAVEN_CHECKS, default value is
"-Plicenses,checkstyle,check-licenses,check-test-suites".
2. Use it in a command along with MAVEN_MODULES_STRING.
-U -Pall-java,all-scala,scala,lgpl,examples %MAVEN_CHECKS%
%MAVEN_MODULES_STRING%
3
Hi,
Please help review this PR:
https://github.com/apache/ignite/pull/8845
Regards,
Atri
Hi,
Please help in reviewing:
https://github.com/apache/ignite/pull/8820
Atri
Taras Ledkov created IGNITE-14274:
-
Summary: Calcite integration: refactoring aggregates converter
rules: single and map/reduce
Key: IGNITE-14274
URL: https://issues.apache.org/jira/browse/IGNITE-14274
Yury Gerzhedovich created IGNITE-14275:
--
Summary: SQL. Calcite: MapReduce aggregates for hash distribution
Key: IGNITE-14275
URL: https://issues.apache.org/jira/browse/IGNITE-14275
Project: Ignite
Andrey N. Gura created IGNITE-14276:
---
Summary: Local maven build runs tests while they are switched off
by skipTests option
Key: IGNITE-14276
URL: https://issues.apache.org/jira/browse/IGNITE-14276
@Valentin Kulichenko , @Nikolay Izhikov
, @samvi...@yandex.ru ,
I saw you reviewing the ticket. Could you please double-check the changes?
"IGNITE-2399: Implement acquireAndExecute In IgniteSemaphore"
Atri, please put a ticket number and name in the title of an email, so that
community member ca
Discussed with Petr privately. Proposal is:
1. The [Build] job runs without any checks.
2. There will be a new job [Sanity Checks], that runs all checks -
checkstyle, licenses, javadoc, check-suites.
3. [Sanity Checks] runs in parallel with [Build].
4. All TC jobs with tests depend on a result of
Konstantin Orlov created IGNITE-14277:
-
Summary: Calcite.
Key: IGNITE-14277
URL: https://issues.apache.org/jira/browse/IGNITE-14277
Project: Ignite
Issue Type: Improvement
Comp
Maxim,
Can you clarify what means '[Sanity Checks] runs in parallel with
[Build]'? AFAIK the checks need the build results to run themselves.
On Wed, 3 Mar 2021 at 18:48, Max Timonin wrote:
>
> Discussed with Petr privately. Proposal is:
>
> 1. The [Build] job runs without any checks.
> 2. There
I mean that any TC job with tests depends on both [Build], [Sanity Checks].
No tests run if any of those jobs failed.
[Build] prepares ignite.zip for distribution between TC agents (mvn
install).
[Sanity Checks] checks that code is correct in terms of our static checks
(mvn test).
Indeed it can b
Yes, they can be performed as parallel, as doesn't depend on each other.
There is an overhead for running git + mvn test twice, but it is a cost for
the flexibility.
On Wed, Mar 3, 2021 at 8:55 PM Max Timonin wrote:
> I mean that any TC job with tests depends on both [Build], [Sanity
> Checks].
Dear Community,
The release candidate is ready. The rest of the documentation pages
will be completed prior to the release announcement message. Please,
see the links below.
I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.10.0-rc1/
https://dist.apache.org/
Max,
> There is an overhead for running git + mvn test twice, but it is a cost for
> the flexibility.
Yes, I mean this issue. I have no objections, the build queue seems to
be empty most of the time.
On Wed, 3 Mar 2021 at 21:01, Max Timonin wrote:
>
> Yes, they can be performed as parallel, as
Atri,
I've added my comments in the PR.
-Val
On Wed, Mar 3, 2021 at 7:29 AM Denis Magda wrote:
> @Valentin Kulichenko , @Nikolay Izhikov
> , @samvi...@yandex.ru ,
>
> I saw you reviewing the ticket. Could you please double-check the changes?
> "IGNITE-2399: Implement acquireAndExecute In Ignit
The Project Management Committee (PMC) for Apache Ignite has invited
Mauricio Stekl to become a committer and we are pleased to announce
that he has accepted.
Mauricio is the contributor who has been maintaining and improving our
website for the last two years. There are countless small and
signif
Petr,
Any suggestions on how to fix this? One of the ideas that come to my mind
is to unify the process. For example, by enforcing that all changes are
merged only through PRs. That, however, means that all contributors are
forced to work with GitHub, which is not necessarily a great thing.
Thoug
Maksim Timonin created IGNITE-14278:
---
Summary: Design public Index API
Key: IGNITE-14278
URL: https://issues.apache.org/jira/browse/IGNITE-14278
Project: Ignite
Issue Type: New Feature
23 matches
Mail list logo
