Sergei Ryzhov created IGNITE-13153:
--
Summary: Fix CammandHandler user Attributes
Key: IGNITE-13153
URL: https://issues.apache.org/jira/browse/IGNITE-13153
Project: Ignite
Issue Type: Task
Hello, Igniters!
I'd like to get a review of the ticket [1]. The patch is ready [2].
Can someone look at it, please?
[1] https://issues.apache.org/jira/browse/IGNITE-13144
[2] https://github.com/apache/ignite/pull/7924
--
BR, Sergey Antonov
Taras Ledkov created IGNITE-13154:
-
Summary: Introduce aility to manage manage binary types by the
users
Key: IGNITE-13154
URL: https://issues.apache.org/jira/browse/IGNITE-13154
Project: Ignite
Hello, Maxim.
Thank you for so detailed explanation.
Can we put the content of this discussion somewhere on the wiki?
So It doesn’t get lost.
I divide the answer in several parts. From the requirements to the
implementation.
So, if we agreed on the requirements we can proceed with the discussio
Maxim Muzafarov created IGNITE-13155:
Summary: Snapshot creation throws NPE on an in-memory cluster
Key: IGNITE-13155
URL: https://issues.apache.org/jira/browse/IGNITE-13155
Project: Ignite
Hi, Igniters!
I'm going to provide ML model export/import in human-readable format like
JSON.
But I have an issue: what JSON ser/deser library to use:
- I don't want to add dependency with possible CVEs
- I don't need in special annotations to mark the POJO objects or
something similar
Ivan Bessonov created IGNITE-13156:
--
Summary: Continuous query filter deployment hungs discovery thread
Key: IGNITE-13156
URL: https://issues.apache.org/jira/browse/IGNITE-13156
Project: Ignite
Hello!
Our REST Jetty code uses jackson databind.
I think it is a safe bet since most users will have it in classpath anyway,
since they use our REST.
If there are any CVEs we have a lot of pressure to fix it, which will also
fix ML export.
Regards,
--
Ilya Kasnacheev
вт, 16 июн. 2020 г. в 15
Hi,
I created new issue that describes CQ problem in more details: [1]
I'm fine with experimental status and new property naming.
[1] https://issues.apache.org/jira/browse/IGNITE-13156
вт, 16 июн. 2020 г. в 02:20, Valentin Kulichenko <
valentin.kuliche...@gmail.com>:
> Folks,
>
> Thanks for pro
Val,
I like your suggestion about naming, it describes the purpose of the
configuration the best.
On Tue, Jun 16, 2020 at 5:18 PM Ivan Bessonov wrote:
> Hi,
>
> I created new issue that describes CQ problem in more details: [1]
> I'm fine with experimental status and new property naming.
>
> [1
Sergey, Ivan,
Could you please check the questions below? If it's time-consuming to
rework continuous queries, then the new mode can become available in the
experimental state and should not let register continuous queries to avoid
potential deadlocks. Overall, this design gap in continuous querie
Hi Everyone,
We released a new monitoring and management tool this month for Apache
Ignite and GridGain applications; GridGain Control Center. There is a
webinar schedule for tomorrow, JUNE 17 2020 10:00AM PDT (-07:00), where I
will provide an overview of the features and demo different use cases.
Mauricio Stekl created IGNITE-13157:
---
Summary: Upgrade build process for Javadocs
Key: IGNITE-13157
URL: https://issues.apache.org/jira/browse/IGNITE-13157
Project: Ignite
Issue Type: Impro
13 matches
Mail list logo