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
I managed to get some build using build number from 1. Release build step
(for that case - 20)
The result can be found here
https://ci.ignite.apache.org/viewLog.html?buildId=4049646=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages=artifacts#%2Fsrc
Pavel T., Peter I.,
Please confirm that
I've found only this step
https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages=buildTypeStatusDiv_Releases_ApacheIgniteMain=__all_branches__
It requires some build counter.
Peter I, could you please chime in?
ср, 5 июн. 2019 г. в 18:02,
Hi Igniters, Pavel T.,
I'm struggling to find clear steps for building/uploading NuGet packages.
How can I double check if it was built or not? What should I do?
In some internal notes, I've found that NuGet upload can't be undone, and
in
+1 (binding)
On Wed, Jun 5, 2019 at 4:39 PM Ilya Kasnacheev
wrote:
>
> +1
>
> Built C++ and .Net successfully, started .Net <-> Java <-> C++ SSL Cluster
> on Java 11 and Java 8 without tuning any flags.
> --
> Ilya Kasnacheev
>
>
> ср, 5 июн. 2019 г. в 09:44, Nikolay Izhikov :
>
> > +1 (binding)
Alexey,
This is a cool change, do you create a ticket for it?
If no I can create one.
Best regards,
Yuriy Babak
пт, 31 мая 2019 г. в 14:20, Алексей Платонов :
> Hi, Igniters!
> Currently we don't have an ability to deploy automatically user-defined
> preprocessors and vectorizers. Client's
+1
Built C++ and .Net successfully, started .Net <-> Java <-> C++ SSL Cluster
on Java 11 and Java 8 without tuning any flags.
--
Ilya Kasnacheev
ср, 5 июн. 2019 г. в 09:44, Nikolay Izhikov :
> +1 (binding)
>
> В Ср, 05/06/2019 в 01:11 +0100, Denis Magda пишет:
> > +1 (binding)
> >
> > Nice to
Hi Ivan,
In code there are 2 differences:
- TLSv1.2 is used as a default protocol for Communication in case SSL is
used.
- version changed for all pom files, so apache-ignite-src.zip now contains
correct version instead of -SNAPSHOT.
Sincerely,
Dmitriy Pavlov
ср, 5 июн. 2019 г. в 10:49,
Dmitriy Pavlov created IGNITE-11896:
---
Summary: [TC Bot] Comment JIRA may not work for case aliased TC is
used
Key: IGNITE-11896
URL: https://issues.apache.org/jira/browse/IGNITE-11896
Project:
Folks,
I've checked PR [1] and it seems to me it fixes the main issue with a
spark examples.
After adding `scala` profile the [Example] Suite in the master branch
starts to fail - [2] and it works fine in the PR branch [3] (Javadocs
also compiles).
Not sure, but adding this profile also fixes
Alexandr Shapkin created IGNITE-11895:
-
Summary: .NET Resharper inspections got broken after update
Key: IGNITE-11895
URL: https://issues.apache.org/jira/browse/IGNITE-11895
Project: Ignite
I've added 'scala' profile to ~Build Apache Ignite~.
Can you check please that everything is OK now?
> On 5 Jun 2019, at 12:16, Nikolay Izhikov wrote:
>
> Petr.
>
> Current PR solves the following issue: "Data Frame examples crashes in
> master".
>
> We need to solve one more issue:
>
>
Maksim,
I agree with you that we should implement current issue and do not
allow lightweight PME if there are MOVING partitions in the cluster.
But now I'm investigating issue about finalizing update counters cause
it assumes that finalizing happens on exchange and all cache updates
are
Petr.
Current PR solves the following issue: "Data Frame examples crashes in master".
We need to solve one more issue:
"Data Frame examples not tested on TC" - this require "scala" profile in "Build
Ignite" suite.
В Ср, 05/06/2019 в 12:05 +0300, Petr Ivanov пишет:
> > On 5 Jun 2019, at
Alex and all,
> From a user's point of view:
> Inactive cluster - deny writes, deny reads.
> Read-only cluster - deny writes, allow reads.
I would be great to explain what is the need to deny both reads and
writes. What tasks are not possible to solve when cluster is in
read-only state?
ср, 5
> On 5 Jun 2019, at 11:49, Nikolay Izhikov wrote:
>
>> 1. Why does your PR show only single file changed?
>
> Because this change fix the issue described in the ticket [1]
So changes in intermediate commits were reverted in branch?
>
>> 2. Can you describe the problem once more, please?
Ivan,
>From a user's point of view:
Inactive cluster - deny writes, deny reads.
Read-only cluster - deny writes, allow reads.
ср, 5 июн. 2019 г. в 10:44, Павлухин Иван :
> Sergey,
>
> > On inactive cluster caches aren't started. So you can't get data from
> cache.
>
> As a user I do not
> 1. Why does your PR show only single file changed?
Because this change fix the issue described in the ticket [1]
> 2. Can you describe the problem once more, please? Is it about
:ignite-examples module not being build in ~Build Apache Ignite~ ?
Spark examples activated only if `scala` profile
Nikolay,
1. Why does your PR show only single file changed?
2. Can you describe the problem once more, please? Is it about :ignite-examples
module not being build in ~Build Apache Ignite~ ?
> On 4 Jun 2019, at 20:34, Nikolay Izhikov wrote:
>
> Hello, Igniters.
>
> Root of the issue is in
Dmitriy,
Are there any differences between 2.7.5-rc4 and a previous RC?
вт, 4 июн. 2019 г. в 20:35, Dmitriy Pavlov :
>
> Dear Community,
>
>
>
> Please use this thread for all non-voting, discussion, questions related to
> this release.
>
>
>
> Cast your vote here
>
Sergey,
> On inactive cluster caches aren't started. So you can't get data from
cache.
As a user I do not understand what does it mean for cache to be
started. IgniteCache does not provide start/stop methods.
I am trying to figure out why there should be 2 modes (not from an
implementation
+1 (binding)
В Ср, 05/06/2019 в 01:11 +0100, Denis Magda пишет:
> +1 (binding)
>
> Nice to have clusters nodes started with ignite.sh in my JVM 11 environment
> without any settings.
>
> -
> Denis
>
>
> On Tue, Jun 4, 2019 at 6:34 PM Dmitriy Pavlov wrote:
>
> > Dear Community,
> >
> >
> >
22 matches
Mail list logo
