Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to
Hi Ilya,
> Frankly speaking, I do not see the value of having an extra layer of
> indirection around *local* Quartz-based scheduler in Ignite. Can you
> elaborate?
I didnt quite understand that. Are you referring to the
IgniteCombinedSchedulerProcessor?
>
> Our guidelines also recommend having
Hello!
Frankly speaking, I do not see the value of having an extra layer of
indirection around *local* Quartz-based scheduler in Ignite. Can you
elaborate?
Our guidelines also recommend having issue description to document the whys
and hows, and not just issue title.
Regards,
--
Ilya
Andrey,
> Per-partition Lucene index looks simple to implement, but it may require
> per-partition SQL to make full-text search expressions work correctly
> within the SQL quiery.
I think that as long as we follow the map - reduce process that we
already do for other queries, we should be fine.
Hello,
I have raised a PR for the said JIRA:
https://github.com/apache/ignite/pull/9277
TC is green with the PR:
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_BuildApacheIgnite/6105253
Please help in reviewing.
Regards,
Atri
The Apache Ignite Community is pleased to announce the release of
Apache IGNITE python thin client (pyignite) 0.5.1.
This new release of python thin client contains bugfixes and a few new
features
Namely:
1. Event listeners to connection events and query events
2. Optional client's side handshake
Hello Igniters,
I would like to proceed with implementing the feedback service for the
Ignite documentation website.
If nobody objects, let's start the work.
The details are described here:
https://issues.apache.org/jira/browse/IGNITE-15198
With best regards,
Nikita
ср, 17 мар. 2021 г. в 15:50,
Nikita, thanks for releasing the artifacts.
Could you please update the following documentation section as well?
https://ignite.apache.org/docs/latest/extensions-and-integrations/spring/spring-data#maven-configuration
This is what worked for me:
1. Ignite Spring Data dependency
Hello, Igniters!
Release pyignite-0.5.1-rc0 has been accepted.
The votes received:
3 "+1" binding votes
1 "+1" votes
There are no "+0" or "-1"
Here the votes received:
- Igor Sapego (binding) +1
- Pavel Tupitsyn (binding) +1
- Nickolay Izhikov (binding) +1
- Ivan Daschinsky +1
Atri,
> We can have partition level indices on each node.
Per-partition Lucene index looks simple to implement, but it may require
per-partition SQL to make full-text search expressions work correctly
within the SQL quiery.
Per-partition SQL index may kill the performance. We already tried to do
Sorry, I planned on creating a Wiki page for this, but it makes more
sense to be replying here.
> * How Lucene index can be split among the nodes?
We can have partition level indices on each node.
> * If we'll have a single index for all partitions on the particular node,
> then how index
Hello!
Let me try to answer the questions below, since I did not see anybody do
that and thus not everybody may be on the same page.
Regards,
пт, 23 июл. 2021 г. в 13:56, Andrey Mashenkov :
> Atri,
>
> As for now, the potential capabilities are not clear to me.
> At first glance, I see the
+1 (binding)
> 26 июля 2021 г., в 21:11, Pavel Tupitsyn написал(а):
>
> +1
>
> On Mon, Jul 26, 2021 at 11:36 AM Igor Sapego wrote:
>
>> +1 from me
>>
>> Best Regards,
>> Igor
>>
>>
>> On Fri, Jul 23, 2021 at 3:32 PM Ivan Daschinsky
>> wrote:
>>
>>> +1 From me
>>> 1. Checked binary
14 matches
Mail list logo
