Thanks for the report!
The issue here is that a remote filter for a continuous query is loaded
using peer class loading, and other classes that this remote filter depends
on can be lazily loaded during its work.
Loading every dependency class involves going to the node where the
originating class
Dmitriy, could you plz ?
>We can manage that here.
>
>
>> On 24 Mar 2020, at 13:29, Dmitriy Pavlov < dpav...@apache.org > wrote:
>>
>> Hi,
>>
>> I could potentially update this version in the source code, but I'm not
>> able to deploy new version to the server (since it is now sponsored by
>
Ilya Kasnacheev created IGNITE-12840:
Summary: Leaking H2 internals when querying from pyignite
Key: IGNITE-12840
URL: https://issues.apache.org/jira/browse/IGNITE-12840
Project: Ignite
I
I'm currently working on ticket
https://issues.apache.org/jira/browse/IGNITE-12832
It's not exactly what had been suggested but it will allow to pass some
custom properties to the client configuration and to pass parameters without
length limitations using .properties file.
--
Sent from: http:/
Nikolay Izhikov created IGNITE-12841:
Summary: @Override must be on the same line as a method
Key: IGNITE-12841
URL: https://issues.apache.org/jira/browse/IGNITE-12841
Project: Ignite
Iss
Hello, Igniters.
Right now there is no way for the user to set fetchSize of the JdbcStore
This leads to the poor performance of the cache load with the 3-d party
persistence [1]
I propose to add JdbcDialect#setFetchSize method [2]
Thoughts?
[1] https://issues.apache.org/jira/browse/IGNITE-1282
Denis,
I'll review your PR. If this issue is a subject to be included in 2.8.1 in
emergency mode, I'm ok with the current API changes.
Please think about driving creating IEP on security API overhaul prior to
2.9. I believe that you are the most suitable Ignite community member to
drive this activ
> will try to provide such guarantees on the server-side
Thanks. I think it is better to do once in the server code than N times in
every client.
On Wed, Mar 25, 2020 at 11:04 PM Alex Plehanov
wrote:
> Pavel,
>
> 1. Actually it can be solved on the client-side (and already solved in PoC
> implem
Hi Nikolay,
There is a very similar ticket [1]. Perhaps it could be somehow useful.
[1] https://issues.apache.org/jira/browse/IGNITE-11894
Best regards,
Ivan Pavlukhin
чт, 26 мар. 2020 г. в 17:54, Nikolay Izhikov :
>
> Hello, Igniters.
>
> Right now there is no way for the user to set fetchSize
Hello, Ivan.
Yes, this is the same issue.
I will proceed with this improvement if there is no objections.
чт, 26 мар. 2020 г., 19:40 Ivan Pavlukhin :
> Hi Nikolay,
>
> There is a very similar ticket [1]. Perhaps it could be somehow useful.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-118
>
> Deployment API definitely needed as one of the next steps. Currently, we
> are talking only about the first step (execution of already deployed
> tasks).
> Also, I'm not sure about automatic redeploy and peer-class-loading for thin
> clients, I think it's better to have more control here and pr
Good Afternoon All
I was asked to forward this here by Denis Magda. I see in the 2.8 release that
you implemented importing of XGBoost models for distributed inference =>
https://issues.apache.org/jira/browse/IGNITE-10810?focusedCommentId=16728718&page=com.atlassian.jira.plugin.system.issuetabpa
Hi Adam, thanks for starting the thread. The contributions are
highly appreciated and we'll be glad to see you among our contributors,
especially, if it helps to make our ML library stronger.
But first things first, let me introduce you to @Alexey Zinoviev
who is our main ML maintainer.
-
Denis
Good afternoon Denis,
Nice to meet you, Hello to you too Alexey. So I'm not sure if it will be me or
another member on our team, but I wanted to start the discussion. We are
investigating/integrating ignite into our ML platform. In addition We have
already done a separate tensor flow implemen
Sunny Chan created IGNITE-12842:
---
Summary: Cache "IGNITE_DAEMON" system properties in isDaemon call
Key: IGNITE-12842
URL: https://issues.apache.org/jira/browse/IGNITE-12842
Project: Ignite
Iss
Hello,
I was performing some tuning using JFR with our application, and I have found
that in many of the cache get it makes a lot of calls to get System Properties,
which is a synchronized call. Upon further examination of the code I have found
that we can potentially optimized the code to cach
Morning, Adam, Denis!
Let me describe the current status
1. https://issues.apache.org/jira/browse/IGNITE-10810 is related to MLeap
not to XGBoost. This is the right ticket for XGBoost
https://issues.apache.org/jira/browse/IGNITE-10289
2. Currently, we have no plans to add XGBoost or any external
17 matches
Mail list logo