Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

[Maxim Muzafarov]

Folks,

I've marked all the valuable features of 2.10 release with an
appropriate label. Please, let me know if I've missed anything.

Here is the link to the JIRA:
https://s.apache.org/1hyfu


On Thu, 12 Nov 2020 at 12:28, Anton Vinogradov  wrote:
>
> > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > Vinogradov, Ivan Daschinskiy)
> > Will all related issues be included in the 2.10?
> We're at the final preparations phase. Going to start the merge discussion
> soon.
>
> On Wed, Nov 11, 2020 at 4:48 PM Alexey Zinoviev 
> wrote:
>
> > Yes, Model Export/Import for ML will be finished, now it's ready, but under
> > testing on my side.
> >
> > ср, 11 нояб. 2020 г. в 16:08, Nikolay Izhikov :
> >
> > > I suggest to include CDC feature to the 2.10 scope.
> > >
> > > > 11 нояб. 2020 г., в 16:06, Maxim Muzafarov 
> > > написал(а):
> > > >
> > > > Igniters,
> > > >
> > > >
> > > > Can you clarify the issue statuses according to the Apache Ignite
> > > > Roadmap [1] and the 2.10 Apache Ignite Release? Here are some major
> > > > issues which are expected to be included in 2.10 with the unknown
> > > > status:
> > > >
> > > > - Distributed environment tests [2] (Nikolay Izhikov, Anton
> > > > Vinogradov, Ivan Daschinskiy)
> > > > Will all related issues be included in the 2.10?
> > > >
> > > > - Native persistence defragmentation [6][7] (Anton Kalashnikov, Sergey
> > > Chugunov)
> > > > Are we on the last mile with this for 2.10?
> > > >
> > > > - Consistency-related improvements for atomic caches [3] (Alexey
> > > Scherbakov)
> > > > Do we have the JIRA issue? Will the issue be included in 2.10?
> > > >
> > > > - Tombstone objects during rebalancing [4] (Alexey Scherbakov)
> > > > The issue [4] is in progress state. Will it be finished prior to code
> > > freeze?
> > > >
> > > > - SQL runtime statistics (Konstantin Orlov)
> > > > Do we have an IEP for this or JIRA issue?
> > > >
> > > > - ML Model export/import [5] (Alexey Zinoviev)
> > > > - Will the issue be finished?
> > > >
> > > >
> > > > [1]
> > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap
> > > > [2]
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-56%3A+Distributed+environment+tests
> > > > [3]
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again
> > > > [4] https://issues.apache.org/jira/browse/IGNITE-11704
> > > > [5] https://issues.apache.org/jira/browse/IGNITE-6642
> > > > [6] https://issues.apache.org/jira/browse/IGNITE-13143
> > > > [7]
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation
> > > >
> > > > On Tue, 10 Nov 2020 at 15:58, Maxim Muzafarov 
> > wrote:
> > > >>
> > > >> Folks,
> > > >>
> > > >> I've created the release page on the Confluence. Feel free to mail in
> > > >> case of any errors.
> > > >>
> > > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10
> > > >>
> > > >> On Fri, 6 Nov 2020 at 17:56, Maxim Muzafarov 
> > wrote:
> > > >>>
> > > >>> Igniters,
> > > >>>
> > > >>>
> > > >>> Let's finalize the discussion [1] about the next upcoming major
> > Apache
> > > >>> Ignite 2.10  release. The major improvements related to the proposed
> > > >>> release:
> > > >>> - Improvements for partition clearing related parts
> > > >>> - Add tracing of SQL queries.
> > > >>> - CPP: Implement Cluster API
> > > >>> - .NET: Thin client: Transactions
> > > >>> - .NET: Thin Client: Continuous Query
> > > >>> - Java Thin client Kubernetes discovery
> > > >>>
> > > >>> etc.
> > > >>> Total: 166 RESOLVED issues [2].
> > > >>>
> > > >>>
> > > >>> Let's start the discussion about Time and Scope, and also I propose
> > > >>> myself as the release manager of the Apache Ignite 2.10. If you'd
> > like
> > > >>> to lead this release, please, let us know, I see no problems to chose
> > > >>> a better candidate.
> > > >>>
> > > >>>
> > > >>> Proposed release timeline:
> > > >>>
> > > >>> Scope Freeze: December 10, 2020
> > > >>> Code Freeze: December 24, 2020
> > > >>> Voting Date: January 18, 2021
> > > >>> Release Date: January 25, 2021
> > > >>>
> > > >>>
> > > >>> Proposed release scope:
> > > >>> [2]
> > > >>>
> > > >>>
> > > >>> WDYT?
> > > >>>
> > > >>>
> > > >>> [1]
> > >
> > http://apache-ignite-developers.2346864.n4.nabble.com/2-9-1-release-proposal-tp49769p49867.html
> > > >>> [2]
> > >
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.10%20and%20status%20in%20(Resolved%2C%20Closed)%20and%20resolution%20%3D%20Fixed%20order%20by%20priority%20
> > >
> > >
> >

