Ramya Magham created IGNITE-12838:
-
Summary: Fails to start server with spring configuration with
known host addresses
Key: IGNITE-12838
URL: https://issues.apache.org/jira/browse/IGNITE-12838
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
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
Pavel,
1. Actually it can be solved on the client-side (and already solved in PoC
implementation). But I agreed it brings extra complexity for client-side
implementation, will try to provide such guarantees on the server-side.
2. ComputeTask has also "reduce" step which is executed on the
Alex, thanks for preparing the outline.
I'd like us to discuss an approach for compute tasks update with no
downtimes on the servers' end. For instance, let's assume that a
Python/C++/Node.JS developer requested to update a compute task he called
from the app. Should we introduce some system
Hi Alex,
First of all, thank you for preparing this IEP!
Protocol changes look good to me.
However, I have objections regarding race condition behavior and about Java
API.
1. "Due to some races, it's possible that notification for some task will
be delivered to the client before the response
Hi, Igniters!
Long ago I raised the issue [1]. The change is obvious yet useful; it
allows Ignite security implementations to manage per-cache-based
CACHE_CREATE/CACHE_DESTROY permissions (as opposed to system level
permissions). It is ready now, and some of community members have approved
it.
Hi Maxim,
Here is a ticket [1] where I've collected INFRA recommendations shared in
an adjacent discussion thread. Please check it, add anything new you heard
from them.
Feel free to take over this task, appreciate your help. However, please
give me a couple of days to finish the merge of the
Ilya Kasnacheev created IGNITE-12837:
Summary: Make sure Ignite leaves nothing in static fields after
node is stopped, write test
Key: IGNITE-12837
URL: https://issues.apache.org/jira/browse/IGNITE-12837
Hello guys.
I've implemented PoC and created IEP [1] for thin client compute grid
functionality. Please have a look.
[1]:
https://cwiki.apache.org/confluence/display/IGNITE/IEP-42+Thin+client%3A+compute+support
пт, 24 янв. 2020 г. в 16:56, Alex Plehanov :
> We've discussed thin client compute
Kirill Tkalenko created IGNITE-12836:
Summary: Writing methods to avoid limit of 65535 bytes for
java.io.DataOutput#writeUTF
Key: IGNITE-12836
URL: https://issues.apache.org/jira/browse/IGNITE-12836
Aleksey Plekhanov created IGNITE-12835:
--
Summary: Thin client: compute support
Key: IGNITE-12835
URL: https://issues.apache.org/jira/browse/IGNITE-12835
Project: Ignite
Issue Type: New
Igniters,
I've recently found that some of our releases were missed at the
Apache announce mail list: 2.6.0 [4], 2.7.0 [5], 2.8.0 [3].
I've contacted the Apache announce list moderators and got the
requirements for our download page [6] (see the message below). I'm
going to update the download
13 matches
Mail list logo
