Nikolay, thanks for joining the discussion.
Please give me a few days to respond and create tickets. A bit hectic week.
-
Denis
On Sat, Apr 18, 2020 at 6:10 AM Nikolay Izhikov wrote:
> > 1. Add ability to enable\disable subset of the metrics for collection:
> >
Igniters,
Here is a draft of our very first roadmap. I decided to make it damp simple
but descriptive:
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
What we need to do next is to:
- Fill in the "Readiness Estimated Time" column with your best guess of
when an
Hello Johnny,
Added you to contributors group in JIRA.
Welcome to Ignite community!
Pavel
On Wed, Apr 22, 2020 at 7:58 PM Johnny Galatikitis <
johnny.galatiki...@gmail.com> wrote:
> Hello,
>
> I am working on IGNITE-12905 and forgot to ask for contributors
> permissions.
>
> regards, J.
>
Hello,
I am working on IGNITE-12905 and forgot to ask for contributors
permissions.
regards, J.
Ok, thanks for the clarification.
I retract my "-1": no strong objections.
On Wed, Apr 22, 2020 at 3:15 PM Dmitriy Pavlov wrote:
> Hi Folks,
>
> There is nothing wrong with releasing system by it's modules, one-by-one.
> Also it is perfectly OK to have each module in a separate git repo. Each
Ilya Kasnacheev created IGNITE-12934:
Summary: Change test start|stop log format for correct TC and
build.log visibility.
Key: IGNITE-12934
URL: https://issues.apache.org/jira/browse/IGNITE-12934
Aleksey Plekhanov created IGNITE-12933:
--
Summary: Node failed after put incorrect key class for indexed
type to transactional cache
Key: IGNITE-12933
URL: https://issues.apache.org/jira/browse/IGNITE-12933
Folks, could you please take a look at this issue?
It seems quite serious if we can potentially get B+Tree corrupted.
Sincerely,
Dmitriy Pavlov
пт, 17 апр. 2020 г. в 19:25, Alexander Korenshteyn (Jira) :
> Alexander Korenshteyn created IGNITE-12911:
>
Hi Folks,
There is nothing wrong with releasing system by it's modules, one-by-one.
Also it is perfectly OK to have each module in a separate git repo. Each of
these module release-candidate is voted separately. At the foundation
level, release cycle of the project/modules is not defined, it is
Pavel,
1. We can conduct separate votes for every client, do you see any issues
here?
2. This is true, but we have backward compatibility in our protocol, so
everything
should work just fine.
Best Regards,
Igor
On Tue, Apr 21, 2020 at 9:22 PM Pavel Tupitsyn wrote:
> -1
>
> - Ignite is a
Hello, Ivan.
I think we can include this improvements.
Please, go ahead.
> 22 апр. 2020 г., в 10:21, Ivan Bessonov написал(а):
>
> Hi Igniters,
>
> I'm continuing with IGNITE-12756 PR creation. It turned out that we need 3
> more cherry-picks
> to avoid massive code changes. Tests started
Pavel Tupitsyn created IGNITE-12932:
---
Summary: Thin client cluster discovery
Key: IGNITE-12932
URL: https://issues.apache.org/jira/browse/IGNITE-12932
Project: Ignite
Issue Type: New
icode created IGNITE-12931:
--
Summary: General error: "java.lang.ArrayIndexOutOfBound
Key: IGNITE-12931
URL: https://issues.apache.org/jira/browse/IGNITE-12931
Project: Ignite
Issue Type: Bug
Thank you for your response, Konstantin
I think we cannot just turn this optimization
>
Of course not, that is the reason why I started this thread.
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table don't change
> it neither on remove or update
Yes, but we can increment this
Hi Igniters,
I'm continuing with IGNITE-12756 PR creation. It turned out that we need 3
more cherry-picks
to avoid massive code changes. Tests started failing after my initial
attempt to create that PR.
So, in total I have PR with 6 commits in it. Some of them fix components
and tests for them,
Hello, Ivan
I think we cannot just turn this optimization on because a result invalidation
counts on org.h2.engine.Database#modificationDataId (see
org.h2.command.dml.Query#sameResultAsLast(Session, Value[], Value[], long)),
but org.apache.ignite.internal.processors.query.h2.opt.GridH2Table
16 matches
Mail list logo