Re: [REVIEW REQUEST] IEP-47 Native Persistence Defragmentation, core logic

[Ivan Bessonov]

Denis,

chances that feature will be fully complete is a bit low. We still make
adjustments to the API
and we need a few optimizations so that it would work faster.

чт, 12 нояб. 2020 г. в 19:11, Denis Magda :

> Ivan,
>
> Nice! Is the plan to get it added to Ignite 2.10?
>
> -
> Denis
>
>
> On Thu, Nov 12, 2020 at 7:11 AM Ivan Bessonov 
> wrote:
>
> > Hi Igniters,
> >
> > Core functionality of defragmentation is finally implemented in [1].
> > There's no public API in it
> > for now, patch is already very big and had to be split into smaller tasks
> > (that consist mostly of refactoring).
> >
> > Code is a little rough right now, I'm gonna go through all the remaining
> > TODO, but you can already
> > start reviewing it. PR is here: [2].
> >
> > First control.sh commands are here, but I don't have TC test results yet:
> > [3].
> > There will be more API related issues later, but now I'd like to polish
> > core classes.
> >
> > Please leave your thoughts here and in PR.
> >
> > Thank you!
> >
> > [0]
> >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation
> > [1] https://issues.apache.org/jira/browse/IGNITE-13190
> > [2] https://github.com/apache/ignite/pull/7984/files
> > [3] https://issues.apache.org/jira/browse/IGNITE-13697
> >
> > --
> > Sincerely yours,
> > Ivan Bessonov
> >
>


-- 
Sincerely yours,
Ivan Bessonov

Re: [DISCUSS] Missed (non-suited) tests

[Ilya Kasnacheev]

Hello!

I have left some comments and there's also more discussion there. Can you
please look?

Thanks,
-- 
Ilya Kasnacheev


вт, 3 нояб. 2020 г. в 00:03, Max Timonin :

