[DISCUSSION] Major changes in Ignite in 2020

[dmagda]

Dear Ignite community,

Many of us want to see where Ignite is heading and ask for some sort of a
2020 course/plan/roadmap and a predictable schedule of major releases.
Also, there are intentions to enhance some internal processes and
collaboration approaches.

Let's start moving in that direction by defining 3-5 major changes you
would like to contribute this year personally or will be glad to drive
(like processes changes) and work together with someone else. Dear, Ignite
user community, please share your suggestions as well.

Note, let's use this thread to collect major
topics/directions/features/changes. Just respond with your proposals. Don't
go into arguments if you don't agree with someone's opinions. Once the
topics are collected, we'll create a wiki page and, most likely, will start
working through specific items in focus groups and only then lay out a
cohesive plan with some dates.

-
Denis

[dmagda]

My top list of changes is as follows:

   - Feature: New lightweight Apache Ignite website with advanced search
   engine optimizations and updated technical content. Why? Much better
   discoverability of Ignite via search engines like Google to let many more
   application developers learn about Ignite existence. This change is to be
   brought to live soon:
   http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Website-New-Look-td46324.html


   - Feature: New Ignite documentation on a new platform and with a new
   structure. Why? Ignite documentation has to help new application developers
   to get up and running as quickly as possible, it also has to become a
   primary source that answers most of the questions. Our current docs have a
   lot of gaps: https://issues.apache.org/jira/browse/IGNITE-7595


   - Process Change: to be successful with the point above, documentation
   should be created/updated before we close a JIRA ticket for
   code/API/feature contribution. Why? First, application developers learn
   Ignite and create their Ignite-apps referring to API reference and
   technical documentation (and not to the source code), thus, documentation
   needs to be treated as an integral part of the whole project. Second, while
   writing a new documentation paragraph we could discover incompleteness of a
   fix/feature or usability issues before the change is released publicly.


   - Feature: complete the modularization project by defining the Ignite
   core that will be released separately from Ignite extensions. The 'why' is
   written here:
   https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization

-
Denis


On Thu, Mar 19, 2020 at 11:21 AM Denis Magda <[hidden email]> wrote:

> Dear Ignite community,
>
> Many of us want to see where Ignite is heading and ask for some sort of a
> 2020 course/plan/roadmap and a predictable schedule of major releases.
> Also, there are intentions to enhance some internal processes and
> collaboration approaches.
>
> Let's start moving in that direction by defining 3-5 major changes you
> would like to contribute this year personally or will be glad to drive
> (like processes changes) and work together with someone else. Dear, Ignite
> user community, please share your suggestions as well.
>
> Note, let's use this thread to collect major
> topics/directions/features/changes. Just respond with your proposals. Don't
> go into arguments if you don't agree with someone's opinions. Once the
> topics are collected, we'll create a wiki page and, most likely, will start
> working through specific items in focus groups and only then lay out a
> cohesive plan with some dates.
>
> -
> Denis
>

[Saikat Maitra]

Hi Denis,

Thank you for sharing the list of top changes. The list looks good.

I wanted to share that efforts regarding IEP-36 is already underway and
there are also open PRs under review and working through review feedback.
One of the area that we are focussing is first we will merge changes in
ignite-extensions repo before removing the specific migrated module from
ignite repo.

There are also contribution from community on bug fixes in
ignite-extensions repo as well which we are verifying and merging in
ignite-extensions repo after running through CI pipeline in teamcity.

I like the focus area on docs and I really like the Apache Ignite Usecases
page https://ignite.apache.org/provenusecases.html,  I would like to
suggest if we can add a page like powered by Apache Ignite and list few Org
who are already using Apache Ignite in prod.

Something similar to this page https://flink.apache.org/poweredby.html

Regards,
Saikat






On Thu, Mar 19, 2020 at 1:44 PM Denis Magda <[hidden email]> wrote:

> My top list of changes is as follows:
>
>    - Feature: New lightweight Apache Ignite website with advanced search
>    engine optimizations and updated technical content. Why? Much better
>    discoverability of Ignite via search engines like Google to let many more
>    application developers learn about Ignite existence. This change is to be
>    brought to live soon:
>    http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Website-New-Look-td46324.html
>
>
>    - Feature: New Ignite documentation on a new platform and with a new
>    structure. Why? Ignite documentation has to help new application developers
>    to get up and running as quickly as possible, it also has to become a
>    primary source that answers most of the questions. Our current docs have a
>    lot of gaps: https://issues.apache.org/jira/browse/IGNITE-7595
>
>
>    - Process Change: to be successful with the point above, documentation
>    should be created/updated before we close a JIRA ticket for
>    code/API/feature contribution. Why? First, application developers learn
>    Ignite and create their Ignite-apps referring to API reference and
>    technical documentation (and not to the source code), thus, documentation
>    needs to be treated as an integral part of the whole project. Second, while
>    writing a new documentation paragraph we could discover incompleteness of a
>    fix/feature or usability issues before the change is released publicly.
>
>
>    - Feature: complete the modularization project by defining the Ignite
>    core that will be released separately from Ignite extensions. The 'why' is
>    written here:
>    https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization
>
> -
> Denis
>
>
> On Thu, Mar 19, 2020 at 11:21 AM Denis Magda <[hidden email]> wrote:
>
>> Dear Ignite community,
>>
>> Many of us want to see where Ignite is heading and ask for some sort of a
>> 2020 course/plan/roadmap and a predictable schedule of major releases.
>> Also, there are intentions to enhance some internal processes and
>> collaboration approaches.
>>
>> Let's start moving in that direction by defining 3-5 major changes you
>> would like to contribute this year personally or will be glad to drive
>> (like processes changes) and work together with someone else. Dear, Ignite
>> user community, please share your suggestions as well.
>>
>> Note, let's use this thread to collect major
>> topics/directions/features/changes. Just respond with your proposals. Don't
>> go into arguments if you don't agree with someone's opinions. Once the
>> topics are collected, we'll create a wiki page and, most likely, will start
>> working through specific items in focus groups and only then lay out a
>> cohesive plan with some dates.
>>
>> -
>> Denis
>>
>

[Pavel Tupitsyn]

My top priorities:

   - Thin Client API extension: Compute, Continuous Queries, Services
   - .NET Near Cache: soon to come in Thick API, to be investigated for
   Thin Clients
   - .NET Modernization for Ignite 3.0: drop legacy .NET Framework support,
   target .NET Standard 2.0, add nullable annotations to the API


On Fri, Mar 20, 2020 at 5:23 AM Saikat Maitra <[hidden email]>
wrote:

