[MTCGA]: new failures in builds [5623554] needs to be handled

[dpavlov . tasks]

Hi Igniters,

 I've detected some new issue on TeamCity to be handled. You are more than 
welcomed to help.

 If your changes can lead to this failure(s): We're grateful that you were a 
volunteer to make the contribution to this project, but things change and you 
may no longer be able to finalize your contribution.
 Could you respond to this email and indicate if you wish to continue and fix 
test failures or step down and some committer may revert you commit. 

 *New test failure in master BasicIndexTest.testInlineSizeChange 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=6131871779633595667=%3Cdefault%3E=testDetails
 Changes may lead to failure were done by 
 - igor sapego  
https://ci.ignite.apache.org/viewModification.html?modId=907658

 - Here's a reminder of what contributors were agreed to do 
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute 
 - Should you have any questions please contact dev@ignite.apache.org 

Best Regards,
Apache Ignite TeamCity Bot 
https://github.com/apache/ignite-teamcity-bot
Notification generated at 06:41:21 26-09-2020 

[MTCGA]: new failures in builds [5623586] needs to be handled

[dpavlov . tasks]

Hi Igniters,

 I've detected some new issue on TeamCity to be handled. You are more than 
welcomed to help.

 If your changes can lead to this failure(s): We're grateful that you were a 
volunteer to make the contribution to this project, but things change and you 
may no longer be able to finalize your contribution.
 Could you respond to this email and indicate if you wish to continue and fix 
test failures or step down and some committer may revert you commit. 

 *New Critical Failure in master-nightly Disk Page Compressions 
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_DiskPageCompressions?branch=%3Cdefault%3E
 Changes may lead to failure were done by 
 - igor sapego  
https://ci.ignite.apache.org/viewModification.html?modId=907658

 - Here's a reminder of what contributors were agreed to do 
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute 
 - Should you have any questions please contact dev@ignite.apache.org 

Best Regards,
Apache Ignite TeamCity Bot 
https://github.com/apache/ignite-teamcity-bot
Notification generated at 02:26:19 26-09-2020 

[MTCGA]: new failures in builds [5623568] needs to be handled

[dpavlov . tasks]

Hi Igniters,

 I've detected some new issue on TeamCity to be handled. You are more than 
welcomed to help.

 If your changes can lead to this failure(s): We're grateful that you were a 
volunteer to make the contribution to this project, but things change and you 
may no longer be able to finalize your contribution.
 Could you respond to this email and indicate if you wish to continue and fix 
test failures or step down and some committer may revert you commit. 

 *New Critical Failure in master MVCC Cache 7 
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_MvccCache7?branch=%3Cdefault%3E
 Changes may lead to failure were done by 
 - igor sapego  
https://ci.ignite.apache.org/viewModification.html?modId=907658

 - Here's a reminder of what contributors were agreed to do 
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute 
 - Should you have any questions please contact dev@ignite.apache.org 

Best Regards,
Apache Ignite TeamCity Bot 
https://github.com/apache/ignite-teamcity-bot
Notification generated at 02:11:18 26-09-2020 

Re: New Ignite Docs: Status and Incomplete Items

[Denis Magda]

Pavel,

Alright, I'll do the porting of those pages and you'll take care of
IGNITE-13331 . Let's
split the job.

Nikolay, I'll review your contribution early next week.

Thanks, folks, for the cooperation.

-
Denis


On Thu, Sep 24, 2020 at 11:19 PM Pavel Tupitsyn 
wrote:

