Ivan,
I did something wrong?
What should I do to release all effectively?
On Thu, 5 Mar 2020 at 08:23, Denis Magda wrote:
>
> Ivan,
>
> The release of binaries is one of the final steps. There are still several
> steps left before we can consider all the 2.8 release activities completed:
> https
Ivan,
The release of binaries is one of the final steps. There are still several
steps left before we can consider all the 2.8 release activities completed:
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-6.3.4.Releasedocumentaiononreadme.io
https://cwiki.apache.o
Denis, folks,
As it was already mentioned 2.8 is already in maven [1]. Consequently
"effectively" released. In my opinion it is not correct to consider
release in progress.
Agree that 2.8.1 sounds as a proper option here.
[1] https://mvnrepository.com/artifact/org.apache.ignite/ignite-core/2.8.0
> That's right, only C++ and .NET clients have partition awareness
Are your sure? Was not the feature implemented for java thin client in [1]?
[1] https://issues.apache.org/jira/browse/IGNITE-11898
Best regards,
Ivan Pavlukhin
ср, 4 мар. 2020 г. в 18:18, Denis Magda :
>
> Maxim,
>
> Yes, it's p
Hi Evgenii,
I am individually Put()ing the elements using PutIfAbsent(). Each element
can range 2kb-35Kb in size.
Actually, the process that writes the data does not write the data directly
to the cache, it uses a compute function to send the payload to the process
that is doing the reading. The
Hi,
How are you loading the data? Do you use putAll or DataStreamer?
Evgenii
ср, 4 мар. 2020 г. в 15:37, Raymond Wilson :
> To add some further detail:
>
> There are two processes interacting with the cache. One process is writing
> data into the cache, while the second process is extracting da
To add some further detail:
There are two processes interacting with the cache. One process is writing
data into the cache, while the second process is extracting data from the
cache using a continuous query. The process that is the reader of the data
is throwing the exception.
Increasing the cac
I've been having a sporadic issue with the Ignite 2.7.5 JVM halting due to
out of memory error related to a cache with persistence enabled
I just upgraded to the C#.Net, Ignite 2.7.6 client to pick up support for
C# affinity functions and now have this issue appearing regularly while
adding around
Hi Igniters,
Let me introduce you to Mike James, who has been working on a gripping
project that uses Apache Ignite as a backbone for a distributed DMX Control
system. That's a use case of the entertainment industry and, hopefully,
many rockstars will switch to the solution to produce light effect
Nikolay Izhikov created IGNITE-12749:
Summary: Unsupported operation exception on node stop if
collisionspi not null
Key: IGNITE-12749
URL: https://issues.apache.org/jira/browse/IGNITE-12749
Proje
Andrei,
I am also working with Apache Ignite ML and am interested in providing
wrappers for Ignite ML API, but am wondering if instead of simply recreating
the low level Java API for ML inside Python, how about creating some higher
level services "Auto ML" workflow ? For example:
1. here is raw
Dear Community,
I was very inspired in Ignite ML and I wanted to try it with Python.
Particularly I was interested in compares Ignite ML VS Spark ML
However, I came across the fact that pyignite component allows only to
perform basic cache operations through the API and it has nothing to do w
Vyacheslav, Denis, hi again.
>>> I agree with the proposal to introduce a new method which returns proxy
include the case of locally deployed services.
I see one is restricted to use an interface for service with
IgniteServiceProcessor#serviceProxy(…):
A.ensure(svcItf.isInterface(), "Servi
Maxim,
Yes, it's preferable to have metrics pages fully completed even though the
feature is an experimental state. We want to encourage to try it out and
switch to the new APIs eventually. Without technical instructions available
our users will have a hard time checking the new capabilities.
Nik
I think yes.
I will prepare documentation shortly.
> 4 марта 2020 г., в 17:50, Maxim Muzafarov написал(а):
>
> Folks,
>
>
> Do we need a fully complete public documentation for metrics marked
> with @ExperimentalFeature? The API can significantly be changed.
>
> On Wed, 4 Mar 2020 at 17:10,
Folks,
Do we need a fully complete public documentation for metrics marked
with @ExperimentalFeature? The API can significantly be changed.
On Wed, 4 Mar 2020 at 17:10, Artem Budnikov wrote:
>
> The only feature that is left is "WAL page compression"
>
> The three other features are limitation
Andrey N. Gura created IGNITE-12748:
---
Summary: PushMetricsExporterAdapter based exporters could lead to
exceptions on getting gauge value
Key: IGNITE-12748
URL: https://issues.apache.org/jira/browse/IGNITE-12748
Hi Pavel,
Excellent! It will be good to publish the first article (what's new in
Ignite.NET 2.8) prior to a generic blog on blogs.apache.org so that we can
link your post in for those who are looking for more details. Do you have
any timeline in mind for this article?
@Alexey Zinoviev , how about
The only feature that is left is "WAL page compression"
The three other features are limitations that were present in Ignite
2.7 and now they are removed. Since they were never mentioned in the
docs, there is nothing to do.
-Artem
On 04.03.2020 17:02, Denis Magda wrote:
I'll work on the fo
Dmitriy,
Ignite 2.8 will be announced as soon as the documentation is prepared and
released. Until then, the release is still considered under progress. Here
is a dedicated discussion for documentation activities. We should be ready
soon:
http://apache-ignite-developers.2346864.n4.nabble.com/Ignit
>
> I'll work on the following items today and tomorrow:
>
>- JDBC: Support for query cancellation
>
>
>- JDBC: Support for query timeout
>
>
>- suspend/resume for pessimistic transactions
>
>
>- WAL page compression
>
>
Artem, are these the only tickets left apart f
Artem,
IEP [1] answers this in detail, but in brief...
Cons:
- each get() cost, when RR used, increased by requests to each backup,
- read from backup, near cache and external store usage are impossible.
Pros:
- consistency may be checked online (no need to turn off the cluster),
- consistency w
Hello!
Thank you for leading this discussion.
I agree with some other voices that we should never start voting about new
release over the weekend. I think that only monday and tuesday are suitable
for new release votings, since it guarantees that announcement, voting and
decision all happen on we
Ilya, let me personally thank you for checking and filing this bug.
I checked timeline for [result] [vote] email and new email describing new
issue. Unfortunately, after closing the vote it is not possible to stop
release from publishing (only if RM will delay publish stage after closing
the vote)
Hi Folks,
Unfortunately https://dist.apache.org/repos/dist/release/ignite/2.8.0/ is
already there, so release was happened. I'm not sure it is a good idea to
substitute binaries later. Was it announced to announce@ ?
IMO, 2.8.1 is ok for that case.
Sincerely,
Dmitriy Pavlov
ср, 4 мар. 2020 г.
Anton,
Yes, I can add this feature to the docs. I have a couple of questions,
though:
* Are there any downsides to using this feature?
* When users should use it? What are the recommendations?
-Artem
On 04.03.2020 13:46, Anton Vinogradov wrote:
Artem,
Is it possible to create documentati
GCE image is broken but it is a "know issue" and will be fixed some time later.
AWS image is self sufficient — no additional steps required to run Apache
Ignite 2.8.0 on AWS using it.
> On 4 Mar 2020, at 14:08, Maxim Muzafarov wrote:
>
> Pavel, Pert, Nikolay,
>
>
> Thank you all for your hel
Igor Seliverstov created IGNITE-12747:
-
Summary: Calcite integration. Correlated queries support.
Key: IGNITE-12747
URL: https://issues.apache.org/jira/browse/IGNITE-12747
Project: Ignite
Hello!
My opinion is that we have what we have and I recommend using the API
provided with Apache Ignite.
Regards,
--
Ilya Kasnacheev
чт, 27 февр. 2020 г. в 13:57, Sunny Chan, CLSA :
> Just to make it clear, you prefer the option 1 in my suggestion? That is
> listed out all the potential conf
Pavel, Pert, Nikolay,
Thank you all for your help. I stuck yesterday due to don't have
sufficient privileges to complete some of the release steps.
Currently, all of them have been completed.
Do I need something to do with these additional steps?
AWS deployment --
https://console.aws.amazon.com
Artem,
Is it possible to create documentation for ReadRepair feature [1] [2]?
Feature marked as @IgnireExperimenta but ready to be used.
Javadoc [3] explains the details.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-31+Consistency+check+and+fix
[2] https://issues.apache.org/jira/brow
Hi everyone,
I have created the docs for the following items so far:
* Default Ignite work dir location
https://apacheignite.readme.io/docs/getting-started-28#section-setting-up-work-directory
* Baseline auto-adjust feature
https://apacheignite.readme.io/docs/baseline-topolo
Hi everyone,
I have created the docs for the following items so far:
-Default Ignite work dir location
https://apacheignite.readme.io/docs/getting-started-28#section-setting-up-work-directory
- Baseline auto-adjust feature
https://apacheignite.readme.io/docs/baseline-top
Docker image uploaded.
> On 4 Mar 2020, at 11:37, Pavel Tupitsyn wrote:
>
> Maxim, what about the rest of the release steps, like Docker and NuGet? Do
> you need help with that?
>
> On Wed, Mar 4, 2020 at 9:33 AM Alexey Zinoviev
> wrote:
>
>> Maxim, you great, I was happy to work with you on
Maxim, what about the rest of the release steps, like Docker and NuGet? Do
you need help with that?
On Wed, Mar 4, 2020 at 9:33 AM Alexey Zinoviev
wrote:
> Maxim, you great, I was happy to work with you on that release, it was a
> very difficult task and it required a lot of your time, thank you
Denis, I have a few blog posts on Ignite.NET planned:
* What's new in Ignite.NET 2.8 (Thin Client Partition Awareness, logging,
expiry policy, cluster API, .NET Core 3.x, Dockerfile)
* Ignite.NET performance improvements on .NET Core 3.x
* Ignite.NET Partition Awareness performance
* Fixing JNI th
Pavel, ++1.
> 4 марта 2020 г., в 11:20, Pavel Tupitsyn написал(а):
>
> Igniters,
>
> The release has already happened.
> It is on our website [1], it is on Maven [2].
> People are using it, so I don't think we can do anything at this point.
>
> Bugs happen, we can't delay the release forever b
Igniters,
The release has already happened.
It is on our website [1], it is on Maven [2].
People are using it, so I don't think we can do anything at this point.
Bugs happen, we can't delay the release forever because of them. Let's fix
things in 2.8.1.
[1] https://ignite.apache.org/download.cgi
38 matches
Mail list logo