> Hi Denis,
>
> Thank you for sharing the list of top changes. The list looks good.
>
> I wanted to share that efforts regarding IEP-36 is already underway and
> there are also open PRs under review and working through review feedback.
> One of the area that we are focussing is first we will merge changes in
> ignite-extensions repo before removing the specific migrated module from
> ignite repo.
>
> There are also contribution from community on bug fixes in
> ignite-extensions repo as well which we are verifying and merging in
> ignite-extensions repo after running through CI pipeline in teamcity.
>
> I like the focus area on docs and I really like the Apache Ignite Usecases
> page https://ignite.apache.org/provenusecases.html,  I would like to
> suggest if we can add a page like powered by Apache Ignite and list few Org
> who are already using Apache Ignite in prod.
>
> Something similar to this page https://flink.apache.org/poweredby.html
>
> Regards,
> Saikat
>
>
>
>
>
>
> On Thu, Mar 19, 2020 at 1:44 PM Denis Magda <[hidden email]> wrote:
>
>> My top list of changes is as follows:
>>
>>    - Feature: New lightweight Apache Ignite website with advanced search
>>    engine optimizations and updated technical content. Why? Much better
>>    discoverability of Ignite via search engines like Google to let many more
>>    application developers learn about Ignite existence. This change is to be
>>    brought to live soon:
>>    http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Website-New-Look-td46324.html
>>
>>
>>    - Feature: New Ignite documentation on a new platform and with a new
>>    structure. Why? Ignite documentation has to help new application developers
>>    to get up and running as quickly as possible, it also has to become a
>>    primary source that answers most of the questions. Our current docs have a
>>    lot of gaps: https://issues.apache.org/jira/browse/IGNITE-7595
>>
>>
>>    - Process Change: to be successful with the point above,
>>    documentation should be created/updated before we close a JIRA ticket for
>>    code/API/feature contribution. Why? First, application developers learn
>>    Ignite and create their Ignite-apps referring to API reference and
>>    technical documentation (and not to the source code), thus, documentation
>>    needs to be treated as an integral part of the whole project. Second, while
>>    writing a new documentation paragraph we could discover incompleteness of a
>>    fix/feature or usability issues before the change is released publicly.
>>
>>
>>    - Feature: complete the modularization project by defining the Ignite
>>    core that will be released separately from Ignite extensions. The 'why' is
>>    written here:
>>    https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization
>>
>> -
>> Denis
>>
>>
>> On Thu, Mar 19, 2020 at 11:21 AM Denis Magda <[hidden email]> wrote:
>>
>>> Dear Ignite community,
>>>
>>> Many of us want to see where Ignite is heading and ask for some sort of
>>> a 2020 course/plan/roadmap and a predictable schedule of major releases.
>>> Also, there are intentions to enhance some internal processes and
>>> collaboration approaches.
>>>
>>> Let's start moving in that direction by defining 3-5 major changes you
>>> would like to contribute this year personally or will be glad to drive
>>> (like processes changes) and work together with someone else. Dear, Ignite
>>> user community, please share your suggestions as well.
>>>
>>> Note, let's use this thread to collect major
>>> topics/directions/features/changes. Just respond with your proposals. Don't
>>> go into arguments if you don't agree with someone's opinions. Once the
>>> topics are collected, we'll create a wiki page and, most likely, will start
>>> working through specific items in focus groups and only then lay out a
>>> cohesive plan with some dates.
>>>
>>> -
>>> Denis
>>>
>>

[Ivan Rakov]

Hi everyone!

Major changes that are going to be contributed from our side:
- https://issues.apache.org/jira/browse/IGNITE-11704 - keeping tombstones
for removed entries to make rebalance consistent (this problem is solved by
on-heap deferred deletes queue so far).
- https://issues.apache.org/jira/browse/IGNITE-11147  - don't cancel
ongoing rebalance if affinity assignment for the rebalancing group wasn't
changed during the PME.
- Batch of other updates related to the historical rebalance. Goal is to
make historical rebalance stable and to ensure that if WAL history is
configured properly the cluster will be able to recover data consistency
via historical rebalance in case of any topology changes (including cycling
restart).
- Overhaul of partition loss handling. It has several flaws so far; the
most critical one is that by default (with PartitionLossPolicy.IGNORE)
Ignite may silently lose data. Also, (PartitionLossPolicy.IGNORE) is
totally inapplicable to scenarios when persistence is enabled and BLT is
established. Also, even safe policies have bugs: LOST state is reset when
node rejoins the cluster, so data actually can be lost even with safe
policy. We are going to set safe policy as default and fix related bugs.
- Distributed tracing (via OpenCensus). Discovery, communication and
transactions will be covered.

On Fri, Apr 10, 2020 at 11:43 AM Anton Kalashnikov <[hidden email]>
wrote:

> My top priorities:
> * Cache warm-up - loading data from disk to memory before the join to
> cluster -
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-40+Cache+warm-up
> * PDS Defragmentation - possibility to free up space on disc after
> removing entries
>
>
> --
> Best regards,
> Anton Kalashnikov
>
>
>
> 20.03.2020, 10:19, "Pavel Tupitsyn" <[hidden email]>:
>
> My top priorities:
>
>    - Thin Client API extension: Compute, Continuous Queries, Services
>    - .NET Near Cache: soon to come in Thick API, to be investigated for
>    Thin Clients
>    - .NET Modernization for Ignite 3.0: drop legacy .NET Framework
>    support, target .NET Standard 2.0, add nullable annotations to the API
>
>
> On Fri, Mar 20, 2020 at 5:23 AM Saikat Maitra <[hidden email]>
> wrote:
>
> Hi Denis,
>
> Thank you for sharing the list of top changes. The list looks good.
>
> I wanted to share that efforts regarding IEP-36 is already underway and
> there are also open PRs under review and working through review feedback.
> One of the area that we are focussing is first we will merge changes in
> ignite-extensions repo before removing the specific migrated module from
> ignite repo.
>
> There are also contribution from community on bug fixes in
> ignite-extensions repo as well which we are verifying and merging in
> ignite-extensions repo after running through CI pipeline in teamcity.
>
> I like the focus area on docs and I really like the Apache Ignite Usecases
> page https://ignite.apache.org/provenusecases.html,  I would like to
> suggest if we can add a page like powered by Apache Ignite and list few Org
> who are already using Apache Ignite in prod.
>
> Something similar to this page https://flink.apache.org/poweredby.html
>
> Regards,
> Saikat
>
>
>
>
>
>
> On Thu, Mar 19, 2020 at 1:44 PM Denis Magda <[hidden email]> wrote:
>
> My top list of changes is as follows:
>
>    - Feature: New lightweight Apache Ignite website with advanced search
>    engine optimizations and updated technical content. Why? Much better
>    discoverability of Ignite via search engines like Google to let many more
>    application developers learn about Ignite existence. This change is to be
>    brought to live soon:
>    http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Website-New-Look-td46324.html
>
>
>    - Feature: New Ignite documentation on a new platform and with a new
>    structure. Why? Ignite documentation has to help new application developers
>    to get up and running as quickly as possible, it also has to become a
>    primary source that answers most of the questions. Our current docs have a
>    lot of gaps: https://issues.apache.org/jira/browse/IGNITE-7595
>
>
>    - Process Change: to be successful with the point above, documentation
>    should be created/updated before we close a JIRA ticket for
>    code/API/feature contribution. Why? First, application developers learn
>    Ignite and create their Ignite-apps referring to API reference and
>    technical documentation (and not to the source code), thus, documentation
>    needs to be treated as an integral part of the whole project. Second, while
>    writing a new documentation paragraph we could discover incompleteness of a
>    fix/feature or usability issues before the change is released publicly.
>
>
>    - Feature: complete the modularization project by defining the Ignite
>    core that will be released separately from Ignite extensions. The 'why' is
>    written here:
>    https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization
>
> -
> Denis
>
>
> On Thu, Mar 19, 2020 at 11:21 AM Denis Magda <[hidden email]> wrote:
>
> Dear Ignite community,
>
> Many of us want to see where Ignite is heading and ask for some sort of a
> 2020 course/plan/roadmap and a predictable schedule of major releases.
> Also, there are intentions to enhance some internal processes and
> collaboration approaches.
>
> Let's start moving in that direction by defining 3-5 major changes you
> would like to contribute this year personally or will be glad to drive
> (like processes changes) and work together with someone else. Dear, Ignite
> user community, please share your suggestions as well.
>
> Note, let's use this thread to collect major
> topics/directions/features/changes. Just respond with your proposals. Don't
> go into arguments if you don't agree with someone's opinions. Once the
> topics are collected, we'll create a wiki page and, most likely, will start
> working through specific items in focus groups and only then lay out a
> cohesive plan with some dates.
>
> -
> Denis
>
>