> > Do you want me to port those pages or are you going to do it yourself?
> I'm ok either way, any help with this will be greatly appreciated :)
>
> > Are you saying the .NET community no longer uses those?
> Existing integrations are for legacy technologies.
> We are going to remove them in 3.0 [1] and, hopefully, replace them with
> modern equivalents later.
>
> [1]
>
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist
>
> On Fri, Sep 25, 2020 at 2:20 AM Denis Magda  wrote:
>
> > Pavel, thanks for preparing the list of the missing pages. Do you want me
> > to port those pages or are you going to do it yourself?
> >
> > Btw, what's wrong with the 3rd-party integrations? Are you saying the
> .NET
> > community no longer uses those?
> >
> > -
> > Denis
> >
> >
> > On Fri, Sep 18, 2020 at 5:45 AM Pavel Tupitsyn 
> > wrote:
> >
> > > Denis,
> > >
> > > > @Pavel Tupitsyn  ... Are you going to document
> > the
> > > features added in 2.9  <
> > https://issues.apache.org/jira/browse/IGNITE-13331
> > > >
> > >
> > > Yes, I have this on my plate, but the release was postponed so I
> > postponed
> > > the task as well.
> > >
> > >
> > > > is there is anything else you planned to move from readme.io?
> > >
> > > A list of missing things:
> > > - Standalone nodes [1]
> > > - Java detection, known issues [2]
> > > - XML configuration [3]
> > > - Serialization details [4]
> > > - Platform interop [5]
> > > - Deployment [6]
> > > - Troubleshooting [7]
> > > - Assembly loading [8]
> > > - LINQ [9]
> > > - Calling Java services [10]
> > > - Plugins [11]
> > > - Logging [12]
> > >
> > > Also "Third-party integrations", but I consider them legacy, so we can
> > > skip that.
> > >
> > > [1] https://apacheignite-net.readme.io/docs/standalone-nodes
> > > [2] https://apacheignite-net.readme.io/docs/cross-platform-support
> > > [3] https://apacheignite-net.readme.io/docs/configuration
> > > [4] https://apacheignite-net.readme.io/docs/serialization
> > > [5] https://apacheignite-net.readme.io/docs/platform-interoperability
> > > [6] https://apacheignite-net.readme.io/docs/deployment
> > > [7] https://apacheignite-net.readme.io/docs/troubleshooting
> > > [8] https://apacheignite-net.readme.io/docs/zero-deployment
> > > [9] https://apacheignite-net.readme.io/docs/sql-database
> > > [10] https://apacheignite-net.readme.io/docs/calling-java-services
> > > [11] https://apacheignite-net.readme.io/docs/plugins
> > > [12] https://apacheignite-net.readme.io/docs/logging
> > >
> > > On Fri, Sep 18, 2020 at 11:21 AM Ivan Daschinsky 
> > > wrote:
> > >
> > > > Hi! As we introduce CMake build system for Ignite C++ for Linux and
> Mac
> > > OS
> > > > X and this improvement is in ignite 2.9, we should document it.
> (CMake
> > > for
> > > > windows is not ready yet and will be in 2.10)
> > > > I created ticket for it and assigned it to me. Patch will be
> available
> > > > soon.
> > > >
> > > > [1] - https://issues.apache.org/jira/browse/IGNITE-13459
> > > >
> > > > пт, 18 сент. 2020 г. в 09:59, Nikolay Izhikov :
> > > >
> > > > > Hello, Denis.
> > > > >
> > > > > >   • @Nikolay Izhikov, is there any chance you can document
> the
> > > new
> > > > > management commands the next week? Use me as a reviewer.
> > > > >
> > > > > Yes.
> > > > >
> > > > > > 18 сент. 2020 г., в 02:24, Denis Magda 
> > > написал(а):
> > > > > >
> > > > > > Folks,
> > > > > >
> > > > > > While Artem is unavailable, Mauricio and I keep pushing the new
> > docs
> > > > > project to the finish line:
> > > > https://ignite.apache.org/docs/latest/preface
> > > > > >
> > > > > > Overall, we hope to copy the last bits from the readme.io to the
> > new
> > > > > engine, document the release and contribution process, and settle
> > down
> > > > with
> > > > > the search plug-in throughout the next week or so. The docs will be
> > > ready
> > > > > by the time of the 2.9 release.
> > > > > >
> > > > > > But there are some items that need the involvement of some of
> you:
> > > > > >   • @Pavel Tupitsyn, I heard from Artem that you are working
> on
> > > > some
> > > > > .NET-specific tasks. Are you going to document the features added
> in
> > > 2.9
> > > > > and is there is anything else you planned to move from readme.io?
> > > > > >   • @Nikolay Izhikov, is there any chance you can document
> the
> > > new
> > > > > management commands the next week? Use me as a reviewer.
> > > > > >
> > > > > > Once, all the features are documented and old pages are moved
> from
> > > > > readme.io, I'll go ahead and merge the new docs to the master and
> > > > > ignite-2.9 branch.
> > > > > >
> > > > > > -
> > > > > > Denis
> > > 

Re: Hi, Ignite community

[Ivan Pavlukhin]

Hi Kirill,

