Denis Garus created IGNITE-12282:
Summary: Access restriction to the internal package of Ignite
Key: IGNITE-12282
URL: https://issues.apache.org/jira/browse/IGNITE-12282
Project: Ignite
Issue
Denis Garus created IGNITE-12283:
Summary: Access restriction to IgniteKernal
Key: IGNITE-12283
URL: https://issues.apache.org/jira/browse/IGNITE-12283
Project: Ignite
Issue Type: Task
Folks,
As a prereviewer, I'd like to say that the solution looks good to me, but
fresh eyes would be good.
On Fri, Oct 11, 2019 at 9:40 AM Denis Garus wrote:
> Hello, Igniters!
>
> I've raised the PR [1] with the sandbox for AI [2].
> Could somebody review it?
>
> If you have questions and pref
Hello Denis, Anton,
Could you please clarify the following aspect? Do we need the same
changes/capabilities related to Continuous Queries, Disco listeners,
CacheStore Factories etc?
Thanks,
S.
пт, 11 окт. 2019 г. в 12:24, Anton Vinogradov :
> Folks,
>
> As a prereviewer, I'd like to say that th
Hello, Slava!
The scope of the issue is limited by the following features:
- StreamReceiver for DataStreamer;
- EntryProcessor;
- ComputeJob;
- filter and transformer for ScanQuery.
But, sure, we should execute any user-defined code in the sandbox on a
remote node.
Feel free to creat
Hi Denis,
Yep, I understand the scope of the ticket, but... I think it is not a good
idea to merge partly implemented feature(s) into the master branch.
Especially, at this moment. We are at the stage of preparing a new release
and I doubt that all improvements, tests (unit tests, integration test
>From my point, we should divide the sandbox and features that use it.
The sandbox is fully implemented and has needed tests.
Also, I added in the main features of Ignite (cache and compute) the
sandbox calls.
I don't see any problem to have the sandbox in the master branch
and implement covering
Hi Denis,
In my humble opinion, the security (the sandbox feature is about security,
right?) either covers all APIs/subsystems or not.
Security should work always and everywhere otherwise it is not security :)
> From my point, we should divide the sandbox and features that use it.
> Also, I added
Hello Mulugeta, Igniters.
Thanks for your interest and efforts in integrating the persistent memory
to Ignite. Here are my thoughts on the PR:
First of all I was questioning whether we want to use the integration with
the pmem library via JNI. Java 14 will have native support for NVME via
native
Ilya Kasnacheev created IGNITE-12284:
Summary: When service class not found on any server nodes, service
not deployed without any error
Key: IGNITE-12284
URL: https://issues.apache.org/jira/browse/IGNITE-12284
Denis, thank you,
>
> Would you also keep our events page up-to-date?
Sure, I will do this gladly.
Sally, nice to meet you!
пт, 11 окт. 2019 г. в 00:12, Denis Magda :
> Kseniya, welcome to the community and thanks for offering the help with
> these activities. Most of us are focused on the code
Hello Emmanouil,
Are you referring to any specific implementation tailored for a cloud? If
I'm not mistaken you were mentioning AWS/GCE. Is there any Github source
code?
Here is a list of existing integrations with streaming and pub/sub
frameworks:
https://apacheignite-mix.readme.io/docs/overview
Hi all,
By mentioning Pub/Sub I mean Google Cloud's Pub/Sub [1]
Yes it is indeed cloud specific. It is the messaging service provided by
GCP.
I have made the integration with it, but I haven't published it yet (I am
waiting for the discussion/ticket and proceed with the contribution).
Kind regard
Hello Emmanouil,
Can you please share more info about the implementation?
We have similar implementation for data streamers with Kafka and RocketMQ
https://apacheignite-mix.readme.io/docs/kafka-streamer
https://apacheignite-mix.readme.io/docs/rocketmq-streamer
Please review and share if you ha
Hello Ivan,
I have updated the PR as per our discussion.
Please review and share your feedback.
Regards,
Saikat
On Sun, Sep 1, 2019 at 3:20 PM Saikat Maitra
wrote:
> Hi Ivan,
>
> I have taken care of review comments and also have shared a question for
> the application of default Query timeou
15 matches
Mail list logo