Mikhail,
I think you've answered your first question in your second question. The
CQ handler on client nodes does not make sense because there is no data on
client nodes that can be notified of, therefore there is no reason to fail
the CQ as it does not affect the execution in any way.
As for the
Hello!
I would like to contribute to apache ignite and i am asking for
contribution permission.
I would like to start with IGNITE-12890.
My github username: makedonskaya
Jira username: makedonskaya
Hello!
I have added you to Contributors role, you can now assign this issue to
yourself.
Please make sure to read
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
Regards,
--
Ilya Kasnacheev
пн, 13 апр. 2020 г. в 12:25, Maria Makedonskaya :
> Hello!
>
> I would like to co
Oleg Ostanin created IGNITE-12891:
-
Summary: Add userAttributes map to all GridClient messages
Key: IGNITE-12891
URL: https://issues.apache.org/jira/browse/IGNITE-12891
Project: Ignite
Issue
Since there are no objections, I'll go ahead with removal.
Thanks
On Wed, Apr 8, 2020 at 10:35 PM Pavel Tupitsyn wrote:
> Igniters,
>
> Let's remove "This operating system has been tested less rigorously"
> diagnostic [1] [2].
> It does not make sense:
> * All Linux and macOS versions are consi
Hello, Igniters!
Recently we added the possibility of sending user defined attributes from
clients, and check those attributes in a custom authenticator
implementation[1]. However in some cases it's not working well for
GridClient because currently the attributes are only added to TOPOLOGY
message
+1
We should garantee user attributes transmission to cluster once they are
set in client configuration.
пн, 13 апр. 2020 г. в 15:09, Oleg Ostanin :
> Hello, Igniters!
>
> Recently we added the possibility of sending user defined attributes from
> clients, and check those attributes in a custom
Alexey,
Thanks for clarification. I think that is all I wanted to know.
Thank you.
On 13.04.2020 11:43, Alexey Goncharuk wrote:
Mikhail,
I think you've answered your first question in your second question. The
CQ handler on client nodes does not make sense because there is no data on
client n
I'm ok with that approach. Petr, what's your thinking?
-
Denis
On Fri, Apr 10, 2020 at 4:20 PM Maxim Muzafarov wrote:
> Denis, Petr
>
> If I'll prepare pgp and sha512 for this Google Compute Image file [1]
> is there any official repository where we can store these files to use
> them?
> Can w
Hello Saikat,
You can find short website development guidelines on this page [1]. They
are elementary and request to use pull-requests, especially, if the one is
not a committer. Feel free to elaborate on the process.
Btw, what are the scripts referred by you?
[1] https://cwiki.apache.org/conflu
Semyon Danilov created IGNITE-12892:
---
Summary: Clarify WAL archive size configuration
Key: IGNITE-12892
URL: https://issues.apache.org/jira/browse/IGNITE-12892
Project: Ignite
Issue Type: S
Maxim Muzafarov created IGNITE-12893:
Summary: Add support for the SimplifyBooleanExpression rule to
checkstyle
Key: IGNITE-12893
URL: https://issues.apache.org/jira/browse/IGNITE-12893
Project: I
Alexey Kukushkin created IGNITE-12894:
-
Summary: Cannot use IgniteAtomicSequence in Ignite services
Key: IGNITE-12894
URL: https://issues.apache.org/jira/browse/IGNITE-12894
Project: Ignite
Folks,
As another suggestion, we can place such files (pgp, sha512) here
https://downloads.apache.org/ignite/gce/ (`gce` directory must be
created). I don't have access rights there.
All files have been prepared by me. I'm ready to provide them.
On Mon, 13 Apr 2020 at 19:49, Denis Magda wrote:
Igniters,
It's really `must-have` feature for me to enable Apache Ignite
pull-request status checks on GitHub. Currently we don't have any of
them. The most obvious check for each pull-request is:
- build the source code and check code-style violations;
This will give us some advantages. For ins
Igniters, especially those who write blog posts or create presentations for
various talks,
As part of the website redesign, we've produced new Ignite diagrams and
pictures that are hosted in Ignite's website Github repo:
https://github.com/apache/ignite-website/tree/master/images/png-diagrams
I a
It's a good idea and many of mature projects have the same
вт, 14 апр. 2020 г., 2:14 Maxim Muzafarov :
> Igniters,
>
> It's really `must-have` feature for me to enable Apache Ignite
> pull-request status checks on GitHub. Currently we don't have any of
> them. The most obvious check for each pull
17 matches
Mail list logo