Welcome to Apache Ignite Community!

I added your JIRA account to the contributor list. A following page can
help you to start and pick a ticket
https://ignite.apache.org/community/contribute.html

Feel free to write a message to dev@ignite.apache.org if you need any
assistance.

2020-09-25 17:25 GMT+03:00, Kirill Gusakov :
> Hello, Ignite Community!
>
> My name is Kirill. I want to contribute to Apache Ignite, my JIRA username
> kgusakov. Any help on this will be appreciated.
>
> Thanks!
>


-- 

Best regards,
Ivan Pavlukhin

Re: Too many messages in log in case of exceptions in user computations.

[Denis Mekhanikov]

Nikolay,

First the error is printed on the map node, then on the reduce node, and
then the exception is thrown from the method that triggered the execution.
The compute grid seems to use the "print an error message and delegate
exception to the caller" which doesn't make much sense.
If you don't know what to do with an error and delegate it to the caller,
what's the point in printing it to log?
This is the kind of information that should only be printed when debug
logging is enabled.

I created a ticket for this issue:
https://issues.apache.org/jira/browse/IGNITE-13487

Denis

пн, 10 авг. 2020 г. в 18:45, Nikolay Izhikov :

> Hello, Vasiliy.
>
> This messages are shown on the different nodes, isn’t it?
>
> > 10 авг. 2020 г., в 18:34, Vasiliy Sisko 
> написал(а):
> >
> > In case of errors in user computations the Ignite Compute Grid produces a
> > lot of errors into the log.
> > In the worst way it produces the next messages:
> >1. Failed to execute job: …
> >2. Failed to reduce job results: …
> >3. Failed to execute task: …
> >
> > There is a suggestion to decrease log level for first and second messages
> > to DEBUG level, because of the third message will still be shown.
> >
> > --
> > Vasiliy Sisko
>
>

[jira] [Created] (IGNITE-13487) Decrease logging level for exceptions throws from compute engine

[Denis Mekhanikov (Jira)]

Denis Mekhanikov created IGNITE-13487:
-

 Summary: Decrease logging level for exceptions throws from compute 
engine
 Key: IGNITE-13487
 URL: https://issues.apache.org/jira/browse/IGNITE-13487
 Project: Ignite
  Issue Type: Improvement
Reporter: Denis Mekhanikov
Assignee: Denis Mekhanikov


When a compute job fails during execution, it leads to two error messages 
printed on different nodes:

1. {{Failed to execute job}} on the map node.
 2. {{Failed to obtain remote job result policy for result from 
ComputeTask.result(..) method (will fail the whole task)}} on the reduce node.

Also an exception is thrown from the {{execute()}} method that triggered this 
task.

It seems that none of these errors should actually be shown to users. This 
information should be printed only if debug logging is enabled for the 
corresponding packages.