[Юрий]

Hi Igniters!

Major changes that are going to be contributed from our side for IGNITE SQL:

   - Local runtime statistics which helps to estimate query execution plan.
   It should help use right join order in most cases. Seems could be done by
   Q3.
   - most efforts will be direct to new SQL engine based on Calcite. I hope
   new engine will be able to execute a query arbitrary complexity by end of
   the year, however it still have many performance optimization absent.


пт, 10 апр. 2020 г. в 14:52, Ivan Rakov <[hidden email]>:

> Hi everyone!
>
> Major changes that are going to be contributed from our side:
> - https://issues.apache.org/jira/browse/IGNITE-11704 - keeping tombstones
> for removed entries to make rebalance consistent (this problem is solved by
> on-heap deferred deletes queue so far).
> - https://issues.apache.org/jira/browse/IGNITE-11147  - don't cancel
> ongoing rebalance if affinity assignment for the rebalancing group wasn't
> changed during the PME.
> - Batch of other updates related to the historical rebalance. Goal is to
> make historical rebalance stable and to ensure that if WAL history is
> configured properly the cluster will be able to recover data consistency
> via historical rebalance in case of any topology changes (including cycling
> restart).
> - Overhaul of partition loss handling. It has several flaws so far; the
> most critical one is that by default (with PartitionLossPolicy.IGNORE)
> Ignite may silently lose data. Also, (PartitionLossPolicy.IGNORE) is
> totally inapplicable to scenarios when persistence is enabled and BLT is
> established. Also, even safe policies have bugs: LOST state is reset when
> node rejoins the cluster, so data actually can be lost even with safe
> policy. We are going to set safe policy as default and fix related bugs.
> - Distributed tracing (via OpenCensus). Discovery, communication and
> transactions will be covered.
>
> On Fri, Apr 10, 2020 at 11:43 AM Anton Kalashnikov <[hidden email]>
> wrote:
>
>> My top priorities:
>> * Cache warm-up - loading data from disk to memory before the join to
>> cluster -
>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-40+Cache+warm-up
>> * PDS Defragmentation - possibility to free up space on disc after
>> removing entries
>>
>>
>> --
>> Best regards,
>> Anton Kalashnikov
>>
>>
>>
>> 20.03.2020, 10:19, "Pavel Tupitsyn" <[hidden email]>:
>>
>> My top priorities:
>>
>>    - Thin Client API extension: Compute, Continuous Queries, Services
>>    - .NET Near Cache: soon to come in Thick API, to be investigated for
>>    Thin Clients
>>    - .NET Modernization for Ignite 3.0: drop legacy .NET Framework
>>    support, target .NET Standard 2.0, add nullable annotations to the API
>>
>>
>> On Fri, Mar 20, 2020 at 5:23 AM Saikat Maitra <[hidden email]>
>> wrote:
>>
>> Hi Denis,
>>
>> Thank you for sharing the list of top changes. The list looks good.
>>
>> I wanted to share that efforts regarding IEP-36 is already underway and
>> there are also open PRs under review and working through review feedback.
>> One of the area that we are focussing is first we will merge changes in
>> ignite-extensions repo before removing the specific migrated module from
>> ignite repo.
>>
>> There are also contribution from community on bug fixes in
>> ignite-extensions repo as well which we are verifying and merging in
>> ignite-extensions repo after running through CI pipeline in teamcity.
>>
>> I like the focus area on docs and I really like the Apache Ignite
>> Usecases page https://ignite.apache.org/provenusecases.html,  I would
>> like to suggest if we can add a page like powered by Apache Ignite and list
>> few Org who are already using Apache Ignite in prod.
>>
>> Something similar to this page https://flink.apache.org/poweredby.html
>>
>> Regards,
>> Saikat
>>
>>
>>
>>
>>
>>
>> On Thu, Mar 19, 2020 at 1:44 PM Denis Magda <[hidden email]> wrote:
>>
>> My top list of changes is as follows:
>>
>>    - Feature: New lightweight Apache Ignite website with advanced search
>>    engine optimizations and updated technical content. Why? Much better
>>    discoverability of Ignite via search engines like Google to let many more
>>    application developers learn about Ignite existence. This change is to be
>>    brought to live soon:
>>    http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-Website-New-Look-td46324.html
>>
>>
>>    - Feature: New Ignite documentation on a new platform and with a new
>>    structure. Why? Ignite documentation has to help new application developers
>>    to get up and running as quickly as possible, it also has to become a
>>    primary source that answers most of the questions. Our current docs have a
>>    lot of gaps: https://issues.apache.org/jira/browse/IGNITE-7595
>>
>>
>>    - Process Change: to be successful with the point above,
>>    documentation should be created/updated before we close a JIRA ticket for
>>    code/API/feature contribution. Why? First, application developers learn
>>    Ignite and create their Ignite-apps referring to API reference and
>>    technical documentation (and not to the source code), thus, documentation
>>    needs to be treated as an integral part of the whole project. Second, while
>>    writing a new documentation paragraph we could discover incompleteness of a
>>    fix/feature or usability issues before the change is released publicly.
>>
>>
>>    - Feature: complete the modularization project by defining the Ignite
>>    core that will be released separately from Ignite extensions. The 'why' is
>>    written here:
>>    https://cwiki.apache.org/confluence/display/IGNITE/IEP-36%3A+Modularization
>>
>> -
>> Denis
>>
>>
>> On Thu, Mar 19, 2020 at 11:21 AM Denis Magda <[hidden email]> wrote:
>>
>> Dear Ignite community,
>>
>> Many of us want to see where Ignite is heading and ask for some sort of a
>> 2020 course/plan/roadmap and a predictable schedule of major releases.
>> Also, there are intentions to enhance some internal processes and
>> collaboration approaches.
>>
>> Let's start moving in that direction by defining 3-5 major changes you
>> would like to contribute this year personally or will be glad to drive
>> (like processes changes) and work together with someone else. Dear, Ignite
>> user community, please share your suggestions as well.
>>
>> Note, let's use this thread to collect major
>> topics/directions/features/changes. Just respond with your proposals. Don't
>> go into arguments if you don't agree with someone's opinions. Once the
>> topics are collected, we'll create a wiki page and, most likely, will start
>> working through specific items in focus groups and only then lay out a
>> cohesive plan with some dates.
>>
>> -
>> Denis
>>
>>