> Hi!
>
> I've updated PR: https://github.com/apache/ignite/pull/8367. Anton, Ivan,
> Ivan could you please review it?
>
> Some moments to mention:
> 1. I've added new suites: SerializerSuite (ignite-cassandra-serializers),
> DistanceTestSuite, NaiveBayesTestSuite (ignite-ml). Should we configure a
> TeamCity to run them?
>
> 2. Some tests marked as failed, I'll create corresponding tickets for them
> after PR approved:
> - IgnitePKIndexesMigrationToUnwrapPkTest
> - P2PGridifySelfTest
> - GridCacheMultithreadedFailoverAbstractTest
> - WalCompactionAfterRestartTest
> - GridTcpCommunicationSpiLogTest
> - ComplexSecondaryKeyUnwrapSelfTest
> - SqlTransactionsSelfTest
>
> 3. Add docs to DEVNOTES.txt
>
> On Mon, Nov 2, 2020 at 11:44 AM Anton Vinogradov  wrote:
>
> > > As I understand we
> > > can't just move suites between modules, as TeamCity may depend on the
> > path
> > > to them.
> > See no problem to update TC as well.
> >
> > On Fri, Oct 30, 2020 at 4:32 PM Ivan Daschinsky 
> > wrote:
> >
> > > I suggests to mark these tests with @Ignore and file tickets to fix
> them.
> > >
> > > пт, 30 окт. 2020 г. в 16:26, Ivan Daschinsky :
> > >
> > > > Hi
> > > >
> > > > WalCompactionAfterRestartTest -- yes we need it. This test failed
> > because
> > > > of race (test shold be rewritten a little bit)
> > > >
> > > > пт, 30 окт. 2020 г. в 16:15, Max Timonin :
> > > >
> > > >> Hi!
> > > >>
> > > >> Yes, you're correct. I've developed the check and started to clean
> > tests
> > > >> (move them to suites, mark some tests with Ignore, etc.). I finish
> > work
> > > on
> > > >> the core module. I hope it was the biggest one, and others are less.
> > If
> > > >> so,
> > > >> I think I will finish the work on other modules in 1 or 2 weeks, as
> I
> > do
> > > >> this activity in the background (~10% of my work time). Actually
> I've
> > > >> found
> > > >> 3 failed tests in the core module that aren't in any suite, so I
> need
> > > time
> > > >> to discover reason of failures and if we actually need those tests:
> > > >>
> > > >> GridCacheMultithreadedFailoverAbstractTest
> > > >> WalCompactionAfterRestartTest
> > > >> GridTcpCommunicationSpiLogTest
> > > >>
> > > >> Also we should decide how to be with wrongly located es. As I
> > understand
> > > >> we
> > > >> can't just move suites between modules, as TeamCity may depend on
> the
> > > path
> > > >> to them. So, for such cases I've just created suites in the right
> > > module,
> > > >> and replaced the test list with the new class suite. It does not
> look
> > > >> pretty enough, but I think It's a path of least resistance. WDYT?
> > > >>
> > > >> BEFORE:
> > > >> Module A -> SuiteA -> testA1, testA2, testB1, testB2
> > > >> Module B -> testB1, testB2
> > > >>
> > > >> AFTER:
> > > >> Module A -> SuiteA, SuiteB
> > > >> Module B -> SuiteB -> testB1, testB2
> > > >>
> > > >> On Fri, Oct 30, 2020 at 3:38 PM Anton Vinogradov 
> > wrote:
> > > >>
> > > >> > Folks,
> > > >> > What's the current state of this thread?
> > > >> > AFAIU, we found unused and wrongly located tests and developed
> some
> > > >> > checker, could we split this to some PRs?
> > > >> > Let's merge tests usage fix and location fixes first, this will
> > > provide
> > > >> us
> > > >> > an ability to automate check using Travis.
> > > >> >
> > > >> > On Tue, Oct 20, 2020 at 12:06 PM Ivan Pavlukhin <
> > vololo...@gmail.com>
> > > >> > wrote:
> > > >> >
> > > >> > > Max, Ivan,
> > > >> > >
> > > >> > > Using explicit @Ignore and the automated check sounds good to
> me.
> > If
> > > >> > > nobody has arguments against it I think we should do it.
> > > >> > >
> > > >> > > 2020-10-19 19:30 GMT+03:00, Max Timonin <
> timonin.ma...@gmail.com
> > >:
> > > >> > > > Hi Ivan,
> > > >> > > >
> > > >> > > > I've checked the ticket you provide. It contains subtasks to
> > > >> uncomment
> > > >> > or
> > > >> > > > to remove some unused tests. It definitely describes some
> cases
> > > I've
> > > >> > > found.
> > > >> > > > So what do you think if I uncomment them in suites, add
> @Ignore
> > > >> > > annotation
> > > >> > > > for those tests while the tickets are open? This will help to
> > find
> > > >> out
> > > >> > > > tests that were forgiven in a recent time.
> > > >> > > >
> > > >> > > > Also I believe that this check must be automated. I didn't
> find
> > a
> > > >> way
> > > >> > how
> > > >> > > > uncomment / unused tests are found in the ticket. If there is
> no
> > > >> any -
> > > >> > I
> > > >> > > > propose mine PR for this purpose.
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > On Mon, Oct 19, 2020 at 5:24 PM Ivan Daschinsky <
> > > >> ivanda...@gmail.com>
> > > >> > > > wrote:
> > > >> > > >
> > > >> > > >> Ivan, as far as I understand, Max also created verification
> > check
> > > >> for
> > > >> > > not
> > > >> 