The issue can be reproduced by running the following example:
{code:java}
public class ComputeException {
public static void main(String[] args) {
new ComputeException().run();
}

void run() {
IgniteConfiguration igniteCfg = 
Ignition.loadSpringBean("config/ignite.xml", "ignite.cfg");
igniteCfg.setClientMode(true);

try (Ignite ignite = Ignition.start(igniteCfg)) {
ignite.compute(ignite.cluster().forServers()).execute(new 
ErroneousTask(), null);
}
}

public static class ErroneousTask extends ComputeTaskAdapter {
@Override public @NotNull Map 
map(List list,
@Nullable Object o) throws IgniteException {
LinkedHashMap map = new 
LinkedHashMap<>();
for (ClusterNode node : list)
map.put(new ErroneousJob(), node);

return map;
}

@Override public @Nullable Object reduce(List list) 
throws IgniteException {
return null;
}
}

public static class ErroneousJob extends ComputeJobAdapter {
@Override public Object execute() throws IgniteException {
throw new IgniteException("I failed. Sorry :(");
}
}
}
{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Hi, Ignite community

[Kirill Gusakov]

Hello, Ignite Community!

My name is Kirill. I want to contribute to Apache Ignite, my JIRA username
kgusakov. Any help on this will be appreciated.

Thanks!

[jira] [Created] (IGNITE-13485) Java thin: increase test coverage for transactions and partition awareness

[Pavel Tupitsyn (Jira)]

Pavel Tupitsyn created IGNITE-13485:
---

 Summary: Java thin: increase test coverage for transactions and 
partition awareness
 Key: IGNITE-13485
 URL: https://issues.apache.org/jira/browse/IGNITE-13485
 Project: Ignite
  Issue Type: Improvement
  Components: thin client
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.10


Add tests for the following scenarios:
* Partitioned cache with backups
* Serializable transactions (locking behavior)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: JAR-based code deployment

[Taras Ledkov]

Hi,

Great idea, but some points are not clear for me:
- Redeploy and versioning. Does it mean that several versions of the 
code will be prohibited?
- Will there be any additional requirements for the content of the JAR? 
Metadata, security etc.

If yes, then maybe we should talk about Ignte ARchive (IAR) likes WAR.

On 25.09.2020 4:42, Valentin Kulichenko wrote:

Igniters,

During the meetup dedicated to Ignite 3.0 [1], one of the items I've
mentioned was JAR based code deployment, as an alternative to peer class
loading and other mechanisms for code deployment.

As promised, I've started drafting the IEP for this change [2]. Please let
me know your thoughts.

[1]
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0#ApacheIgnite3.0-Meetups
[2]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-59%3A+JAR-based+code+deployment

-Val


--
Taras Ledkov
Mail-To: tled...@gridgain.com

Re: New Ignite Docs: Status and Incomplete Items

[Nikolay Izhikov]

Hello, Igniters.

I’ve prepared two PR for new docs:


https://github.com/apache/ignite/pull/8279 - JOBS system view description.

https://github.com/apache/ignite/pull/8280 - KILL commands description.

Please, review.

> 25 сент. 2020 г., в 09:19, Pavel Tupitsyn  написал(а):
> 
>> Do you want me to port those pages or are you going to do it yourself?
> I'm ok either way, any help with this will be greatly appreciated :)
> 
>> Are you saying the .NET community no longer uses those?
> Existing integrations are for legacy technologies.
> We are going to remove them in 3.0 [1] and, hopefully, replace them with
> modern equivalents later.
> 
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist
> 
> On Fri, Sep 25, 2020 at 2:20 AM Denis Magda  wrote:
> 
>> Pavel, thanks for preparing the list of the missing pages. Do you want me
>> to port those pages or are you going to do it yourself?
>> 
>> Btw, what's wrong with the 3rd-party integrations? Are you saying the .NET
>> community no longer uses those?
>> 
>> -
>> Denis
>> 
>> 
>> On Fri, Sep 18, 2020 at 5:45 AM Pavel Tupitsyn 
>> wrote:
>> 
>>> Denis,
>>> 
 @Pavel Tupitsyn  ... Are you going to document
>> the
>>> features added in 2.9  <
>> https://issues.apache.org/jira/browse/IGNITE-13331
 
>>> 
>>> Yes, I have this on my plate, but the release was postponed so I
>> postponed
>>> the task as well.
>>> 
>>> 
 is there is anything else you planned to move from readme.io?
>>> 
>>> A list of missing things:
>>> - Standalone nodes [1]
>>> - Java detection, known issues [2]
>>> - XML configuration [3]
>>> - Serialization details [4]
>>> - Platform interop [5]
>>> - Deployment [6]
>>> - Troubleshooting [7]
>>> - Assembly loading [8]
>>> - LINQ [9]
>>> - Calling Java services [10]
>>> - Plugins [11]
>>> - Logging [12]
>>> 
>>> Also "Third-party integrations", but I consider them legacy, so we can
>>> skip that.
>>> 
>>> [1] https://apacheignite-net.readme.io/docs/standalone-nodes
>>> [2] https://apacheignite-net.readme.io/docs/cross-platform-support
>>> [3] https://apacheignite-net.readme.io/docs/configuration
>>> [4] https://apacheignite-net.readme.io/docs/serialization
>>> [5] https://apacheignite-net.readme.io/docs/platform-interoperability
>>> [6] https://apacheignite-net.readme.io/docs/deployment
>>> [7] https://apacheignite-net.readme.io/docs/troubleshooting
>>> [8] https://apacheignite-net.readme.io/docs/zero-deployment
>>> [9] https://apacheignite-net.readme.io/docs/sql-database
>>> [10] https://apacheignite-net.readme.io/docs/calling-java-services
>>> [11] https://apacheignite-net.readme.io/docs/plugins
>>> [12] https://apacheignite-net.readme.io/docs/logging
>>> 
>>> On Fri, Sep 18, 2020 at 11:21 AM Ivan Daschinsky 
>>> wrote:
>>> 
 Hi! As we introduce CMake build system for Ignite C++ for Linux and Mac
>>> OS
 X and this improvement is in ignite 2.9, we should document it. (CMake
>>> for
 windows is not ready yet and will be in 2.10)
 I created ticket for it and assigned it to me. Patch will be available
 soon.
 
 [1] - https://issues.apache.org/jira/browse/IGNITE-13459
 
 пт, 18 сент. 2020 г. в 09:59, Nikolay Izhikov :
 
> Hello, Denis.
> 
>>  • @Nikolay Izhikov, is there any chance you can document the
>>> new
> management commands the next week? Use me as a reviewer.
> 
> Yes.
> 
>> 18 сент. 2020 г., в 02:24, Denis Magda 
>>> написал(а):
>> 
>> Folks,
>> 
>> While Artem is unavailable, Mauricio and I keep pushing the new
>> docs
> project to the finish line:
 https://ignite.apache.org/docs/latest/preface
>> 
>> Overall, we hope to copy the last bits from the readme.io to the
>> new
> engine, document the release and contribution process, and settle
>> down
 with
> the search plug-in throughout the next week or so. The docs will be
>>> ready
> by the time of the 2.9 release.
>> 
>> But there are some items that need the involvement of some of you:
>>  • @Pavel Tupitsyn, I heard from Artem that you are working on
 some
> .NET-specific tasks. Are you going to document the features added in
>>> 2.9
> and is there is anything else you planned to move from readme.io?
>>  • @Nikolay Izhikov, is there any chance you can document the
>>> new
> management commands the next week? Use me as a reviewer.
>> 
>> Once, all the features are documented and old pages are moved from
> readme.io, I'll go ahead and merge the new docs to the master and
> ignite-2.9 branch.
>> 
>> -
>> Denis
> 
> 
 
 --
 Sincerely yours, Ivan Daschinskiy
 
>>> 
>> 

Re: JAR-based code deployment

[Ilya Kasnacheev]

Hello!

I don't like reliance on ignitectl utility. It should be available but it
should be accompanied by some Java API in my opinion.

I don't understand how to peer deploy my code if I run a client from my
IDE, along with all dependencies. I think that easy-to-develop is crucial
for any product.

I also think this is a drawback compared to e.g. existing
PeerAssemblyLoading in .Net.

Regards,
-- 
Ilya Kasnacheev


пт, 25 сент. 2020 г. в 04:43, Valentin Kulichenko <
valentin.kuliche...@gmail.com>:

> Igniters,
>
> During the meetup dedicated to Ignite 3.0 [1], one of the items I've
> mentioned was JAR based code deployment, as an alternative to peer class
> loading and other mechanisms for code deployment.
>
> As promised, I've started drafting the IEP for this change [2]. Please let
> me know your thoughts.
>
> [1]
>
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0#ApacheIgnite3.0-Meetups
> [2]
>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-59%3A+JAR-based+code+deployment
>
> -Val
>

Re: Ignite 2.9 Announcement Blog Post

[Alex Plehanov]

Denis,

Ok, I will prepare the text soon.

чт, 24 сент. 2020 г. в 23:36, Denis Magda :

> @Alex Plehanov 
>
> Are you interested in writing a blog post that covers the major
> improvements of the 2.9 release? It will be referenced from the
> announcement email and distributed through other channels. Examples of
> previous articles: https://blogs.apache.org/ignite/
>
> It happened that I was the only one who would write such an article but
> will step down with pleasure if you can take over this task. Once the draft
> is ready, I'll ask a professional technical editor, who reviews my texts,
> to work with you as well.
>
> -
> Denis
>

Re: New Ignite Docs: Status and Incomplete Items

[Pavel Tupitsyn]

> Do you want me to port those pages or are you going to do it yourself?
I'm ok either way, any help with this will be greatly appreciated :)

> Are you saying the .NET community no longer uses those?
Existing integrations are for legacy technologies.
We are going to remove them in 3.0 [1] and, hopefully, replace them with
modern equivalents later.

[1]
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist

On Fri, Sep 25, 2020 at 2:20 AM Denis Magda  wrote:

> Pavel, thanks for preparing the list of the missing pages. Do you want me
> to port those pages or are you going to do it yourself?
>
> Btw, what's wrong with the 3rd-party integrations? Are you saying the .NET
> community no longer uses those?
>
> -
> Denis
>
>
> On Fri, Sep 18, 2020 at 5:45 AM Pavel Tupitsyn 
> wrote:
>
> > Denis,
> >
> > > @Pavel Tupitsyn  ... Are you going to document
> the
> > features added in 2.9  <
> https://issues.apache.org/jira/browse/IGNITE-13331
> > >
> >
> > Yes, I have this on my plate, but the release was postponed so I
> postponed
> > the task as well.
> >
> >
> > > is there is anything else you planned to move from readme.io?
> >
> > A list of missing things:
> > - Standalone nodes [1]
> > - Java detection, known issues [2]
> > - XML configuration [3]
> > - Serialization details [4]
> > - Platform interop [5]
> > - Deployment [6]
> > - Troubleshooting [7]
> > - Assembly loading [8]
> > - LINQ [9]
> > - Calling Java services [10]
> > - Plugins [11]
> > - Logging [12]
> >
> > Also "Third-party integrations", but I consider them legacy, so we can
> > skip that.
> >
> > [1] https://apacheignite-net.readme.io/docs/standalone-nodes
> > [2] https://apacheignite-net.readme.io/docs/cross-platform-support
> > [3] https://apacheignite-net.readme.io/docs/configuration
> > [4] https://apacheignite-net.readme.io/docs/serialization
> > [5] https://apacheignite-net.readme.io/docs/platform-interoperability
> > [6] https://apacheignite-net.readme.io/docs/deployment
> > [7] https://apacheignite-net.readme.io/docs/troubleshooting
> > [8] https://apacheignite-net.readme.io/docs/zero-deployment
> > [9] https://apacheignite-net.readme.io/docs/sql-database
> > [10] https://apacheignite-net.readme.io/docs/calling-java-services
> > [11] https://apacheignite-net.readme.io/docs/plugins
> > [12] https://apacheignite-net.readme.io/docs/logging
> >
> > On Fri, Sep 18, 2020 at 11:21 AM Ivan Daschinsky 
> > wrote:
> >
> > > Hi! As we introduce CMake build system for Ignite C++ for Linux and Mac
> > OS
> > > X and this improvement is in ignite 2.9, we should document it. (CMake
> > for
> > > windows is not ready yet and will be in 2.10)
> > > I created ticket for it and assigned it to me. Patch will be available
> > > soon.
> > >
> > > [1] - https://issues.apache.org/jira/browse/IGNITE-13459
> > >
> > > пт, 18 сент. 2020 г. в 09:59, Nikolay Izhikov :
> > >
> > > > Hello, Denis.
> > > >
> > > > >   • @Nikolay Izhikov, is there any chance you can document the
> > new
> > > > management commands the next week? Use me as a reviewer.
> > > >
> > > > Yes.
> > > >
> > > > > 18 сент. 2020 г., в 02:24, Denis Magda 
> > написал(а):
> > > > >
> > > > > Folks,
> > > > >
> > > > > While Artem is unavailable, Mauricio and I keep pushing the new
> docs
> > > > project to the finish line:
> > > https://ignite.apache.org/docs/latest/preface
> > > > >
> > > > > Overall, we hope to copy the last bits from the readme.io to the
> new
> > > > engine, document the release and contribution process, and settle
> down
> > > with
> > > > the search plug-in throughout the next week or so. The docs will be
> > ready
> > > > by the time of the 2.9 release.
> > > > >
> > > > > But there are some items that need the involvement of some of you:
> > > > >   • @Pavel Tupitsyn, I heard from Artem that you are working on
> > > some
> > > > .NET-specific tasks. Are you going to document the features added in
> > 2.9
> > > > and is there is anything else you planned to move from readme.io?
> > > > >   • @Nikolay Izhikov, is there any chance you can document the
> > new
> > > > management commands the next week? Use me as a reviewer.
> > > > >
> > > > > Once, all the features are documented and old pages are moved from
> > > > readme.io, I'll go ahead and merge the new docs to the master and
> > > > ignite-2.9 branch.
> > > > >
> > > > > -
> > > > > Denis
> > > >
> > > >
> > >
> > > --
> > > Sincerely yours, Ivan Daschinskiy
> > >
> >
>