Anton Kalashnikov created IGNITE-11377:
--
Summary: Display time to baseline auto-adjust event in console.sh
Key: IGNITE-11377
URL: https://issues.apache.org/jira/browse/IGNITE-11377
Project:
Ilya Borisov created IGNITE-11376:
-
Summary: Web console: frontend cold build speed improvements
Key: IGNITE-11376
URL: https://issues.apache.org/jira/browse/IGNITE-11376
Project: Ignite
Vasiliy Sisko created IGNITE-11375:
--
Summary: Web console: Show appropriate message in no data
component when demo is disabled on agent
Key: IGNITE-11375
URL: https://issues.apache.org/jira/browse/IGNITE-11375
Ilya Borisov created IGNITE-11374:
-
Summary: Web console: fix frontend audit issues
Key: IGNITE-11374
URL: https://issues.apache.org/jira/browse/IGNITE-11374
Project: Ignite
Issue Type:
Evgenii Zhuravlev created IGNITE-11373:
--
Summary: varchar_ignorecase doesn't work properly
Key: IGNITE-11373
URL: https://issues.apache.org/jira/browse/IGNITE-11373
Project: Ignite
Hi Ankit,
could you please share your JIRA username?
Sincerely,
Dmitriy Pavlov
ср, 20 февр. 2019 г. в 05:55, ankit singh :
> Hi,
>
> As newbie committer to apache ignite, I would like to start with following
> jiras
>
> IGNITE-11230
> IGNITE-11131
Done, please check access now.
ср, 20 февр. 2019 г. в 21:49, Ivan Fedotov :
> Dmitriy, thank you for the response.
>
> My wiki username is "ivanan", the related mailbox is ivanan...@gmail.com.
>
> ср, 20 февр. 2019 г. в 18:38, Dmitriy Pavlov :
>
> > Hi Ivan,
> >
> > Now admin service is
Dmitriy, thank you for the response.
My wiki username is "ivanan", the related mailbox is ivanan...@gmail.com.
ср, 20 февр. 2019 г. в 18:38, Dmitriy Pavlov :
> Hi Ivan,
>
> Now admin service is unavailable (gives error 503). I'll add rights once it
> is up and running.
>
> Could you share your
Hi Ivan,
Now admin service is unavailable (gives error 503). I'll add rights once it
is up and running.
Could you share your wiki username? I can't find any users who signed up in
the wiki with any similar email/username
Sincerely,
Dmitriy Pavlov
ср, 20 февр. 2019 г. в 18:26, Ivan Fedotov :
>
Alexey Platonov created IGNITE-11372:
Summary: [ML] Fix javadoc in VectorWithDistributionId
Key: IGNITE-11372
URL: https://issues.apache.org/jira/browse/IGNITE-11372
Project: Ignite
Hi, Igniters.
I am planning to formalize migration to JUnit5 and create IEP which will
include related issues.
I already started to work on one of the issues [1] and created a draft for
the corresponding IEP [2].
Please, give me rights for confluence to create IEP.
[1]
Denis Mekhanikov created IGNITE-11371:
-
Summary: Cache get operation with readThrough returns null if
remove is performed concurrently
Key: IGNITE-11371
URL: https://issues.apache.org/jira/browse/IGNITE-11371
Fixed that.
> On 20 Feb 2019, at 14:50, Stepan Pilschikov wrote:
>
> Denis, Dmitry
>
> Found that https://issues.apache.org/jira/browse/IGNITE-9922
> Release process just do not copy this folder
> And this directory do not copy because of Dmitry concerns described earlier
>
> Agreed with
Hi, this ticket is already assigned, so you can contact the contributor if
he wants to proceed with fix or not.
ср, 20 февр. 2019 г. в 16:08, ankit singh :
> Hi,
> As newbie to Apache ingnite Dev, I would like to work on following jira.
>
> IGNITE-11369
>
Just a reminder: Veto is valid with justification. I see no reasons either
(need some time to dive into details), but it is not a reason for a veto.
ср, 20 февр. 2019 г. в 16:39, Anton Vinogradov :
> Dmitriy,
>
> Please stop chilling community :)
> No one makes final decisions here.
> Please
Dmitriy,
Please stop chilling community :)
No one makes final decisions here.
Please make sure you've got my position before chilling :)
I see no arguments to replace one solution with another.
In case no real reasons will be provided this merge will gain my Veto, just
a warning...
On Wed, Feb
Dmitriy,
> So I suggest chilling a couple of days without any discussion.
Why you trying to stop regular, positive dev-list discussion?
I think, we should have a strong reason to throw away some subsystem and
completely rewrite it.
We will damage product robustness with it.
>> 1. Automatic
Hi, please do not rush to make any final decision. I think we all need some
time to think about these 2 solutions.
So I suggest chilling a couple of days without any discussion.
Later we can come back to this topic and dive into it once again, maybe we
can merge it into one taking the best parts
Hi,
As newbie to Apache ingnite Dev, I would like to work on following jira.
IGNITE-11369
>> 1. Automatic tests scaling for new versions.
>> 2. Automatic dependency management.
Let's just improve the current solution.
See no problems here.
You'll have my *Veto* on merge without real reasons to replace solution
instead of improvement.
On Wed, Feb 20, 2019 at 3:55 PM Pavel Kovalenko
Anton,
In my first message, I already noticed the usability problems of the
current framework and showed how they can be solved using the new framework.
It gives us 2 major advantages:
1. Automatic tests scaling for new versions.
2. Automatic dependency management.
Described approach simplifies
Taras Ledkov created IGNITE-11370:
-
Summary: Doc: remove SqlQuery documentation
Key: IGNITE-11370
URL: https://issues.apache.org/jira/browse/IGNITE-11370
Project: Ignite
Issue Type: Task
Taras Ledkov created IGNITE-11369:
-
Summary: Remove H2 console form documentation
Key: IGNITE-11369
URL: https://issues.apache.org/jira/browse/IGNITE-11369
Project: Ignite
Issue Type: Task
Yury Gerzhedovich created IGNITE-11368:
--
Summary: use the same information about indexes for ODBC JDBC
drivers as for system view INDEXES
Key: IGNITE-11368
URL:
Hi Igniters,
Grid NIO server experts review needed for issue
https://issues.apache.org/jira/browse/IGNITE-11299
It is an issue for Ignite to be run under Java 11 & Windows.
Sincerely,
Dmitriy Pavlov
Denis, Dmitry
Found that https://issues.apache.org/jira/browse/IGNITE-9922
Release process just do not copy this folder
And this directory do not copy because of Dmitry concerns described earlier
Agreed with Denis that examples folder should be in release build because
of:
- they really help to
Ivan Rakov created IGNITE-11367:
---
Summary: Fix several issues in PageMemoryTracker
Key: IGNITE-11367
URL: https://issues.apache.org/jira/browse/IGNITE-11367
Project: Ignite
Issue Type: Bug
Stepan Pilschikov created IGNITE-11366:
--
Summary: python thin client: add python examples in release build
Key: IGNITE-11366
URL: https://issues.apache.org/jira/browse/IGNITE-11366
Project:
Stanislav Lukyanov created IGNITE-11365:
---
Summary: Partition sizes differ after streaming with
allowOverwrite=false with concurrent PME
Key: IGNITE-11365
URL:
Ivan Daschinskiy created IGNITE-11364:
-
Summary: Segmenting node can cause ring topology broke
Key: IGNITE-11364
URL: https://issues.apache.org/jira/browse/IGNITE-11364
Project: Ignite
Hello, Pavel.
Please, clarify.
What exactly your new compatibility framework should check?
I know at lease 2 compatible subsystem in Ignite that should work with
previous versions:
1. Persistence.
2. Thin client.
> A new version of Ignite has released and a developer should update
Hello, Denis.
> This XML may contain task descriptors, but I couldn't find any
documentation on this format.
> This information can be provided in simple JAR files with the same file
structure.
I support you proposal. Let's:
1. Support jar files instead of gar.
2. Write down documentation about
Sergey Kozlov created IGNITE-11363:
--
Summary: Document replicated cache performance degradation.
Key: IGNITE-11363
URL: https://issues.apache.org/jira/browse/IGNITE-11363
Project: Ignite
Igor,
Thank you! It helped. I adapted my code to the new protocol, so my
tests are passing.
On Tue, 2019-02-19 at 13:22 +0300, Igor Sapego wrote:
> This is my branch. I fixed an issue so re-merge and check if it
> helps.
>
> Best Regards,
> Igor
>
>
> On Tue, Feb 19, 2019 at 8:14 AM Dmitry
Denis,
This XML may contain task descriptors, but I couldn't find any
documentation on this format.
Also it may contain a userVersion [1] parameter, which can be used to force
tasks redeployment in some cases.
This information can be provided in simple JAR files with the same file
structure.
Vyacheslav,
Thank you for answers!
>> I'm not sure what is a problem here?
At the moment it's a little bit hard to understand the impact of such a
change because the number of test suites is small.
Let's Imagine you have X compatibility test suites where X is a relatively
big number, let's say
Fully agree with Slava,
Pavel, please share your vision of compatibility framework (current and
desired).
It really looks like you don't love current just because you can't
understand how to use it properly.
But this should not mean we have to remove the current, we should
Ivan Bessonov created IGNITE-11362:
--
Summary: New protocol version is absent in baseline autoadjustment
visor args
Key: IGNITE-11362
URL: https://issues.apache.org/jira/browse/IGNITE-11362
Project:
38 matches
Mail list logo