[jira] [Created] (IGNITE-13711) Exception is discarded in GridCacheProcessor

[Ilya Kasnacheev (Jira)]

Ilya Kasnacheev created IGNITE-13711:


 Summary: Exception is discarded in GridCacheProcessor
 Key: IGNITE-13711
 URL: https://issues.apache.org/jira/browse/IGNITE-13711
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Reporter: Ilya Kasnacheev


{code}
locJoinCtx.initCaches()
 .forEach(cacheDesc -> {
  try {
   ctx.query().initQueryStructuresForNotStartedCache(cacheDesc);
  }
  catch (Exception e) {
   log.error("Can't initialize query structures for not started cache 
[cacheName=" + cacheDesc.cacheName() + "]");
  }
 });
{code}



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

Re: [REVIEW REQUEST] IEP-47 Native Persistence Defragmentation, core logic

[Ivan Bessonov]

But maybe I just don't know the date. To be short - right now
defragmentation is my first priority.

вт, 17 нояб. 2020 г. в 15:18, Ivan Bessonov :

> Denis,
>
> chances that feature will be fully complete is a bit low. We still make
> adjustments to the API
> and we need a few optimizations so that it would work faster.
>
> чт, 12 нояб. 2020 г. в 19:11, Denis Magda :
>
>> Ivan,
>>
>> Nice! Is the plan to get it added to Ignite 2.10?
>>
>> -
>> Denis
>>
>>
>> On Thu, Nov 12, 2020 at 7:11 AM Ivan Bessonov 
>> wrote:
>>
>> > Hi Igniters,
>> >
>> > Core functionality of defragmentation is finally implemented in [1].
>> > There's no public API in it
>> > for now, patch is already very big and had to be split into smaller
>> tasks
>> > (that consist mostly of refactoring).
>> >
>> > Code is a little rough right now, I'm gonna go through all the remaining
>> > TODO, but you can already
>> > start reviewing it. PR is here: [2].
>> >
>> > First control.sh commands are here, but I don't have TC test results
>> yet:
>> > [3].
>> > There will be more API related issues later, but now I'd like to polish
>> > core classes.
>> >
>> > Please leave your thoughts here and in PR.
>> >
>> > Thank you!
>> >
>> > [0]
>> >
>> >
>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation
>> > [1] https://issues.apache.org/jira/browse/IGNITE-13190
>> > [2] https://github.com/apache/ignite/pull/7984/files
>> > [3] https://issues.apache.org/jira/browse/IGNITE-13697
>> >
>> > --
>> > Sincerely yours,
>> > Ivan Bessonov
>> >
>>
>
>
> --
> Sincerely yours,
> Ivan Bessonov
>


-- 
Sincerely yours,
Ivan Bessonov

[jira] [Created] (IGNITE-13712) Simple application integrating dynamic configuration

[Sergey Chugunov (Jira)]

Sergey Chugunov created IGNITE-13712:


 Summary: Simple application integrating dynamic configuration
 Key: IGNITE-13712
 URL: https://issues.apache.org/jira/browse/IGNITE-13712
 Project: Ignite
  Issue Type: Sub-task
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov


Apache Ignite node and cluster configurations include many use-cases of varying 
complexity.

To explore how different use-cases work based on new dynamic configuration a 
sample application needs to be developed.

The application should support basic and more complicated configurations, exact 
list of configurations will be provided later.



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

[jira] [Created] (IGNITE-13713) [ML] Add target encoding preprocessor

[Mark Andreev (Jira)]

Mark Andreev created IGNITE-13713:
-

 Summary: [ML] Add target encoding preprocessor
 Key: IGNITE-13713
 URL: https://issues.apache.org/jira/browse/IGNITE-13713
 Project: Ignite
  Issue Type: Improvement
  Components: ml
Reporter: Mark Andreev
Assignee: Mark Andreev
 Fix For: 2.10


I suggest to add target encoding processor based on "Daniele Miccii-Barreca 
(2001). A Preprocessing Scheme for High-Cardinality Categorical Attributes in 
Classification and Prediction Problems. SIGKDD Explor. Newsl. 3, 1. From 
http://dx.doi.org/10.1145/507533.507538"; and implemented in 
"scikit-learn-contrib/category_encoders" as TargetEncoder 
([https://github.com/scikit-learn-contrib/category_encoders/blob/master/category_encoders/target_encoder.py).]



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

[jira] [Created] (IGNITE-13714) [ML] Add catboost inference integration

[Mark Andreev (Jira)]

Mark Andreev created IGNITE-13714:
-

 Summary: [ML] Add catboost inference integration
 Key: IGNITE-13714
 URL: https://issues.apache.org/jira/browse/IGNITE-13714
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.10
Reporter: Mark Andreev
Assignee: Mark Andreev


I suggest to add catboost (https://catboost.ai/) inference to ignite ml. We can 
use catboost java wrapper 
([https://catboost.ai/docs/concepts/java-package.html)] . Size of catboost.jar 
is 6.4 MB.

 

Catboost use [ Apache-2.0 
License|https://github.com/catboost/catboost/blob/master/LICENSE]. 



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

Re: [jira] [Created] (IGNITE-13714) [ML] Add catboost inference integration

[Alexey Zinoviev]

Great, assign it, and go ahead

вт, 17 нояб. 2020 г., 18:48 Mark Andreev (Jira) :

> Mark Andreev created IGNITE-13714:
> -
>
>  Summary: [ML] Add catboost inference integration
>  Key: IGNITE-13714
>  URL: https://issues.apache.org/jira/browse/IGNITE-13714
>  Project: Ignite
>   Issue Type: Improvement
> Affects Versions: 2.10
> Reporter: Mark Andreev
> Assignee: Mark Andreev
>
>
> I suggest to add catboost (https://catboost.ai/) inference to ignite ml.
> We can use catboost java wrapper ([
> https://catboost.ai/docs/concepts/java-package.html)] . Size of
> catboost.jar is 6.4 MB.
>
>
>
> Catboost use [ Apache-2.0 License|
> https://github.com/catboost/catboost/blob/master/LICENSE].
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)
>

Re: [jira] [Created] (IGNITE-13713) [ML] Add target encoding preprocessor

[Alexey Zinoviev]

Will wait a PR to make a review

вт, 17 нояб. 2020 г., 18:24 Mark Andreev (Jira) :

> Mark Andreev created IGNITE-13713:
> -
>
>  Summary: [ML] Add target encoding preprocessor
>  Key: IGNITE-13713
>  URL: https://issues.apache.org/jira/browse/IGNITE-13713
>  Project: Ignite
>   Issue Type: Improvement
>   Components: ml
> Reporter: Mark Andreev
> Assignee: Mark Andreev
>  Fix For: 2.10
>
>
> I suggest to add target encoding processor based on "Daniele
> Miccii-Barreca (2001). A Preprocessing Scheme for High-Cardinality
> Categorical Attributes in Classification and Prediction Problems. SIGKDD
> Explor. Newsl. 3, 1. From http://dx.doi.org/10.1145/507533.507538"; and
> implemented in "scikit-learn-contrib/category_encoders" as TargetEncoder ([
> https://github.com/scikit-learn-contrib/category_encoders/blob/master/category_encoders/target_encoder.py)
> .]
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)
>

Re: Live coding session next week

[Kseniya Romanova]

That was really fun! We should definitely repeat in January or February.
Thanks for participating!

Video: https://youtu.be/RsqeIaQfSpc
Project: https://github.com/vkulichenko/code-session
Article about data distribution in Apache Ignite:
https://www.gridgain.com/resources/blog/data-distribution-in-apache-ignite

Don't miss our next meetup. We will have a use-case from the bank and
how-to about Ignite + Drools
RVSP here:
https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/274647932/


пт, 13 нояб. 2020 г. в 16:13, Kseniya Romanova :

> Hi Ilya! You can see the meeting link after RVSP on meetup.com
> https://www.meetup.com/Apache-Ignite-Virtual-Meetup/events/273935662/
> This mailing list is open and to announce the zoom link is not the best
> thing to do. I can not understand why it's fun to interrupt zoom calls, but
> some people (and bots) do that all the time. Just this week Reactive Summit
> had to change the platform for Q&A because of this.
>
> BTW I fixed several timezones in the event description, sorry if I mislead
> someone. Just forgot about changing summertime back.
>
> пт, 13 нояб. 2020 г. в 05:31, Ilya Kazakov :
>
>> Hello Valentin!
>>
>> Could you provide a link for a meeting, please?
>>
>> -
>> Ilya Kazakov
>>
>> пт, 13 нояб. 2020 г. в 07:07, Valentin Kulichenko <
>> valentin.kuliche...@gmail.com>:
>>
>> > Igniters,
>> >
>> > On Tuesday next week (Nov 17), Denis Magda and I will conduct a live
>> > coding session, where we will implement a primitive Ignite-like
>> distributed
>> > database from scratch. We will demonstrate major components required for
>> > such a system, show how they interact with each other and how they can
>> be
>> > implemented in Java.
>> >
>> > Join if you would like to better understand how distributed systems work
>> > under the hood, or if you simply want to have some fun :)
>> >
>> > RSVP and all the details here: Tuesday, November 17, 2020
>> > 8:00 AM to 10:00 AM PST
>> >
>> > -Val
>> >
>>
>

[jira] [Created] (IGNITE-13715) ComputeScheduleExample doesn't work

[Vyacheslav Koptilin (Jira)]

Vyacheslav Koptilin created IGNITE-13715:


 Summary: ComputeScheduleExample doesn't work
 Key: IGNITE-13715
 URL: https://issues.apache.org/jira/browse/IGNITE-13715
 Project: Ignite
  Issue Type: Bug
  Components: examples
Reporter: Vyacheslav Koptilin
Assignee: Vyacheslav Koptilin


{{ComputeScheduleExample}} does not work due to invalid CRON expression.

Steps to reproduce:
 # Start {{ExampleNodeStartup}}
 # Run {{ComputeScheduleExample}}

Node output:
{noformat}
[00:08:02] Ignite node started OK (id=821d7a9c)
[00:08:02] Topology snapshot [ver=1, locNode=821d7a9c, servers=1, clients=0, 
state=ACTIVE, CPUs=8, offheap=3.2GB, heap=3.5GB]
[00:08:02]   ^-- Baseline [id=0, size=1, online=1, offline=0]
[00:08:32] Joining node doesn't have stored group keys 
[node=fb94c1cf-1fa4-4049-880d-19fa4dd590ce]
[00:08:32] Topology snapshot [ver=2, locNode=821d7a9c, servers=2, clients=0, 
state=ACTIVE, CPUs=8, offheap=6.4GB, heap=7.1GB]
[00:08:32]   ^-- Baseline [id=0, size=2, online=2, offline=0]
[00:08:33] Topology snapshot [ver=3, locNode=821d7a9c, servers=1, clients=0, 
state=ACTIVE, CPUs=8, offheap=3.2GB, heap=3.5GB]
[00:08:33]   ^-- Baseline [id=0, size=1, online=1, offline=0]
{noformat}


{noformat}
[00:08:33] Ignite node started OK (id=fb94c1cf)
[00:08:33] Topology snapshot [ver=2, locNode=fb94c1cf, servers=2, clients=0, 
state=ACTIVE, CPUs=8, offheap=6.4GB, heap=7.1GB]
[00:08:33]   ^-- Baseline [id=0, size=2, online=2, offline=0]

Compute schedule example started.

>>> Schedule future is done and has been unscheduled.
>>> Check all nodes for hello message output.
[00:08:33] Ignite node stopped OK [uptime=00:00:00.085]

Process finished with exit code 0
{noformat}

The log of the first node does not contain the required message.
Also, there is no error message in the example's output.

The root cause of the issue is the invalid CRON expression that is used by the 
example: "{9, 5, 3} * * * * *"
In accordance with the doc 
https://apacheignite.readme.io/docs/cron-based-scheduling#syntax-extension it 
should be the following: "{5, 3} * * * * *"



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

[jira] [Created] (IGNITE-13716) control.sh shows passwords in the output

[Vyacheslav Koptilin (Jira)]

Vyacheslav Koptilin created IGNITE-13716:


 Summary: control.sh shows passwords in the output
 Key: IGNITE-13716
 URL: https://issues.apache.org/jira/browse/IGNITE-13716
 Project: Ignite
  Issue Type: Bug
  Components: control.sh
Reporter: Vyacheslav Koptilin
Assignee: Vyacheslav Koptilin


The control utility shows passwords in the output.
For instance, the "activate" command produces the following output:
{noformat}
Control utility [ver. 2.10.0-SNAPSHOT#20201117-sha1:DEV]
2020 Copyright(C) Apache Software Foundation
User: Vyacheslav Koptilin
Time: 2020-11-18T01:24:44.699
Warning: --keystore-password is insecure. Whenever possible, use interactive 
prompt for password (just discard --keystore-password option).
Command [ACTIVATE] started
Arguments: --keystore 
C:\projects\incubator-ignite\modules\clients\src\test\keystore\node01.jks 
--keystore-password 123456 --ssl-cipher-suites 
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 
--activate --yes

Command deprecated. Use --set-state instead.
Cluster activated
Command [ACTIVATE] finished with code: 0
Control utility has completed execution at: 2020-11-18T01:24:45.998
Execution time: 1299 ms
{noformat}

All passwords should be hidden.



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

Alex Plehanov joins Ignite Project Management Committee

[Denis Magda]

Igniters,

The Project Management Committee (PMC) for Apache Ignite
has invited Alex to become a PMC member and we are pleased to announce that
he has accepted.

Alex joined our community back in 2018 and became one of the key community
members.
He made numerous contributions

since
then, was driving Ignite 2.9 as a release manager, regularly participates
in the dev lists discussions pertaining to the future and evolution of
Ignite.

Join me in congratulating Alex!


-
Denis

Re: Alex Plehanov joins Ignite Project Management Committee

[Saikat Maitra]

Congratulations Alex!!!

On Tue, 17 Nov 2020 at 6:26 PM, Denis Magda  wrote:

> Igniters,
>
> The Project Management Committee (PMC) for Apache Ignite
> has invited Alex to become a PMC member and we are pleased to announce that
> he has accepted.
>
> Alex joined our community back in 2018 and became one of the key community
> members.
> He made numerous contributions
> <
> https://issues.apache.org/jira/browse/IGNITE-13595?jql=project%20%3D%20Ignite%20and%20assignee%20%3D%20alex_pl%20and%20status%20in%20(Closed%2C%20Resolved)
> >
> since
> then, was driving Ignite 2.9 as a release manager, regularly participates
> in the dev lists discussions pertaining to the future and evolution of
> Ignite.
>
> Join me in congratulating Alex!
>
>
> -
> Denis
>

Re: IGNITE-12951 Update documents for migrated extensions

[Saikat Maitra]

Hi Denis,

Yes, I will make a PR to update docs in ignite-website repo as well.

That will cover remaining scope of the jira issue.

Regards,
Saikat

On Mon, 16 Nov 2020 at 9:24 PM, Denis Magda  wrote:

> Got it. Didn't pay attention that those changes were in the readme.txt
> files.
>
> Are you adjusting the docs on the website as well? I bet you were
> submitting a pull-request earlier.
>
> -
> Denis
>
>
> On Mon, Nov 16, 2020 at 6:31 PM Saikat Maitra 
> wrote:
>
> > Hi Denis,
> >
> > My thoughts are that these README.txt files will be published as part of
> > source releases for Ignite Extensions.
> >
> > Regards,
> > Saikat
> >
> > On Mon, Nov 16, 2020 at 5:28 PM Denis Magda  wrote:
> >
> > > Hi Saikat,
> > >
> > > Please go ahead with the merge. Do we need to publish this for the
> Ignite
> > > 2.9 docs at some point? Guess, after the extensions are released under
> > > different names.
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Sun, Nov 15, 2020 at 9:57 AM Saikat Maitra  >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > As discussed I have updated the PR
> > > > https://github.com/apache/ignite-extensions/pull/30
> > > >
> > > > Please review and share your feedback.
> > > >
> > > > Regards,
> > > > Saikat
> > > >
> > > > On Mon, Nov 9, 2020 at 6:38 PM Saikat Maitra <
> saikat.mai...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Nikolay,
> > > > >
> > > > > Thank you for reviewing the changes. I have made changes only in
> the
> > > > > README.txt file and updated the artifactId so that it matches with
> > > > pom.xml.
> > > > >
> > > > > I have also updated the version details in the PR so that it
> matches
> > > with
> > > > > our release version.
> > > > >
> > > > > https://github.com/apache/ignite-extensions/pull/30
> > > > >
> > > > > With respect to naming convention I was thinking we would not be
> > > required
> > > > > to change the groupId and we will only change the artifactId
> similar
> > to
> > > > > spring-boot-autoconfigure-ext module.
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/ignite-extensions/blob/master/modules/spring-boot-autoconfigure-ext/pom.xml#L33
> > > > >
> > > > > Please review and let me know your thoughts.
> > > > >
> > > > > Regards,
> > > > > Saikat
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Nov 9, 2020 at 12:32 AM Nikolay Izhikov <
> nizhi...@apache.org
> > >
> > > > > wrote:
> > > > >
> > > > >> Hello, Saikat.
> > > > >>
> > > > >> As far as I can see you changed artifactId of the extensions not
> > only
> > > > >> docs.
> > > > >>
> > > > >> Do we have an agreement to name each extension as
> > > «{extension-name}-ext»
> > > > >> like «ignite-camel-ext» or similar?
> > > > >> We don’t have much extensions release, so maybe it will be better
> to
> > > > have
> > > > >> naming like
> > > > >>
> > > > >> groupId=org.apache.ignite.extensions
> > > > >> artifactId=ignite-camel
> > > > >>
> > > > >> What do you think?
> > > > >>
> > > > >>
> > > > >> > 9 нояб. 2020 г., в 05:36, Saikat Maitra <
> saikat.mai...@gmail.com>
> > > > >> написал(а):
> > > > >> >
> > > > >> > Hi,
> > > > >> >
> > > > >> > I have raised a PR for the following issue.
> > > > >> >
> > > > >> > Jira : https://issues.apache.org/jira/browse/IGNITE-12951
> > > > >> > PR : https://github.com/apache/ignite-extensions/pull/30
> > > > >> >
> > > > >> > This is an initial PR in Ignite Extensions repo. I will work on
> > > > another
> > > > >> PR
> > > > >> > in ignite repo for the remaining changes.
> > > > >> >
> > > > >> > Regards,
> > > > >> > Saikat
> > > > >>
> > > > >>
> > > >
> > >
> >
>

[MTCGA]: new failures in builds [5738981] 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.

 *New Critical Failure in master Cache (Restarts) 1 
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CacheRestarts1?branch=%3Cdefault%3E
 No changes in the build

 - 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 05:52:42 18-11-2020 

[jira] [Created] (IGNITE-13717) Additional test coverage for calcite engine.

[Stanilovsky Evgeny (Jira)]

Stanilovsky Evgeny created IGNITE-13717:
---

 Summary: Additional test coverage for calcite engine.
 Key: IGNITE-13717
 URL: https://issues.apache.org/jira/browse/IGNITE-13717
 Project: Ignite
  Issue Type: Improvement
  Components: sql
Affects Versions: 2.9
Reporter: Stanilovsky Evgeny
Assignee: Stanilovsky Evgeny


We need to expand current calcite engine tests coverage. 



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

[jira] [Created] (IGNITE-13718) REST API to manage configuration

[Sergey Chugunov (Jira)]

Sergey Chugunov created IGNITE-13718:


 Summary: REST API to manage configuration
 Key: IGNITE-13718
 URL: https://issues.apache.org/jira/browse/IGNITE-13718
 Project: Ignite
  Issue Type: Sub-task
Reporter: Sergey Chugunov


Application developed in IGNITE-13712 should expose REST API for managing 
configuration and integrate with command-line tool prototype from IGNITE-13610.



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