--
Живи с улыбкой! :D

[smeadows-abb]

My company is initiating major project using Golang, Ignite and need native
Golang client support. What is the status of support for Golang?



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[Igor Sapego-2]

My plan includes:
* Cluster API for C++ thick client
* Moving Python, Node.js and PHP thin clients in separate repositories and
separate release cycles.
* Partition Awareness for Python and Node.js thin clients
* SQL for C++ thin client.

Steven,

There are some third-party golang clients AFAIK, for example [1]. Though
I'm not aware of their current
status.

[1] - https://github.com/amsokol/ignite-go-client


Best Regards,
Igor


On Fri, Apr 10, 2020 at 5:26 PM smeadows-abb <[hidden email]>
wrote:

> My company is initiating major project using Golang, Ignite and need native
> Golang client support. What is the status of support for Golang?
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[smeadows-abb]

First thanks for your quick response.

I looked at  https://github.com/amsokol/ignite-go-client and its NOT
completed and nothing has been for last 16 months. Initial test with package
failed, so trying to determine your project roadmap with regards to Golang
and maybe Rust support.

I'm NOT sure of 'AFAIK' ?

We may need to implement your Restful API to provide support for Golang and
Rust, provided it's complete?

Thanks,
  Steve





--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[dmagda]

Folks,

Thanks to everyone responded.

@Alexey Zinoviev <[hidden email]>, @Alexey Scherbakov
<[hidden email]>, @Nikolay Izhikov <[hidden email]>, @Maxim
Muzafarov <[hidden email]>, @Anton Vinogradov <[hidden email]>, @Andrey
Gura <[hidden email]>  could you guys please also join this thread and
share your intentions for this year?

What I want to do next, once the majority responds, is to create an Ignite
Roadmap wiki page and put together a table with all the initiatives. The
table will have an "expected readiness" column with contributors best
guess/estimate on when an improvement is to be ready (you would need to
fill it once the page exists). The last column will be for a target release
- once we see that many improvements converge around some date, then we'll
know when Ignite 2.9, 2.10, etc. need to be released. Hope you guys are
fine with such an approach for the roadmap and release schedule creation.

-
Denis


On Fri, Apr 10, 2020 at 7:44 AM Igor Sapego <[hidden email]> wrote:

> My plan includes:
> * Cluster API for C++ thick client
> * Moving Python, Node.js and PHP thin clients in separate repositories and
> separate release cycles.
> * Partition Awareness for Python and Node.js thin clients
> * SQL for C++ thin client.
>
> Steven,
>
> There are some third-party golang clients AFAIK, for example [1]. Though
> I'm not aware of their current
> status.
>
> [1] - https://github.com/amsokol/ignite-go-client
>
>
> Best Regards,
> Igor
>
>
> On Fri, Apr 10, 2020 at 5:26 PM smeadows-abb <[hidden email]>
> wrote:
>
> > My company is initiating major project using Golang, Ignite and need
> native
> > Golang client support. What is the status of support for Golang?
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >
>

[Alexey Zinoviev]

Hi, Denis, currently I'm working on roadmap, will publish during this
month. Need a time to estimate different things.
Will join later and update the wiki pages suggested earlier.

пт, 10 апр. 2020 г. в 18:38, Denis Magda <[hidden email]>:

> Folks,
>
> Thanks to everyone responded.
>
> @Alexey Zinoviev <[hidden email]>, @Alexey Scherbakov
> <[hidden email]>, @Nikolay Izhikov <[hidden email]>, @Maxim
> Muzafarov <[hidden email]>, @Anton Vinogradov <[hidden email]>, @Andrey
> Gura <[hidden email]>  could you guys please also join this thread and
> share your intentions for this year?
>
> What I want to do next, once the majority responds, is to create an Ignite
> Roadmap wiki page and put together a table with all the initiatives. The
> table will have an "expected readiness" column with contributors best
> guess/estimate on when an improvement is to be ready (you would need to
> fill it once the page exists). The last column will be for a target release
> - once we see that many improvements converge around some date, then we'll
> know when Ignite 2.9, 2.10, etc. need to be released. Hope you guys are
> fine with such an approach for the roadmap and release schedule creation.
>
> -
> Denis
>
>
> On Fri, Apr 10, 2020 at 7:44 AM Igor Sapego <[hidden email]> wrote:
>
>> My plan includes:
>> * Cluster API for C++ thick client
>> * Moving Python, Node.js and PHP thin clients in separate repositories and
>> separate release cycles.
>> * Partition Awareness for Python and Node.js thin clients
>> * SQL for C++ thin client.
>>
>> Steven,
>>
>> There are some third-party golang clients AFAIK, for example [1]. Though
>> I'm not aware of their current
>> status.
>>
>> [1] - https://github.com/amsokol/ignite-go-client
>>
>>
>> Best Regards,
>> Igor
>>
>>
>> On Fri, Apr 10, 2020 at 5:26 PM smeadows-abb <[hidden email]>
>> wrote:
>>
>> > My company is initiating major project using Golang, Ignite and need
>> native
>> > Golang client support. What is the status of support for Golang?
>> >
>> >
>> >
>> > --
>> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>> >
>>
>

[dmagda]

Steven,

Please start a dedicated discussion for the Golang support. At the moment,
I'm not aware if anybody from the community planned to provide support
out-of-the-box. However, that's not a tricky task thanks to Ignite's binary
protocol that lets enable any programming language support easily.

-
Denis


On Fri, Apr 10, 2020 at 8:43 AM smeadows-abb <[hidden email]>
wrote:

> First thanks for your quick response.
>
> I looked at  https://github.com/amsokol/ignite-go-client and its NOT
> completed and nothing has been for last 16 months. Initial test with
> package
> failed, so trying to determine your project roadmap with regards to Golang
> and maybe Rust support.
>
> I'm NOT sure of 'AFAIK' ?
>
> We may need to implement your Restful API to provide support for Golang and
> Rust, provided it's complete?
>
> Thanks,
>   Steve
>
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[Alexei Scherbakov]

Folks,

I keep working on tasks related to data consistency.

This includes:

Lost partitions handling overhaul (almost done) and tombstones support
aforementioned by Ivan Rakov
Atomic protocol overhaul (see [1])

The ultimate goal of the year is to prepare Ignite for passing Jepsen tests.

[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again


пт, 10 апр. 2020 г. в 18:49, Denis Magda <[hidden email]>:

> Steven,
>
> Please start a dedicated discussion for the Golang support. At the moment,
> I'm not aware if anybody from the community planned to provide support
> out-of-the-box. However, that's not a tricky task thanks to Ignite's binary
> protocol that lets enable any programming language support easily.
>
> -
> Denis
>
>
> On Fri, Apr 10, 2020 at 8:43 AM smeadows-abb <[hidden email]>
> wrote:
>
> > First thanks for your quick response.
> >
> > I looked at  https://github.com/amsokol/ignite-go-client and its NOT
> > completed and nothing has been for last 16 months. Initial test with
> > package
> > failed, so trying to determine your project roadmap with regards to
> Golang
> > and maybe Rust support.
> >
> > I'm NOT sure of 'AFAIK' ?
> >
> > We may need to implement your Restful API to provide support for Golang
> and
> > Rust, provided it's complete?
> >
> > Thanks,
> >   Steve
> >
> >
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >
>

--

Best regards,
Alexei Scherbakov

[Pavel Pereslegin]

Hello,

I plan to implement cache key rotation for TDE (phase 3) [1][2].
(At the moment, the design is very draft and will be changed soon).

[1] https://issues.apache.org/jira/browse/IGNITE-12843
[2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652384


сб, 11 апр. 2020 г. в 13:54, Alexei Scherbakov <[hidden email]>:

>
> Folks,
>
> I keep working on tasks related to data consistency.
>
> This includes:
>
> Lost partitions handling overhaul (almost done) and tombstones support
> aforementioned by Ivan Rakov
> Atomic protocol overhaul (see [1])
>
> The ultimate goal of the year is to prepare Ignite for passing Jepsen tests.
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
>
>
> пт, 10 апр. 2020 г. в 18:49, Denis Magda <[hidden email]>:
>
> > Steven,
> >
> > Please start a dedicated discussion for the Golang support. At the moment,
> > I'm not aware if anybody from the community planned to provide support
> > out-of-the-box. However, that's not a tricky task thanks to Ignite's binary
> > protocol that lets enable any programming language support easily.
> >
> > -
> > Denis
> >
> >
> > On Fri, Apr 10, 2020 at 8:43 AM smeadows-abb <[hidden email]>
> > wrote:
> >
> > > First thanks for your quick response.
> > >
> > > I looked at  https://github.com/amsokol/ignite-go-client and its NOT
> > > completed and nothing has been for last 16 months. Initial test with
> > > package
> > > failed, so trying to determine your project roadmap with regards to
> > Golang
> > > and maybe Rust support.
> > >
> > > I'm NOT sure of 'AFAIK' ?
> > >
> > > We may need to implement your Restful API to provide support for Golang
> > and
> > > Rust, provided it's complete?
> > >
> > > Thanks,
> > >   Steve
> > >
> > >
> > >
> > >
> > >
> > > --
> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > >
> >
>
>
> --
>
> Best regards,
> Alexei Scherbakov

[Nikita Amelchev]

Hello, Igniters.

I am going to contribute a new feature - profiling tool and
performance report. This is part of IEP-35. [1]

The tool will be able to collect performance statistics and create a
human-readable report. It will help to analyze workload and to tune
configuration and applications.

Example of report [2, 3, 4].

[1] https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool
[2] https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647581/p1.png
[3] https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647582/p2.png
[4] https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647583/p3.png

сб, 11 апр. 2020 г. в 13:54, Alexei Scherbakov <[hidden email]>:

>
> Folks,
>
> I keep working on tasks related to data consistency.
>
> This includes:
>
> Lost partitions handling overhaul (almost done) and tombstones support
> aforementioned by Ivan Rakov
> Atomic protocol overhaul (see [1])
>
> The ultimate goal of the year is to prepare Ignite for passing Jepsen tests.
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
>
>
> пт, 10 апр. 2020 г. в 18:49, Denis Magda <[hidden email]>:
>
> > Steven,
> >
> > Please start a dedicated discussion for the Golang support. At the moment,
> > I'm not aware if anybody from the community planned to provide support
> > out-of-the-box. However, that's not a tricky task thanks to Ignite's binary
> > protocol that lets enable any programming language support easily.
> >
> > -
> > Denis
> >
> >
> > On Fri, Apr 10, 2020 at 8:43 AM smeadows-abb <[hidden email]>
> > wrote:
> >
> > > First thanks for your quick response.
> > >
> > > I looked at  https://github.com/amsokol/ignite-go-client and its NOT
> > > completed and nothing has been for last 16 months. Initial test with
> > > package
> > > failed, so trying to determine your project roadmap with regards to
> > Golang
> > > and maybe Rust support.
> > >
> > > I'm NOT sure of 'AFAIK' ?
> > >
> > > We may need to implement your Restful API to provide support for Golang
> > and
> > > Rust, provided it's complete?
> > >
> > > Thanks,
> > >   Steve
> > >
> > >
> > >
> > >
> > >
> > > --
> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > >
> >
>
>
> --
>
> Best regards,
> Alexei Scherbakov

--
Best wishes,
Amelchev Nikita

[dmagda]

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 improvement is to be ready for a release.
   - Add references to JIRAs or IEPs to the first column.
   - Add the names of those contributors who will be cooperating with you
   during development. Goes to the "Contributors" column.

Once this step is complete, we'll see how many features converge around the
same date/months and we'll plan through 2.9, 2.10, etc. releases
accordingly.

Please don't put this aside for a while, let's move on quicker. If the
roadmap misses any contributions that you are going to add, then edit the
wiki page.

-
Denis


On Wed, Apr 15, 2020 at 3:35 AM Nikita Amelchev <[hidden email]>
wrote:

> Hello, Igniters.
>
> I am going to contribute a new feature - profiling tool and
> performance report. This is part of IEP-35. [1]
>
> The tool will be able to collect performance statistics and create a
> human-readable report. It will help to analyze workload and to tune
> configuration and applications.
>
> Example of report [2, 3, 4].
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool
> [2]
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647581/p1.png
> [3]
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647582/p2.png
> [4]
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647583/p3.png
>
> сб, 11 апр. 2020 г. в 13:54, Alexei Scherbakov <
> [hidden email]>:
> >
> > Folks,
> >
> > I keep working on tasks related to data consistency.
> >
> > This includes:
> >
> > Lost partitions handling overhaul (almost done) and tombstones support
> > aforementioned by Ivan Rakov
> > Atomic protocol overhaul (see [1])
> >
> > The ultimate goal of the year is to prepare Ignite for passing Jepsen
> tests.
> >
> > [1]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
> >
> >
> > пт, 10 апр. 2020 г. в 18:49, Denis Magda <[hidden email]>:
> >
> > > Steven,
> > >
> > > Please start a dedicated discussion for the Golang support. At the
> moment,
> > > I'm not aware if anybody from the community planned to provide support
> > > out-of-the-box. However, that's not a tricky task thanks to Ignite's
> binary
> > > protocol that lets enable any programming language support easily.
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Fri, Apr 10, 2020 at 8:43 AM smeadows-abb <
> [hidden email]>
> > > wrote:
> > >
> > > > First thanks for your quick response.
> > > >
> > > > I looked at  https://github.com/amsokol/ignite-go-client and its NOT
> > > > completed and nothing has been for last 16 months. Initial test with
> > > > package
> > > > failed, so trying to determine your project roadmap with regards to
> > > Golang
> > > > and maybe Rust support.
> > > >
> > > > I'm NOT sure of 'AFAIK' ?
> > > >
> > > > We may need to implement your Restful API to provide support for
> Golang
> > > and
> > > > Rust, provided it's complete?
> > > >
> > > > Thanks,
> > > >   Steve
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > > >
> > >
> >
> >
> > --
> >
> > Best regards,
> > Alexei Scherbakov
>
>
>
> --
> Best wishes,
> Amelchev Nikita
>

[Dmitry Pavlov]

Hi Denis,

Thank you for driving this.

Igniters,

I would suggest to stress that Apache Ignite community does not guarantee
these features to be available.

Can we add some kind of disclaimer that says Ignite Roadmap does not imply
any obligations regarding availability and timeline. A number of
contributions can be done on best efforts principle, it is always tricky to
make a promise.

Sincerely,
Dmitriy Pavlov

чт, 23 апр. 2020 г. в 00:06, Denis Magda <[hidden email]>:

> 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 improvement is to be ready for a release.
>    - Add references to JIRAs or IEPs to the first column.
>    - Add the names of those contributors who will be cooperating with you
>    during development. Goes to the "Contributors" column.
>
> Once this step is complete, we'll see how many features converge around the
> same date/months and we'll plan through 2.9, 2.10, etc. releases
> accordingly.
>
> Please don't put this aside for a while, let's move on quicker. If the
> roadmap misses any contributions that you are going to add, then edit the
> wiki page.
>
> -
> Denis
>
>
> On Wed, Apr 15, 2020 at 3:35 AM Nikita Amelchev <[hidden email]>
> wrote:
>
> > Hello, Igniters.
> >
> > I am going to contribute a new feature - profiling tool and
> > performance report. This is part of IEP-35. [1]
> >
> > The tool will be able to collect performance statistics and create a
> > human-readable report. It will help to analyze workload and to tune
> > configuration and applications.
> >
> > Example of report [2, 3, 4].
> >
> > [1]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool
> > [2]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647581/p1.png
> > [3]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647582/p2.png
> > [4]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647583/p3.png
> >
> > сб, 11 апр. 2020 г. в 13:54, Alexei Scherbakov <
> > [hidden email]>:
> > >
> > > Folks,
> > >
> > > I keep working on tasks related to data consistency.
> > >
> > > This includes:
> > >
> > > Lost partitions handling overhaul (almost done) and tombstones support
> > > aforementioned by Ivan Rakov
> > > Atomic protocol overhaul (see [1])
> > >
> > > The ultimate goal of the year is to prepare Ignite for passing Jepsen
> > tests.
> > >
> > > [1]
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
> > >
> > >
> > > пт, 10 апр. 2020 г. в 18:49, Denis Magda <[hidden email]>:
> > >
> > > > Steven,
> > > >
> > > > Please start a dedicated discussion for the Golang support. At the
> > moment,
> > > > I'm not aware if anybody from the community planned to provide
> support
> > > > out-of-the-box. However, that's not a tricky task thanks to Ignite's
> > binary
> > > > protocol that lets enable any programming language support easily.
> > > >
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Fri, Apr 10, 2020 at 8:43 AM smeadows-abb <
> > [hidden email]>
> > > > wrote:
> > > >
> > > > > First thanks for your quick response.
> > > > >
> > > > > I looked at  https://github.com/amsokol/ignite-go-client and its
> NOT
> > > > > completed and nothing has been for last 16 months. Initial test
> with
> > > > > package
> > > > > failed, so trying to determine your project roadmap with regards to
> > > > Golang
> > > > > and maybe Rust support.
> > > > >
> > > > > I'm NOT sure of 'AFAIK' ?
> > > > >
> > > > > We may need to implement your Restful API to provide support for
> > Golang
> > > > and
> > > > > Rust, provided it's complete?
> > > > >
> > > > > Thanks,
> > > > >   Steve
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Best regards,
> > > Alexei Scherbakov
> >
> >
> >
> > --
> > Best wishes,
> > Amelchev Nikita
> >
>

[dmagda]

Dmitry, highlighted such a disclaimer in italic. Thanks.

-
Denis


On Thu, Apr 23, 2020 at 3:53 AM Dmitriy Pavlov <[hidden email]> wrote:

> Hi Denis,
>
> Thank you for driving this.
>
> Igniters,
>
> I would suggest to stress that Apache Ignite community does not guarantee
> these features to be available.
>
> Can we add some kind of disclaimer that says Ignite Roadmap does not imply
> any obligations regarding availability and timeline. A number of
> contributions can be done on best efforts principle, it is always tricky to
> make a promise.
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 23 апр. 2020 г. в 00:06, Denis Magda <[hidden email]>:
>
> > 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 improvement is to be ready for a release.
> >    - Add references to JIRAs or IEPs to the first column.
> >    - Add the names of those contributors who will be cooperating with you
> >    during development. Goes to the "Contributors" column.
> >
> > Once this step is complete, we'll see how many features converge around
> the
> > same date/months and we'll plan through 2.9, 2.10, etc. releases
> > accordingly.
> >
> > Please don't put this aside for a while, let's move on quicker. If the
> > roadmap misses any contributions that you are going to add, then edit the
> > wiki page.
> >
> > -
> > Denis
> >
> >
> > On Wed, Apr 15, 2020 at 3:35 AM Nikita Amelchev <[hidden email]>
> > wrote:
> >
> > > Hello, Igniters.
> > >
> > > I am going to contribute a new feature - profiling tool and
> > > performance report. This is part of IEP-35. [1]
> > >
> > > The tool will be able to collect performance statistics and create a
> > > human-readable report. It will help to analyze workload and to tune
> > > configuration and applications.
> > >
> > > Example of report [2, 3, 4].
> > >
> > > [1]
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool
> > > [2]
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647581/p1.png
> > > [3]
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647582/p2.png
> > > [4]
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647583/p3.png
> > >
> > > сб, 11 апр. 2020 г. в 13:54, Alexei Scherbakov <
> > > [hidden email]>:
> > > >
> > > > Folks,
> > > >
> > > > I keep working on tasks related to data consistency.
> > > >
> > > > This includes:
> > > >
> > > > Lost partitions handling overhaul (almost done) and tombstones
> support
> > > > aforementioned by Ivan Rakov
> > > > Atomic protocol overhaul (see [1])
> > > >
> > > > The ultimate goal of the year is to prepare Ignite for passing Jepsen
> > > tests.
> > > >
> > > > [1]
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
> > > >
> > > >
> > > > пт, 10 апр. 2020 г. в 18:49, Denis Magda <[hidden email]>:
> > > >
> > > > > Steven,
> > > > >
> > > > > Please start a dedicated discussion for the Golang support. At the
> > > moment,
> > > > > I'm not aware if anybody from the community planned to provide
> > support
> > > > > out-of-the-box. However, that's not a tricky task thanks to
> Ignite's
> > > binary
> > > > > protocol that lets enable any programming language support easily.
> > > > >
> > > > > -
> > > > > Denis
> > > > >
> > > > >
> > > > > On Fri, Apr 10, 2020 at 8:43 AM smeadows-abb <
> > > [hidden email]>
> > > > > wrote:
> > > > >
> > > > > > First thanks for your quick response.
> > > > > >
> > > > > > I looked at  https://github.com/amsokol/ignite-go-client and its
> > NOT
> > > > > > completed and nothing has been for last 16 months. Initial test
> > with
> > > > > > package
> > > > > > failed, so trying to determine your project roadmap with regards
> to
> > > > > Golang
> > > > > > and maybe Rust support.
> > > > > >
> > > > > > I'm NOT sure of 'AFAIK' ?
> > > > > >
> > > > > > We may need to implement your Restful API to provide support for
> > > Golang
> > > > > and
> > > > > > Rust, provided it's complete?
> > > > > >
> > > > > > Thanks,
> > > > > >   Steve
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Sent from:
> http://apache-ignite-developers.2346864.n4.nabble.com/
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Best regards,
> > > > Alexei Scherbakov
> > >
> > >
> > >
> > > --
> > > Best wishes,
> > > Amelchev Nikita
> > >
> >
>

[Nikolay Izhikov-2]

Hello, Igniters.

Right now I working on POC for some «framework» for integration testing of Ignite.

Feature I want to see in this framework:

        * To manage several Ignite instances inside docker or bare metal servers.
        * To manage Ignite cluster
        * Start/stop arbitrary application to interact with Ignite.
        * Kill nodes
        * collect logs.
        * implement complex real-life based scenarios
        * etc.

My POC are based on duck tape library [1]

[1] https://github.com/confluentinc/ducktape

> 25 апр. 2020 г., в 00:51, Denis Magda <[hidden email]> написал(а):
>
> Dmitry, highlighted such a disclaimer in italic. Thanks.
>
> -
> Denis
>
>
> On Thu, Apr 23, 2020 at 3:53 AM Dmitriy Pavlov <[hidden email]> wrote:
>
>> Hi Denis,
>>
>> Thank you for driving this.
>>
>> Igniters,
>>
>> I would suggest to stress that Apache Ignite community does not guarantee
>> these features to be available.
>>
>> Can we add some kind of disclaimer that says Ignite Roadmap does not imply
>> any obligations regarding availability and timeline. A number of
>> contributions can be done on best efforts principle, it is always tricky to
>> make a promise.
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> чт, 23 апр. 2020 г. в 00:06, Denis Magda <[hidden email]>:
>>
>>> 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 improvement is to be ready for a release.
>>>   - Add references to JIRAs or IEPs to the first column.
>>>   - Add the names of those contributors who will be cooperating with you
>>>   during development. Goes to the "Contributors" column.
>>>
>>> Once this step is complete, we'll see how many features converge around
>> the
>>> same date/months and we'll plan through 2.9, 2.10, etc. releases
>>> accordingly.
>>>
>>> Please don't put this aside for a while, let's move on quicker. If the
>>> roadmap misses any contributions that you are going to add, then edit the
>>> wiki page.
>>>
>>> -
>>> Denis
>>>
>>>
>>> On Wed, Apr 15, 2020 at 3:35 AM Nikita Amelchev <[hidden email]>
>>> wrote:
>>>
>>>> Hello, Igniters.
>>>>
>>>> I am going to contribute a new feature - profiling tool and
>>>> performance report. This is part of IEP-35. [1]
>>>>
>>>> The tool will be able to collect performance statistics and create a
>>>> human-readable report. It will help to analyze workload and to tune
>>>> configuration and applications.
>>>>
>>>> Example of report [2, 3, 4].
>>>>
>>>> [1]
>>>>
>>>
>> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool
>>>> [2]
>>>>
>>>
>> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647581/p1.png
>>>> [3]
>>>>
>>>
>> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647582/p2.png
>>>> [4]
>>>>
>>>
>> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647583/p3.png
>>>>
>>>> сб, 11 апр. 2020 г. в 13:54, Alexei Scherbakov <
>>>> [hidden email]>:
>>>>>
>>>>> Folks,
>>>>>
>>>>> I keep working on tasks related to data consistency.
>>>>>
>>>>> This includes:
>>>>>
>>>>> Lost partitions handling overhaul (almost done) and tombstones
>> support
>>>>> aforementioned by Ivan Rakov
>>>>> Atomic protocol overhaul (see [1])
>>>>>
>>>>> The ultimate goal of the year is to prepare Ignite for passing Jepsen
>>>> tests.
>>>>>
>>>>> [1]
>>>>>
>>>>
>>>
>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
>>>>>
>>>>>
>>>>> пт, 10 апр. 2020 г. в 18:49, Denis Magda <[hidden email]>:
>>>>>
>>>>>> Steven,
>>>>>>
>>>>>> Please start a dedicated discussion for the Golang support. At the
>>>> moment,
>>>>>> I'm not aware if anybody from the community planned to provide
>>> support
>>>>>> out-of-the-box. However, that's not a tricky task thanks to
>> Ignite's
>>>> binary
>>>>>> protocol that lets enable any programming language support easily.
>>>>>>
>>>>>> -
>>>>>> Denis
>>>>>>
>>>>>>
>>>>>> On Fri, Apr 10, 2020 at 8:43 AM smeadows-abb <
>>>> [hidden email]>
>>>>>> wrote:
>>>>>>
>>>>>>> First thanks for your quick response.
>>>>>>>
>>>>>>> I looked at  https://github.com/amsokol/ignite-go-client and its
>>> NOT
>>>>>>> completed and nothing has been for last 16 months. Initial test
>>> with
>>>>>>> package
>>>>>>> failed, so trying to determine your project roadmap with regards
>> to
>>>>>> Golang
>>>>>>> and maybe Rust support.
>>>>>>>
>>>>>>> I'm NOT sure of 'AFAIK' ?
>>>>>>>
>>>>>>> We may need to implement your Restful API to provide support for
>>>> Golang
>>>>>> and
>>>>>>> Rust, provided it's complete?
>>>>>>>
>>>>>>> Thanks,
>>>>>>>  Steve
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Sent from:
>> http://apache-ignite-developers.2346864.n4.nabble.com/
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Best regards,
>>>>> Alexei Scherbakov
>>>>
>>>>
>>>>
>>>> --
>>>> Best wishes,
>>>> Amelchev Nikita
>>>>
>>>
>>

[dmagda]

Nikolay, thanks for responding,

Would you prefer adding this item to the roadmap page after finishing the
idea testing? If there are still many unknowns it can make to the roadmap
after you share the results and propose a final solution.

-
Denis


On Mon, Apr 27, 2020 at 2:06 PM Nikolay Izhikov <[hidden email]> wrote:

> Hello, Igniters.
>
> Right now I working on POC for some «framework» for integration testing of
> Ignite.
>
> Feature I want to see in this framework:
>
>         * To manage several Ignite instances inside docker or bare metal
> servers.
>         * To manage Ignite cluster
>         * Start/stop arbitrary application to interact with Ignite.
>         * Kill nodes
>         * collect logs.
>         * implement complex real-life based scenarios
>         * etc.
>
> My POC are based on duck tape library [1]
>
> [1] https://github.com/confluentinc/ducktape
>
> > 25 апр. 2020 г., в 00:51, Denis Magda <[hidden email]> написал(а):
> >
> > Dmitry, highlighted such a disclaimer in italic. Thanks.
> >
> > -
> > Denis
> >
> >
> > On Thu, Apr 23, 2020 at 3:53 AM Dmitriy Pavlov <[hidden email]>
> wrote:
> >
> >> Hi Denis,
> >>
> >> Thank you for driving this.
> >>
> >> Igniters,
> >>
> >> I would suggest to stress that Apache Ignite community does not
> guarantee
> >> these features to be available.
> >>
> >> Can we add some kind of disclaimer that says Ignite Roadmap does not
> imply
> >> any obligations regarding availability and timeline. A number of
> >> contributions can be done on best efforts principle, it is always
> tricky to
> >> make a promise.
> >>
> >> Sincerely,
> >> Dmitriy Pavlov
> >>
> >> чт, 23 апр. 2020 г. в 00:06, Denis Magda <[hidden email]>:
> >>
> >>> 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 improvement is to be ready for a release.
> >>>   - Add references to JIRAs or IEPs to the first column.
> >>>   - Add the names of those contributors who will be cooperating with
> you
> >>>   during development. Goes to the "Contributors" column.
> >>>
> >>> Once this step is complete, we'll see how many features converge around
> >> the
> >>> same date/months and we'll plan through 2.9, 2.10, etc. releases
> >>> accordingly.
> >>>
> >>> Please don't put this aside for a while, let's move on quicker. If the
> >>> roadmap misses any contributions that you are going to add, then edit
> the
> >>> wiki page.
> >>>
> >>> -
> >>> Denis
> >>>
> >>>
> >>> On Wed, Apr 15, 2020 at 3:35 AM Nikita Amelchev <[hidden email]>
> >>> wrote:
> >>>
> >>>> Hello, Igniters.
> >>>>
> >>>> I am going to contribute a new feature - profiling tool and
> >>>> performance report. This is part of IEP-35. [1]
> >>>>
> >>>> The tool will be able to collect performance statistics and create a
> >>>> human-readable report. It will help to analyze workload and to tune
> >>>> configuration and applications.
> >>>>
> >>>> Example of report [2, 3, 4].
> >>>>
> >>>> [1]
> >>>>
> >>>
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool
> >>>> [2]
> >>>>
> >>>
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647581/p1.png
> >>>> [3]
> >>>>
> >>>
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647582/p2.png
> >>>> [4]
> >>>>
> >>>
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/Cluster+performance+profiling+tool?preview=/145723859/148647583/p3.png
> >>>>
> >>>> сб, 11 апр. 2020 г. в 13:54, Alexei Scherbakov <
> >>>> [hidden email]>:
> >>>>>
> >>>>> Folks,
> >>>>>
> >>>>> I keep working on tasks related to data consistency.
> >>>>>
> >>>>> This includes:
> >>>>>
> >>>>> Lost partitions handling overhaul (almost done) and tombstones
> >> support
> >>>>> aforementioned by Ivan Rakov
> >>>>> Atomic protocol overhaul (see [1])
> >>>>>
> >>>>> The ultimate goal of the year is to prepare Ignite for passing Jepsen
> >>>> tests.
> >>>>>
> >>>>> [1]
> >>>>>
> >>>>
> >>>
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
> >>>>>
> >>>>>
> >>>>> пт, 10 апр. 2020 г. в 18:49, Denis Magda <[hidden email]>:
> >>>>>
> >>>>>> Steven,
> >>>>>>
> >>>>>> Please start a dedicated discussion for the Golang support. At the
> >>>> moment,
> >>>>>> I'm not aware if anybody from the community planned to provide
> >>> support
> >>>>>> out-of-the-box. However, that's not a tricky task thanks to
> >> Ignite's
> >>>> binary
> >>>>>> protocol that lets enable any programming language support easily.
> >>>>>>
> >>>>>> -
> >>>>>> Denis
> >>>>>>
> >>>>>>
> >>>>>> On Fri, Apr 10, 2020 at 8:43 AM smeadows-abb <
> >>>> [hidden email]>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> First thanks for your quick response.
> >>>>>>>
> >>>>>>> I looked at  https://github.com/amsokol/ignite-go-client and its
> >>> NOT
> >>>>>>> completed and nothing has been for last 16 months. Initial test
> >>> with
> >>>>>>> package
> >>>>>>> failed, so trying to determine your project roadmap with regards
> >> to
> >>>>>> Golang
> >>>>>>> and maybe Rust support.
> >>>>>>>
> >>>>>>> I'm NOT sure of 'AFAIK' ?
> >>>>>>>
> >>>>>>> We may need to implement your Restful API to provide support for
> >>>> Golang
> >>>>>> and
> >>>>>>> Rust, provided it's complete?
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>>  Steve
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> Sent from:
> >> http://apache-ignite-developers.2346864.n4.nabble.com/
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>> Best regards,
> >>>>> Alexei Scherbakov
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Best wishes,
> >>>> Amelchev Nikita
> >>>>
> >>>
> >>
>
>