Stanilovsky Evgeny created IGNITE-12277:
---
Summary: Index usage is not applicable for mixed IN and EQUALS
queries.
Key: IGNITE-12277
URL: https://issues.apache.org/jira/browse/IGNITE-12277
Igniters,
Who can advise what we can\should do with the issues related to
`documentation` component to release Ignite 2.8 version?
How can I sort them and prioritize?
What are best-practices here?
Currently, we have 81 issues pinned to 2.8 release [1].
6 - `In Progress`
2 - `Patch Available`
Hello, Mikhail.
I will take a look, shortly.
В Чт, 10/10/2019 в 16:08 +0300, Mikhail Petrov пишет:
> Hello, Igniters.
>
> My project demands extended logic of Apache Ignite REST processor. I'd
> like to implement a specific one and use it with Apache Ignite, but now
> it's impossible. I have
Issues link is broken, because it has a filter that can't be found.
Here is correct link:
Hello, Igniters.
My project demands extended logic of Apache Ignite REST processor. I'd
like to implement a specific one and use it with Apache Ignite, but now
it's impossible. I have created Ticket [1] and PR [2] to provide an
ability to configure custom REST processor implementation via
Hello!
I think that Documentation tickets may be safely postponed until final
stages of release, since it's not included in artifacts, rather available
on readme.io, etc.
Regards,
--
Ilya Kasnacheev
чт, 10 окт. 2019 г. в 14:41, Pavel Kovalenko :
> Issues link is broken, because it has a
Ivan Rakov created IGNITE-12278:
---
Summary: Add metric showing how many nodes may safely leave the
cluster wihout partition loss
Key: IGNITE-12278
URL: https://issues.apache.org/jira/browse/IGNITE-12278
Michal created IGNITE-12279:
---
Summary: Add support for using H2O MOJO models for inference
Key: IGNITE-12279
URL: https://issues.apache.org/jira/browse/IGNITE-12279
Project: Ignite
Issue Type: New
https://issues.apache.org/jira/browse/IGNITE-12278
Best Regards,
Ivan Rakov
On 07.10.2019 15:08, Ivan Rakov wrote:
Denis, Alex,
Sure, new metric will be integrated into new metrics framework.
Let's not expose its value to control.sh right now. I'll create an
issue for aggregated
Hello everyone,
I started using Ignite lately. Part of my work involves Pub/Sub, thus I
created a pub/sub streamer.
Pub/Sub is pretty close to Kafka.
Here's how the streamer works. Every node creates an instance of a Pub/Sub
client.
The clients subscribe to the same topic using the same
Hello Thibaut,
If IGNITE-12236 and IGNITE-12259 solve your problem, then it's totally fine
to get them merged.
Maxim, looks like you are already reviewing one of the tickets. Could you
please double-check two tickets holistically and merge them in case of no
concerns?
-
Denis
On Wed, Oct 9,
Sam created IGNITE-12280:
Summary: Removal of this limitation "It's not recommended to have
class hierarchies with raw reading/writing"
Key: IGNITE-12280
URL: https://issues.apache.org/jira/browse/IGNITE-12280
Alexey
I'm ok for the suggested way in [1]
1. https://issues.apache.org/jira/browse/IGNITE-12263
On Tue, Oct 8, 2019 at 9:59 PM Denis Magda wrote:
> Anton,
>
> Seems like we have a name for the defragmentation mode with a downtime -
> Rolling Defrag )
>
> -
> Denis
>
>
> On Mon, Oct 7, 2019
Hi igniters!
For last two years I've been organizing Ignite online and offline events
for Russia. Now I would like to offer my help with global community growth
activities: events, working with blog authors, cross-promotion with other
communities etc.
Could you share access to AI twitter, so I
Kseniya, welcome to the community and thanks for offering the help with
these activities. Most of us are focused on the code over community
+ awareness, and that's great to have you among those who can dedicate
more time for community growth and Ignite/ASF promotion.
Let me also introduce you to
ROHIT SANGWAN created IGNITE-12281:
--
Summary: Data search from Ignite Cache value object
Key: IGNITE-12281
URL: https://issues.apache.org/jira/browse/IGNITE-12281
Project: Ignite
Issue
16 matches
Mail list logo
