вт, 6 июл. 2021 г. в 15:57, ткаленко кирилл :
> >> Can you clarify what it means to rename root index trees ?
> Replacing
> org.apache.ignite.internal.processors.cache.persistence.IndexStorageImpl.IndexItem,
> changing IndexItem#idxName, but keeping fIndexItem#pageId.
>
Changing to what ? Some te
Hi.
It's ok to have MOVING partitions in the described scenario, because the
second node is started after the first and starts a rebalancing on the next
topology version.
But it shouldn't break query consistency, because reading from the MOVING
partition is not allowed.
Why does it happen for te
Hello!
Nabble is an external resource and we do not have much say in how it works.
I recommend using Apache's Pony Mail:
https://lists.apache.org/list.html?dev@ignite.apache.org
While not without drawbacks, it is overall an useful tool.
Regards,
--
Ilya Kasnacheev
ср, 7 июл. 2021 г. в 04:36
Thanks everyone, I've moved the proposal to Active status.
Working on the implementation.
On Tue, Jul 6, 2021 at 10:31 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> The proposal looks good to me.
>
> -Val
>
> On Tue, Jul 6, 2021 at 2:24 AM Ivan Daschinsky
> wrote:
>
> > I supp
Igniters,
I have a few questions regarding server node startup and thin clients.
State of things:
- Server nodes will be started with 'ignite run' from CLI [1]
- ignite-api module represents our public API
- ignite-api has Ignition interface to start server nodes
Questions:
- What's the idea beh
I'll try to explain:
We create indexes through InlineIndexFactory#createIndex, where at the
beginning we create the root page using QueryIndexDefinition#treeName, so if we
create the same index 2 times, then we will refer to the same root.
In order to make the deletion of the index independent,
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*Test with high flaky rate in master
ZookeeperDiscoveryConcurrentStartAndStartStopTest.testMultipleClusters
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&test
Hi Pavel,
I don't think we will need the pure embedded mode, but we still need to be
able to access the API from compute and services. That said, there are two
usages of the 'Ignite' API:
1. Remote, via the binary protocol.
2. Local - needed for compute and services. (This is how it works n
A side note. Actually “Ignition” naming always confused me. I think about it as
some fancy named API entry point for Ignite. Perhaps it is a good moment to
revisit naming.
> On 8 Jul 2021, at 07:09, Valentin Kulichenko
> wrote:
>
> Hi Pavel,
>
> I don't think we will need the pure embedded m
Hi Ivan,
Ignition IS the entry point to Ignite, so I'm not sure I got your point :)
Where is the contradiction?
Either way, please feel free to give your suggestions for an alternative
name if you have any.
-Val
On Wed, Jul 7, 2021 at 7:56 PM Ivan Pavlukhina wrote:
> A side note. Actually “Ig
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New Critical Failure in master Cache (Restarts) 1
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CacheRestarts1?branch=%3Cdefault%3E
No changes in the build
Val,
So the plan is:
- Remove Ignition#start from the public API
- Make Ignition a class, not an interface
- Add static Ignition#startClient
Sounds good?
On Thu, Jul 8, 2021 at 6:13 AM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Hi Ivan,
>
> Ignition IS the entry point to Ign
12 matches
Mail list logo
