Aleksey Plekhanov created IGNITE-12399:
--
Summary: Java thin client: add cache expiry polocies
Key: IGNITE-12399
URL: https://issues.apache.org/jira/browse/IGNITE-12399
Project: Ignite
Is
Hi, Ivan.
I'm sorry that the discussion was moved in private channel. The problem
I'm trying to solve is described below in the thread. The security
plugin in my case stores and analyzesinfo about a node that failed to join.
Regards,
Mikhail.
Forwarded Message
Subject:
> Since all thin client operations are inherently async, we should be able
to cancel any of them
It's illogical to have such ability. What should do cancel operation of
cancel operation? Moreover, sometimes it's dangerous, for example, create
cache operation should never be canceled. There should b
Hello, Alex.
I think we should improve article formatting - code highlight, fonts, etc.
For now, it’s very hard to read it.
Can you, please, do it?
> 28 нояб. 2019 г., в 09:25, Ivan Pavlukhin написал(а):
>
> Alexei,
>
> Many thanks for that article! Really nice that now we have a document
>
Hello, Igniters.
Join us on Ignite meetup!
There will be cool old fashioned geeky Ignite talks and a "round table"
discussion about Ignite future.
It will happen on *December 3 in Moscow* and will be hosted by Sberbank near
the subway Kutuzovskaya.
Topics:
* Ignite affinity function.
* upc
Alexei,
Many thanks for that article! Really nice that now we have a document
describing Ignite approach for data consistency. I think it is super
important because it is not trivial and very Ignite specific. I
believe lots of Ignite developers will learn something new from this
document.
By the
Hi Mikhail,
Interesting topic. Could you please shed some light how a node
validation failure can be handled? Immediately cannot imagine how one
can handle it.
чт, 21 нояб. 2019 г. в 14:17, Mikhail Petrov :
>
> Hi, Andrey.
>
> I take part in the development of a custom security plugin for Apache
Alex,
Thanks a lot for putting your knowledge on paper. That's an invaluable
contribution!
Looping in the user community (will be interesting for those who use native
persistence) and has just spread the word via Ignite twitter handle:
https://twitter.com/ApacheIgnite/status/1199837055007612928
Igniters,
There are many of us who are spreading the word about Ignite globally. Does
anybody have any technical talk of moderate and advanced complexity for the
O'Reilly Software Architecture conference?
https://conferences.oreilly.com/software-architecture/sa-ca/public/content
The more we submi
Hi Maxim,
Sounds good, thanks for branching. Could you double-check that the
following issue was added to the release?
https://issues.apache.org/jira/browse/IGNITE-10577
-
Denis
On Wed, Nov 27, 2019 at 7:50 AM Maxim Muzafarov wrote:
> Igniters,
>
>
> I think we are ready to create the 2.8 rel
Hi all,
I did add a test suite and run the build with the corresponding arguments,
however the tests did not run [1].
I checked the Flink's build logs and the same message is displayed there
too `No tests to run` [2].
[1]
https://ci.ignite.apache.org/viewLog.html?buildId=4798203&buildTypeId=Ignit
Hi Saikat,
Thanks for driving this activity forward and raising the question. Let me
share my thoughts below and let's see what the broader community thinks.
Each extension needs to have its own version unrelated to the core and
Maven's groupId parameter for extension artifacts should be
"org.apa
Hi,
We will need to add test suites for tests to be executed in build. We pass
them as TestSuites param. I had added Flink sink and source testsuites.
Can you please review and confirm.
Regards
Saikat
On Wed, 27 Nov 2019 at 6:00 AM, Emmanouil Gkatziouras
wrote:
> Hi all!
>
> I was successful
> The request is already processed (task is started), we can't cancel the
request
The request is not "start a task". It is "execute task" (and get result).
Same as "cache get" - you get a result in the end, we don't "start cache
get" then "end cache get".
Since all thin client operations are inhe
Igniters,
I think we are ready to create the 2.8 release branch since features
[1] which we are waiting for are almost completed.
4 December 2019, the 2.8 release branch will be created. All related
issues with a priority less than `critical` will be excluded from the
2.8 release (fix version wi
> We do cancel a request to perform a task. We may and should use this to
cancel any other request in future.
The request is already processed (task is started), we can't cancel the
request. As you mentioned before, we already do almost the same for queries
(close the cursor, but not cancel the re
Hi all!
I was successful building and running my pull requests. It seems that the
tests do not run both for Flink and Pub/Sub [1]
If there is something I cannot do to make them discoverable please let me
know.
[1]
https://ci.ignite.apache.org/viewLog.html?buildTypeId=IgniteExtensions_Build&buildI
Great news, thanks!
On Wed, Nov 27, 2019 at 11:29 AM Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:
> Igniters,
>
> As a final action in my almost year long effort in repairing data
> consistency related issues for transactional persistent caches I've
> prepared an article explaining th
Igniters,
As a final action in my almost year long effort in repairing data
consistency related issues for transactional persistent caches I've
prepared an article explaining the principles of achieving the consistency
between partition copies for these scenarios [1]
Comments and suggestions are w
19 matches
Mail list logo
