> merge to master only fully finished features
It's already true for Ignite master branch.
В Вт, 24/09/2019 в 09:03 +0300, Alexey Zinoviev пишет:
> The planned before 2_3 months release dates are good defender from
> partially merged features, In my opinion
>
> Or we should have Master and dev
The planned before 2_3 months release dates are good defender from
partially merged features, In my opinion
Or we should have Master and dev branch separetely, and merge to master
only fully finished features
пн, 23 сент. 2019 г., 20:27 Maxim Muzafarov :
> Andrey,
>
> Agree with you. It can affe
Hi,
I have pushed PR: 6899, and I hope the community will merge as soon as
possible.
在 2019/9/23 下午5:37, Nikolay Izhikov 写道:
Hello, liyuj
Thanks for your interest in Igniter.
Feel free to assign ticket to yourself.
Looking forward for your contribution!
В Сб, 21/09/2019 в 19:31 +0800, liyu
Jesus H created IGNITE-1:
Summary: Lacking Ignite C++ functionality or examples to store
byte arrays
Key: IGNITE-1
URL: https://issues.apache.org/jira/browse/IGNITE-1
Project: Ignite
Mariya,
Please subscribe to the user list by sending an email to
user-subscr...@ignite.apache.org and forward the question there in English
afterwards.
-
Denis
On Mon, Sep 23, 2019 at 4:44 PM Мария Помазкина
wrote:
> Здравствуйте!
> Я пытаюсь ограничить количество записей, получаемых из игнай
Здравствуйте!
Я пытаюсь ограничить количество записей, получаемых из игнайта.
https://apacheignite.readme.io/docs/cache-queries#section-query
Здесь сказано, что данные будут приходить страницами и можно
установить размер страницы. Тем не менее дальше по тексту примеры кода
указывают на то, что
Outstanding! Let's brag about this publicly :)
https://twitter.com/ApacheIgnite/status/1176280416627486720?s=20
-
Denis
On Mon, Sep 23, 2019 at 3:08 AM Nikolay Izhikov wrote:
> Hello, Team.
>
>
> System view engine is merged to the master.
>
> Thanks, everyone for the feeback and help with it!
Nikolay Izhikov created IGNITE-12221:
Summary: Javadoc generation fail
Key: IGNITE-12221
URL: https://issues.apache.org/jira/browse/IGNITE-12221
Project: Ignite
Issue Type: Sub-task
Andrey,
Agree with you. It can affect the user impression.
Can you advise, how can we guarantee in our case when we complete with
current partially merged features that someone will not partially
merge the new one? Should we monitor the master branch commits for
such purpose?
On Mon, 23 Sep 2019
Maxim,
>> From my point, if some components will not be ready by
>> previously discussed `scope freeze` date it is absolutely OK to
>> perform the next (e.g. 2.8.1, 2.8.2) releases.
It is good approach if partial implemented features aren't merged to
master branch. Unfortunately this is not our c
Got it.
Agree with you.
I think we can finish almost all of this tickets till November.
В Пн, 23/09/2019 в 20:12 +0300, Andrey Gura пишет:
> > > From my point of view monitoring isn't ready for release.
> > Can you clarify, what exactly is not ready?
> > Can we track planned changes somehow?
>
>> From my point of view monitoring isn't ready for release.
> Can you clarify, what exactly is not ready?
> Can we track planned changes somehow?
We have too many not resolved tickets under IEP-35 label [1]. Also it
makes sense to do some usability testing: JMX beans interfaces, system
views, et
Andrey Kuznetsov created IGNITE-12220:
-
Summary: Allow to use cache-related permissions both at system and
per-cache levels
Key: IGNITE-12220
URL: https://issues.apache.org/jira/browse/IGNITE-12220
Folks,
The new thread with 2.8 RELEASE discussion has been scheduled.
http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-8-RELEASE-Time-Scope-Manager-td43616.html
On Thu, 19 Sep 2019 at 20:24, Alexey Zinoviev wrote:
>
> Please post the link to this thread when you'll create
Folks,
Ok, let's have a discussion using the ASF Slack on September 25-th, 17-00 (MSK)
I've created the channel [1] #ignite-release-2_8
Please, join.
I don't think we should postpone the discussion by November but should
plan and discuss for now the next release dates. In this way, the
community
Hello, Andrey.
> From my point of view monitoring isn't ready for release.
Can you clarify, what exactly is not ready?
Can we track planned changes somehow?
В Пн, 23/09/2019 в 17:59 +0300, Andrey Gura пишет:
> Igniters,
>
> From my point of view monitoring isn't ready for release. So it would
Igniters,
>From my point of view monitoring isn't ready for release. So it would
be great to return to this discussion later. It seems that beginning
of November is good time for it.
On Mon, Sep 23, 2019 at 5:37 PM Alexey Zinoviev wrote:
>
> Nikolay Izhikov, ok, let's arrange the talk in ASF sla
Nikolay Izhikov, ok, let's arrange the talk in ASF slack between 16 and 19
MSK, is it possible?
пн, 23 сент. 2019 г. в 17:35, Alexey Zinoviev :
> Ok, I'll clarify the situation
>
> 1. Currently, the ML module is like a black box for me. What exactly
> we are expected to get by the code freeze dat
Ok, I'll clarify the situation
1. Currently, the ML module is like a black box for me. What exactly
we are expected to get by the code freeze date? Do we have tickets we
should address to?
- Yes, we have a few epics that are not finished yet, due to limited free
time the planned dates were writte
Hello, Nikita.
> A node creates the ChangeMasterKeyMessage message and sent it by discovery as
> a custom event.
> The goal is to verify that all nodes have the same master key.
...
> The ChangeMasterKeyFinishMessage action message is sent by discovery as a
> custom event.
> New master key id.
Nikolay Izhikov created IGNITE-12219:
Summary: Cache operations histogram
Key: IGNITE-12219
URL: https://issues.apache.org/jira/browse/IGNITE-12219
Project: Ignite
Issue Type: Improvement
+1 to start releasing 2.8 in November or even in the end of October.
Alex, can we schedule some quick meetings in the new Ignite Slack chat and
discuss all release date details?
Wendseday, 25 September is good for you?
В Пн, 23/09/2019 в 13:31 +0300, Maxim Muzafarov пишет:
> Alexey,
>
> Can yo
Alexey,
Can you, please, clarify some questions.
1. Currently, the ML module is like a black box for me. What exactly
we are expected to get by the code freeze date? Do we have tickets we
should address to?
2. I think we can move code freeze date to December 11-th but, from
your side, do you thi
Aleksey Zinoviev created IGNITE-12218:
-
Summary: [ML] Add support for Strings in Vectorizer
Key: IGNITE-12218
URL: https://issues.apache.org/jira/browse/IGNITE-12218
Project: Ignite
Issu
Aleksey Zinoviev created IGNITE-12217:
-
Summary: [ML] Add support for label encoding
Key: IGNITE-12217
URL: https://issues.apache.org/jira/browse/IGNITE-12217
Project: Ignite
Issue Type:
Aleksey Zinoviev created IGNITE-12216:
-
Summary: [ML][Umbrella]
Key: IGNITE-12216
URL: https://issues.apache.org/jira/browse/IGNITE-12216
Project: Ignite
Issue Type: New Feature
Hello, Team.
System view engine is merged to the master.
Thanks, everyone for the feeback and help with it!
Alex Plekhanov, Andrey Gura, Vyacheslav Daradur, Alex Gonchruk you feed back
helps a lot!
But, Monitoring & Profiling. Phase 2 continues.
I will contribute system views for almost all in
Hello, liyuj
Thanks for your interest in Igniter.
Feel free to assign ticket to yourself.
Looking forward for your contribution!
В Сб, 21/09/2019 в 19:31 +0800, liyuj пишет:
> Hi community,
>
> The issue is relatively simple, and I can contribute.
> Can someone assign this to me? My JIRA ID is
Rick Vincent created IGNITE-12215:
-
Summary: Data region LRU offheap algo not working causes eventual
memory crash
Key: IGNITE-12215
URL: https://issues.apache.org/jira/browse/IGNITE-12215
Project: Ig
29 matches
Mail list logo
