Denis, finally I understood your arguments about interfaces check, thank
you for the explanation.
I agree with the proposal to introduce a new method which returns proxy
include the case of locally deployed services.
Also, such a method should be able to work in mode "local services
preferred", p
XuCongying created IGNITE-12738:
---
Summary: CVEs in the dependencies are in the execution path of
your project
Key: IGNITE-12738
URL: https://issues.apache.org/jira/browse/IGNITE-12738
Project: Ignite
Alexey Goncharuk created IGNITE-12739:
-
Summary: Optimistic serializable transactions may fail infinitely
when read-through is enabled
Key: IGNITE-12739
URL: https://issues.apache.org/jira/browse/IGNITE-12739
Hi Team,
We are trying to use Ignite Hadoop Accelerator for one of our implementation.
But I understand Ignite Hadoop Acceleration is to be discontinued very soon.
Need to know the alternatives to the Accelerator to use Ignite for Hadoop file
system.
Thanks,
Prachi
This message contains info
Hi,
I believe, we definitely should not ignore this.
Alexey, you are the author of this code. What do you think?
Best Regards,
Igor
On Thu, Feb 27, 2020 at 3:56 PM Aleksandr Shapkin wrote:
> Hello!
>
>
>
> I just noticed that the Java thin client throws the following internal
> exceptions:
>
Hi Guys,
Most likely I just forgot to remove the "internal" ClientError and
ClientProtocolError when I was implementing a review comment to merge the
Java thin client into ignite-core (originally I developed the Java thin
client as a separate module). I see that the ClientProtocolError is not
used
Taras Ledkov created IGNITE-12740:
-
Summary: Supports feature flags on index meta pages
Key: IGNITE-12740
URL: https://issues.apache.org/jira/browse/IGNITE-12740
Project: Ignite
Issue Type: T
Alexey Scherbakov created IGNITE-12741:
--
Summary: Allow exchange merges for PME free switch.
Key: IGNITE-12741
URL: https://issues.apache.org/jira/browse/IGNITE-12741
Project: Ignite
Iss
Hi everyone,
Looks like the following line from the Ignite 2.8 release notes is a bit
of an overstatement and should be removed:
> Added support best effort affinity for thin clients (partition awareness)
Java thin client does not support partition awareness. Nodejs and python
thin clients f
Surkov Aleksandr created IGNITE-12742:
-
Summary: Thick client: client hangs when trying to connect to port
10800
Key: IGNITE-12742
URL: https://issues.apache.org/jira/browse/IGNITE-12742
Project:
Surkov Aleksandr created IGNITE-12743:
-
Summary: Thin client: thread does not stop
Key: IGNITE-12743
URL: https://issues.apache.org/jira/browse/IGNITE-12743
Project: Ignite
Issue Type: Bu
That's right, only C++ and .NET clients have partition awareness
Best Regards,
Igor
On Tue, Mar 3, 2020 at 5:02 PM Artem Budnikov
wrote:
> Hi everyone,
>
> Looks like the following line from the Ignite 2.8 release notes is a bit
> of an overstatement and should be removed:
>
> > Added support
Andrey Kuznetsov created IGNITE-12744:
-
Summary: Add user attributes to GridRestRequest creation routine
Key: IGNITE-12744
URL: https://issues.apache.org/jira/browse/IGNITE-12744
Project: Ignite
Folks,
This is in the `Ignite Core` section, so I think mostly related to
java functionality and thin client protocol extension [1]. Sorry for
not being too accurate with this statement
.
The same change is mentioned for C++ and .NET sections of the release
notes (but not for other thin clients).
Hi, Igniters!
If you are from the areas mentioned in subj, consider signing for events
featuring Ignite talks by our contributors and PMCs. Unless the spread of
coronavirus puts off those, you'll be able to meet our community experts in
person and challenge with your questions.
2020-03-09, San Fr
Nikolay Izhikov created IGNITE-12745:
Summary: Compute job system view
Key: IGNITE-12745
URL: https://issues.apache.org/jira/browse/IGNITE-12745
Project: Ignite
Issue Type: Sub-task
Hello!
Can we please hold back publishing AI-2.8.0-rc1 as public Apache Ignite 2.8
release?
I have just been notified that
org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedColocated
org.apache.ignite.internal.processors.cache.distributed
Ilya,
I do not want to force the release no matter what happens, but I think
we should release what we have to get feedback not just from the
developer community but from our users too.
And fix all these issues in 2.8.1.
On Tue, 3 Mar 2020 at 20:33, Ilya Kasnacheev wrote:
>
> Hello!
>
> Can we
Igniters,
Let's discuss approaches for a global announcement/promotion of the
release. I would suggest focusing on a blog post and a community webinar.
The blog post will introduce significant improvements (service grid, thin
clients, new metrics system, ML, etc.) sharing references to documentat
Sounds ineresting, will help with the post, please share the template, not
sure about webinar
вт, 3 мар. 2020 г., 20:59 Denis Magda :
> Igniters,
>
> Let's discuss approaches for a global announcement/promotion of the
> release. I would suggest focusing on a blog post and a community webinar.
>
>
Igniters,
I've just found that a script with docked Apache Ignite on docker hub
site [1] doesn't work for newer versions (start from 2.6.0?) since the
word `fabric` has been removed from a release distribution name.
Can we update this documentation to the newer one?
I can also suggest using this
Folks,
I've done (with Santa's help) most of the steps related to the 2.8.0 RELEASE.
Here are some links according to accepted the release candidate.
Binary, Sources:
https://dist.apache.org/repos/dist/release/ignite/2.8.0/
Bintray:
https://bintray.com/apache/ignite-rpm/apache-ignite/2.8.0
htt
Ilya Kasnacheev created IGNITE-12746:
Summary: Regression in GridCacheColocatedDebugTest: putAll of
sorted keys causes deadlock
Key: IGNITE-12746
URL: https://issues.apache.org/jira/browse/IGNITE-12746
Hello!
I have filed an issue https://issues.apache.org/jira/browse/IGNITE-12746
I think this is potentially a game breaker and makes me recommend avoiding
2.8, if we release it without fix (for now).
If you are using any partitioned caches, anyway.
So I suggest we withhold 2.8.
Regards,
--
Il
Could we also update the "Overview" page with the content from the README
file of GitHub?
https://github.com/apache/ignite/blob/master/README.md
-
Denis
On Tue, Mar 3, 2020 at 1:26 PM Maxim Muzafarov wrote:
> Igniters,
>
>
> I've just found that a script with docked Apache Ignite on docker hub
Ilya,
Thanks for catching that and sharing. I wonder if there are any other
blockers that were pushed to 2.8.x version. If there are a few then we can
produce 2.8.1 shortly, otherwise, it sounds reasonable to me to fix the
issue with putAll, update the binaries and finish the process.
-
Denis
O
Hello Prachi,
A recommended approach is to deploy Ignite in its standard configuration
and pre-load the required data there. This page shares more details:
https://www.gridgain.com/docs/latest/integrations/datalake-accelerator/getting-started
In case synchronization is needed between Ignite and H
Awesome!
Thanks for leading this.
BTW, do we have plans to start 2.9 release process in nearest future?
On Tue, Mar 3, 2020 at 11:07 PM Maxim Muzafarov wrote:
> Folks,
>
>
> I've done (with Santa's help) most of the steps related to the 2.8.0
> RELEASE.
> Here are some links according to accept
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
ср, 4 мар. 2020 г., 8:46 Anton Vinogradov :
> Awesome!
> Thanks for leading this.
>
> BTW, do we have plans to start 2.9 release process in nearest future?
>
Hello, Igniters.
Do we have a person who can fix this issue in the nearest time?
Right now IGNITE-12746 is Open and Unassigned.
> 3 марта 2020 г., в 23:54, Denis Magda написал(а):
>
> Ilya,
>
> Thanks for catching that and sharing. I wonder if there are any other
> blockers that were pushed to
30 matches
Mail list logo
