Re: Change TC trigger from Run All to per-project basis

[Pavel Tupitsyn]

Dmitry, thanks for the explanation, this makes sense.

1) Certainly can be helpful.
2) I would include "Platform .NET Core Linux": does not require win agent,
runs 15 min, covers most functionality.

Pavel

On Wed, Feb 21, 2018 at 12:12 AM, Dmitry Pavlov 
wrote:

> Hi Pavel,
>
> WDYT,
> 1) is it needed to prepare wiki article describing tests and chains we
> have, e.g. describe
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_
> RunBasicTests
> and
> its difference with RunAll; which chain to use in each case?
>
> 2) Which .Net test suite may be applicable to be included into 'run basic
> tests' (requires <30 min to run, no failed test, no flaky test with fail
> rate >1%) ?
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 19 февр. 2018 г. в 0:39, Pavel Tupitsyn :
>
> > Igniters,
> >
> > Currently we have a TeamCity trigger only on Run All aggregating project:
> >
> > https://ci.ignite.apache.org/admin/editTriggers.html?id=
> buildType:IgniteTests24Java8_RunAll
> >
> > Each change triggers it's own full run. If new changes are added while
> some
> > builds are queued,
> > these changes are not picked up, and a separate run is scheduled.
> >
> > At this very moment I see over 600 queued builds, all on master branch
> from
> > some trigger.
> > Previously we had a trigger per-project, which seems to be more
> efficient.
> >
> > Thoughts?
> >
> > Pavel
> >
>

Re: Broken tests after IGNITE-7594 merge

[Pavel Tupitsyn]

Merged to master, cherry-picked to ignite-2.4.

Thanks everyone!

On Wed, Feb 21, 2018 at 12:16 AM, Dmitry Pavlov 
wrote:

> Ilya, thank you from me too for such a fast issue resolution.
>
> Pavel, could you please merge this PR to master? Or please advice who else
> can?
>
> Anton V. could you help?
>
> вт, 20 февр. 2018 г. в 19:11, Pavel Tupitsyn :
>
> > Ilya, thanks for the fix, looks good to me.
> > Please make sure TC passes and merge.
> >
> > On Tue, Feb 20, 2018 at 6:08 PM, Dmitriy Pavlov 
> > wrote:
> >
> > > Issue is not in 'patch available' state.
> > >
> > > On Tue, Feb 20, 2018 at 6:06 PM Ilya Lantukh 
> > > wrote:
> > >
> > >> Fixed, please review: https://issues.apache.org/
> jira/browse/IGNITE-7767
> > .
> > >>
> > >> On Tue, Feb 20, 2018 at 5:44 PM, Ilya Lantukh 
> > >> wrote:
> > >>
> > >>> Pavel,
> > >>>
> > >>> I've fixed default value for WALMode (https://github.com/apache/
> > >>> ignite/pull/3544), but now I have the following test failure:
> > >>> Apache.Ignite.Core.Tests.IgniteConfigurationTest.
> > >>> TestDefaultConfigurationProperties
> > >>>
> > >>>   Expected: LogOnly
> > >>>   But was:  Fsync
> > >>>
> > >>>at NUnit.Framework.Assert.That(Object actual, IResolveConstraint
> > >>> expression, String message, Object[] args)
> > >>>at Apache.Ignite.Core.Tests.IgniteConfigurationTest.
> > >>> CheckDefaultProperties(DataStorageConfiguration cfg) in
> > >>> C:\Projects\ignite\modules\platforms\dotnet\Apache.
> Ignite.Core.Tests\
> > >>> IgniteConfigurationTest.cs:line 551
> > >>>at Apache.Ignite.Core.Tests.IgniteConfigurationTest.
> > >>> TestDefaultConfigurationProperties() in C:\Projects\ignite\modules\
> > >>>
> > platforms\dotnet\Apache.Ignite.Core.Tests\IgniteConfigurationTest.cs:
> line
> > >>> 68
> > >>>
> > >>> Could you please take a look and help us understand why did it
> happen?
> > >>>
> > >>> On Tue, Feb 20, 2018 at 4:48 PM, Pavel Tupitsyn <
> ptupit...@apache.org>
> > >>> wrote:
> > >>>
> >  Ilya,
> > 
> >  Please see modules/platforms/dotnet/Apache.Ignite.Core/
> Configuration/
> >  DataStorageConfiguration.cs:129,
> >  should be changed to match default value in Java.
> > 
> >  Pavel
> > 
> >  On Tue, Feb 20, 2018 at 3:11 PM, Dmitry Pavlov <
> dpavlov@gmail.com
> > >
> >  wrote:
> > 
> > > Hi Pavel,
> > >
> > > Thank you for pointing this out.
> > >
> > > Sincerely,
> > > Dmitry Pavlov
> > >
> > > вт, 20 февр. 2018 г. в 11:48, Pavel Tupitsyn  >:
> > >
> > > > Alexey, Ilya,
> > > >
> > > > Recent merge of IGNITE-7594 has broken some tests in master,
> > > > AND in ignite-2.4 (which concerns me) [1] [2].
> > > >
> > > > * Have you run the tests before merging your changes?
> > > > * Can you please fix this?
> > > >
> > > > In particular, you'll have to update
> > > > the DataStorageConfiguration.DefaultWalMode on .NET side.
> > > >
> > > > Thanks,
> > > > Pavel
> > > >
> > > >
> > > > [1]
> > > >
> > > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=
> > > 1c7b42285f27dbcb5bcc38fe3d7dee8aac5cb873
> > > >
> > > > [2] https://ci.ignite.apache.org/viewLog.html?buildId=1102392
> > > >
> > >
> > 
> > 
> > >>>
> > >>>
> > >>> --
> > >>> Best regards,
> > >>> Ilya
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> Best regards,
> > >> Ilya
> > >>
> > >
> >
>

[GitHub] ignite pull request #3544: ignite-7767 : Updated WalMode values in .NET.

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/3544


---

[GitHub] ignite pull request #3548: IGNITE-7660: Refactor LSQR algorithm

[Andy92]

GitHub user Andy92 opened a pull request:

https://github.com/apache/ignite/pull/3548

IGNITE-7660: Refactor LSQR algorithm

Refactor for the issue ignite-7660.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Andy92/ignite master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3548.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3548


commit 8fee202a0594416e8975919f49de19e8fc68b5bd
Author: Andy 
Date:   2018-02-20T23:49:50Z

IGNITE-7660: Refactor LSQR algorithm




---

Re: IGNITE-6005 is ready for review

[Dmitry Pavlov]

Hi Igniters,

It seems this issue review process hang up.

Andrey Gura had concerns about this implementation. In the same time Ilya L
checked this implementation and approves it.

I didn't find points to improve and concerns are not clear for me. I didn't
managed to get more info in issue
https://issues.apache.org/jira/browse/IGNITE-6005 comments.

What can be our next step to solve this?

Absence of this fix causes 100% timeout in Data Structures suite and wastes
agents for a long time.

Sincerely,
Dmitriy Pavlov

пн, 12 февр. 2018 г. в 17:54, Ilya Lantukh :

> Hi Nikolay,
>
> Thanks for contribution!
>
> I will try to review your pull request by tomorrow.
>
> On Mon, Feb 12, 2018 at 11:45 AM, Nikolay Izhikov 
> wrote:
>
> > Hello, Igniters.
> >
> > I've fix some relatively small issue(100 loc) IGNITE-6005 [1], PR [2]
> > The fix in DataStructuresProcessor.java
> >
> > As far as I can see from git log Ilya Lantukh maintains this piece of
> code.
> >
> > Ilya, can you please take a look at the fix?
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-6005
> >
> > [2] https://github.com/apache/ignite/pull/2773
>
>
>
>
> --
> Best regards,
> Ilya
>

Re: Broken tests after IGNITE-7594 merge

[Dmitry Pavlov]

Ilya, thank you from me too for such a fast issue resolution.

Pavel, could you please merge this PR to master? Or please advice who else
can?

Anton V. could you help?

вт, 20 февр. 2018 г. в 19:11, Pavel Tupitsyn :

> Ilya, thanks for the fix, looks good to me.
> Please make sure TC passes and merge.
>
> On Tue, Feb 20, 2018 at 6:08 PM, Dmitriy Pavlov 
> wrote:
>
> > Issue is not in 'patch available' state.
> >
> > On Tue, Feb 20, 2018 at 6:06 PM Ilya Lantukh 
> > wrote:
> >
> >> Fixed, please review: https://issues.apache.org/jira/browse/IGNITE-7767
> .
> >>
> >> On Tue, Feb 20, 2018 at 5:44 PM, Ilya Lantukh 
> >> wrote:
> >>
> >>> Pavel,
> >>>
> >>> I've fixed default value for WALMode (https://github.com/apache/
> >>> ignite/pull/3544), but now I have the following test failure:
> >>> Apache.Ignite.Core.Tests.IgniteConfigurationTest.
> >>> TestDefaultConfigurationProperties
> >>>
> >>>   Expected: LogOnly
> >>>   But was:  Fsync
> >>>
> >>>at NUnit.Framework.Assert.That(Object actual, IResolveConstraint
> >>> expression, String message, Object[] args)
> >>>at Apache.Ignite.Core.Tests.IgniteConfigurationTest.
> >>> CheckDefaultProperties(DataStorageConfiguration cfg) in
> >>> C:\Projects\ignite\modules\platforms\dotnet\Apache.Ignite.Core.Tests\
> >>> IgniteConfigurationTest.cs:line 551
> >>>at Apache.Ignite.Core.Tests.IgniteConfigurationTest.
> >>> TestDefaultConfigurationProperties() in C:\Projects\ignite\modules\
> >>>
> platforms\dotnet\Apache.Ignite.Core.Tests\IgniteConfigurationTest.cs:line
> >>> 68
> >>>
> >>> Could you please take a look and help us understand why did it happen?
> >>>
> >>> On Tue, Feb 20, 2018 at 4:48 PM, Pavel Tupitsyn 
> >>> wrote:
> >>>
>  Ilya,
> 
>  Please see modules/platforms/dotnet/Apache.Ignite.Core/Configuration/
>  DataStorageConfiguration.cs:129,
>  should be changed to match default value in Java.
> 
>  Pavel
> 
>  On Tue, Feb 20, 2018 at 3:11 PM, Dmitry Pavlov  >
>  wrote:
> 
> > Hi Pavel,
> >
> > Thank you for pointing this out.
> >
> > Sincerely,
> > Dmitry Pavlov
> >
> > вт, 20 февр. 2018 г. в 11:48, Pavel Tupitsyn :
> >
> > > Alexey, Ilya,
> > >
> > > Recent merge of IGNITE-7594 has broken some tests in master,
> > > AND in ignite-2.4 (which concerns me) [1] [2].
> > >
> > > * Have you run the tests before merging your changes?
> > > * Can you please fix this?
> > >
> > > In particular, you'll have to update
> > > the DataStorageConfiguration.DefaultWalMode on .NET side.
> > >
> > > Thanks,
> > > Pavel
> > >
> > >
> > > [1]
> > >
> > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=
> > 1c7b42285f27dbcb5bcc38fe3d7dee8aac5cb873
> > >
> > > [2] https://ci.ignite.apache.org/viewLog.html?buildId=1102392
> > >
> >
> 
> 
> >>>
> >>>
> >>> --
> >>> Best regards,
> >>> Ilya
> >>>
> >>
> >>
> >>
> >> --
> >> Best regards,
> >> Ilya
> >>
> >
>

Re: Change TC trigger from Run All to per-project basis

[Dmitry Pavlov]

Hi Pavel,

WDYT,
1) is it needed to prepare wiki article describing tests and chains we
have, e.g. describe
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RunBasicTests
and
its difference with RunAll; which chain to use in each case?

2) Which .Net test suite may be applicable to be included into 'run basic
tests' (requires <30 min to run, no failed test, no flaky test with fail
rate >1%) ?

Sincerely,
Dmitriy Pavlov

пн, 19 февр. 2018 г. в 0:39, Pavel Tupitsyn :

> Igniters,
>
> Currently we have a TeamCity trigger only on Run All aggregating project:
>
> https://ci.ignite.apache.org/admin/editTriggers.html?id=buildType:IgniteTests24Java8_RunAll
>
> Each change triggers it's own full run. If new changes are added while some
> builds are queued,
> these changes are not picked up, and a separate run is scheduled.
>
> At this very moment I see over 600 queued builds, all on master branch from
> some trigger.
> Previously we had a trigger per-project, which seems to be more efficient.
>
> Thoughts?
>
> Pavel
>

Re: TX SQL: SELECT FOR UPDATE implementation

[Alexander Paschenko]

Hello again, and here I go with some more thoughts on SELECT FOR UPDATE.
After having talking to Vlad, we returned again to question about how
SELECT FOR UPDATE should work with JOINs.

It seems that distributed joins currently are better to be left aside
as long as rework of distributed queries and joins is a separate big
issue.
However, probably we still should think about what we could make work
after all with what we have in our hands now. And it seems that some
scenarios are pretty doable - say, when there's an ordinary JOIN of
few tables, we can simply append keys of those tables to list of
selected columns, and that would work in case of collocated data.

* Alas, major vendors (Postgres, MySQL, Oracle) all also honor
subqueries in JOINs - say, like this:

select p.id , c.id from person p inner join (select * from company) c
on p.company_id = c.id where p.id > 3 and p.id < 10 for update;

Obviously, this is a bit corner case as such JOIN is not much
different from an ordinary multi-table one, but it gives overall idea
of what I'm talking about - major databases lock what's been selected
in subquery as well.

That said, aforementioned case probably could also be processed as
suggested above - that is, we take innermost query, append key to list
of its selected columns, so that we can refer to that new column from
outer query, etc, etc. In principle we could process even
multiple-level nesting of queries with such approach.
Also no major vendors, except probably MySQL, support GROUP BY with
SELECT FOR UPDATE, and this simplifies our task a bit. :)

If someone can think of an example of a query that cannot be processed
in the way described above, please write about it.

* Also it looks like no major vendors out of three mentioned above
lock record from tables mentioned in subqueries in SELECT columns or
in WHERE - say, this query

select p.id, (select count(*) from company) from person p

will lock only records in Person table.

Thoughts? Should we attempt to implement JOINs support right away? Or
would it be better to leave it be for (near) future and start with
simple implementation that would ban JOINs altogether?

Regards,
Alex


2018-01-25 10:58 GMT+03:00 Vladimir Ozerov :
> Alex,
>
> Thank you for detailed analysis. My 50 cents:
>
> 1) I would not allow GROUP BYs in the first place. These are good
> candidates for further iterations IMO
> 2) Same as p.1
> 3) In final TX SQL solution we woll lock rows, not keys
> (GridCacheMapEntry). Can we simply lock every row returned from the query?
> 4) Same as p.1
> 5) Yes, it should work the same way we would implement it for normal queries
>
> Also I am not quite understand why should we keep results on map node until
> all keys are locked. This increases memory pressure on the server. Instead,
> I would start sending batches to reducer immediately, but do not return the
> very first result to the user until all results are collected. This way
> pressure is moved to the client what increases cluster stability. Will that
> work?
>
> On Wed, Jan 24, 2018 at 6:23 PM, Alexander Paschenko <
> alexander.a.pasche...@gmail.com> wrote:
>
>> Hello Igniters,
>>
>> I'd like to bring up the discussion about implementation details of
>> https://issues.apache.org/jira/browse/IGNITE-6937 about
>> support of SELECT FOR UPDATE statements as a part of overall activity
>> on transactional SQL.
>>
>> That kind of statements allows the user proactively obtain row level
>> locks for the records that they may (or may not) want to
>> update in further statements of the same transaction.
>>
>> Suggested general approach to implementation is as follows:
>>
>> - Perform two-step SELECT as usual (e.g. split, map, reduce stages), BUT
>> - Map nodes start giving away their first result pages for such query
>> only after they have traversed whole their result set
>> and have obtained locks for all keys corresponding to selected rows
>> (e.g. rows matching WHERE clause).
>>
>> I've made some research on how some RDBMSs behave (MySQL, Oracle, Pg)
>> and found that they all also consider SELECT FOR UPDATE
>> finished and give away its result set only after all locks have been
>> acquired, so in general suggested strategy is similar to
>> what other databases do. Alas, everyone concerned is welcome to share
>> their views on how this feature could work in Ignite - as well as on
>> some stuff stated below. These are some caveats that I'd like to
>> discuss in addition to overall approach.
>>
>> First: should we allow GROUP BY clause in SELECT FOR UPDATE? Oracle
>> and Pg do not support it in any way, while MySQL does.
>>
>> Second: should we allow JOIN clause in SELECT FOR UPDATE? All
>> mentioned major vendors support it, but with Ignite implementation
>> likely
>> will not be straightforward - this has to do with pt. 3.
>>
>> Third: in general case, how do we detect *keys* that we should lock?
>> Consider following statement: SELECT name FROM person FOR UPDATE.
>> This 

[GitHub] ignite pull request #3547: IGNITE-5829 WAL Delta records optimizations.

[Jokser]

GitHub user Jokser opened a pull request:

https://github.com/apache/ignite/pull/3547

IGNITE-5829 WAL Delta records optimizations.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-5829-dual-mode

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3547.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3547


commit 5855257ce55e88e94ab61473547f1c25ecff6088
Author: Pavel Kovalenko 
Date:   2017-07-28T09:55:31Z

IGNITE-5829 Initial implementation.

commit 9a83f020e3c42cec6ee559a830388817d3288459
Author: Pavel Kovalenko 
Date:   2017-07-28T11:54:51Z

IGNITE-5829 Fixed creation CacheDataRowAdapter from LazyDataEntry.

commit bc18394f317ab6854c8fd75efe3f50f64bcfe64a
Author: Pavel Kovalenko 
Date:   2017-07-28T15:53:01Z

IGNITE-5829 Some changes.

commit 1e08c3fb5c02ec8acafd71b50b6ad3b749259f1a
Author: Andrey V. Mashenkov 
Date:   2017-07-31T11:14:56Z

IGNITE-4800: Lucene query may fails with NPE. This closes #2315.

commit 3fdf453e89a7bd76dff6b6d0646e3821ea3921d5
Author: Andrey V. Mashenkov 
Date:   2017-07-31T14:32:12Z

IGNITE-4800: Lucene query may fails with NPE.
Test fixed.

commit 739d8da94599c67c6ec9365019ed937cf05dbf32
Author: Pavel Kovalenko 
Date:   2017-08-02T11:58:08Z

IGNITE-5829 Passing WAL reference to CacheRow.

commit 1ca697ffcd8daf31a8ed1b2a078f40c688cb6b73
Author: Pavel Kovalenko 
Date:   2017-08-02T12:49:32Z

Merge branch 'ignite-2.1.4' into ignite-5829

commit a916d8bf9f5fbf9bb863913ee8de8414ddc5a303
Author: Pavel Kovalenko 
Date:   2017-08-02T12:53:59Z

IGNITE-5829 Fixed H2 rows.

commit 6895bce938efab7a30ded16e9e181f5f376c2728
Author: Pavel Kovalenko 
Date:   2017-08-02T12:55:49Z

IGNITE-5829 Code cleaning

commit 86f6fb19b1e2c7171f5cacf44a2f9246ced0177c
Author: Pavel Kovalenko 
Date:   2017-08-02T13:01:57Z

IGNITE-5829 Allocate non-direct buffer.

commit e255a564985a12113984ec02f15a4443495b8ffc
Author: Nikolay Izhikov 
Date:   2017-08-02T08:52:44Z

ignite-5712 Context switching for optimistic transactions

commit 772d462b68c7de8517d1f61e2e05ec8eefb18eac
Author: Alexey Kuznetsov 
Date:   2017-08-03T04:55:15Z

Merge branch ignite-2.1.3 into ignite-2.1.4

commit 72d706e6f3bad47d19846f0aba1f74431957fa69
Author: Pavel Kovalenko 
Date:   2017-08-03T11:29:59Z

IGNITE-5829 Minor changes.

commit 0f3b7ca25313083e4dc35e7842931a655abd
Author: tledkov-gridgain 
Date:   2017-08-04T08:46:14Z

IGNITE-5126: Batch support for this JDBC driver. This closes #2162.

commit d1a74a4be8744528e6ed23706174041ddb0f2618
Author: devozerov 
Date:   2017-08-04T09:04:38Z

Merge remote-tracking branch 'upstream/ignite-2.1.4' into ignite-2.1.4

commit 0b3a9a7176f5ae44a96ecf700c8147193dfbf064
Author: Igor Sapego 
Date:   2017-08-04T10:18:00Z

IGNITE-5923: ODBC: SQLGetTypeInfo now works with SQL_ALL_TYPES

(cherry picked from commit 48c914d)

commit 4e0385fbc0f50548f2da3407fdfdfe939b463c67
Author: Igor Sapego 
Date:   2017-08-04T15:34:27Z

IGNITE-5939: ODBC: SQLColAttributes now works with legacy attribute codes.

(cherry picked from commit 70ffa2c)

commit b4e3d661fc23a212660afd67f50159e135338aa9
Author: Pavel Kovalenko 
Date:   2017-08-04T16:47:20Z

IGNITE-5829 Final version without tests and backward compatibility.

commit c243fc1e7c5e9fe73715cb2b25ee55ee82eb1214
Author: Pavel Kovalenko 
Date:   2017-08-04T16:54:27Z

IGNITE-5829 Uncomment tests.

commit 93c4b9e3dbf5ef12dc95bdab20abaf40bbfc715c
Author: Pavel Kovalenko 
Date:   2017-08-06T16:34:58Z

IGNITE-5829 Code cleaning

commit 215a77687c88edc60dba055029ba6ac1642e1555
Author: Pavel Kovalenko 
Date:   2017-08-06T16:37:02Z

IGNITE-5829 Fixed cache size property for PayloadLinker.

commit 17e758dfc091ae4e416e1cca60ca2361ced8ffd0
Author: Pavel Kovalenko 
Date:   2017-08-06T18:30:35Z

IGNITE-5829 Fixed compilation.

commit 3b9b663a49064e301c1d619b06f3a581808ca66a
Author: Pavel Kovalenko 
Date:   2017-08-06T20:44:38Z

IGNITE-5829 Some logic changes in GridCacheMapEntry.

commit e3d033682e6ab4c28ed0bebd7c5fb22895456cb1
Author: Pavel Kovalenko 
Date:   2017-08-06T22:56:41Z

IGNITE-5829 Lookup pointer from WAL every time. Log update.

commit 4f02504475fd1e5cc3b9f4754856e44d20fdc1cb
Author: Alexey Kuznetsov 
Date:   2017-08-07T02:41:22Z

Merge branch ignite-2.1.3 into ignite-2.1.4.

commit a7b2430a1fb00104b01e3609211ea358964640d7

Re: Ignite Thin clients for Node.js, Python, PHP

[Denis Magda]

Sergey,

Excellent, please share the branch once you're ready. As I understand, the
guys can take it as a basis and support all the APIs available in the
protocol

On Tue, Feb 20, 2018 at 5:31 AM, Sergey Kozlov  wrote:

> Hi
>
> Yes, I've a prototype of python client supporting cache operations only.
>
> I plan to share that after official AI 2.4 release providing thin client
> implementation.
>
> On Tue, Feb 20, 2018 at 11:40 AM, Pavel Tupitsyn 
> wrote:
>
> > Hi,
> >
> > As far as I know, Sergey Kozlov  already has some
> > Python thin client implementation,
> > not sure how much functionality is in there, but it may be a good start.
> >
> > Sergey, can you share something with us?
> >
> > Thanks,
> > Pavel
> >
> > On Tue, Feb 20, 2018 at 1:34 AM, Alexey Kukushkin <
> > kukushkinale...@gmail.com
> > > wrote:
> >
> > > Also, we could have a Hangouts call or something to share thin client
> > > development experience. You can reach me at kukushkinale...@gmail.com.
> > >
> >
>
>
>
> --
> Sergey Kozlov
> GridGain Systems
> www.gridgain.com
>

Re: Broken tests after IGNITE-7594 merge

[Pavel Tupitsyn]

Ilya, thanks for the fix, looks good to me.
Please make sure TC passes and merge.

On Tue, Feb 20, 2018 at 6:08 PM, Dmitriy Pavlov 
wrote:

> Issue is not in 'patch available' state.
>
> On Tue, Feb 20, 2018 at 6:06 PM Ilya Lantukh 
> wrote:
>
>> Fixed, please review: https://issues.apache.org/jira/browse/IGNITE-7767.
>>
>> On Tue, Feb 20, 2018 at 5:44 PM, Ilya Lantukh 
>> wrote:
>>
>>> Pavel,
>>>
>>> I've fixed default value for WALMode (https://github.com/apache/
>>> ignite/pull/3544), but now I have the following test failure:
>>> Apache.Ignite.Core.Tests.IgniteConfigurationTest.
>>> TestDefaultConfigurationProperties
>>>
>>>   Expected: LogOnly
>>>   But was:  Fsync
>>>
>>>at NUnit.Framework.Assert.That(Object actual, IResolveConstraint
>>> expression, String message, Object[] args)
>>>at Apache.Ignite.Core.Tests.IgniteConfigurationTest.
>>> CheckDefaultProperties(DataStorageConfiguration cfg) in
>>> C:\Projects\ignite\modules\platforms\dotnet\Apache.Ignite.Core.Tests\
>>> IgniteConfigurationTest.cs:line 551
>>>at Apache.Ignite.Core.Tests.IgniteConfigurationTest.
>>> TestDefaultConfigurationProperties() in C:\Projects\ignite\modules\
>>> platforms\dotnet\Apache.Ignite.Core.Tests\IgniteConfigurationTest.cs:line
>>> 68
>>>
>>> Could you please take a look and help us understand why did it happen?
>>>
>>> On Tue, Feb 20, 2018 at 4:48 PM, Pavel Tupitsyn 
>>> wrote:
>>>
 Ilya,

 Please see modules/platforms/dotnet/Apache.Ignite.Core/Configuration/
 DataStorageConfiguration.cs:129,
 should be changed to match default value in Java.

 Pavel

 On Tue, Feb 20, 2018 at 3:11 PM, Dmitry Pavlov 
 wrote:

> Hi Pavel,
>
> Thank you for pointing this out.
>
> Sincerely,
> Dmitry Pavlov
>
> вт, 20 февр. 2018 г. в 11:48, Pavel Tupitsyn :
>
> > Alexey, Ilya,
> >
> > Recent merge of IGNITE-7594 has broken some tests in master,
> > AND in ignite-2.4 (which concerns me) [1] [2].
> >
> > * Have you run the tests before merging your changes?
> > * Can you please fix this?
> >
> > In particular, you'll have to update
> > the DataStorageConfiguration.DefaultWalMode on .NET side.
> >
> > Thanks,
> > Pavel
> >
> >
> > [1]
> >
> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=
> 1c7b42285f27dbcb5bcc38fe3d7dee8aac5cb873
> >
> > [2] https://ci.ignite.apache.org/viewLog.html?buildId=1102392
> >
>


>>>
>>>
>>> --
>>> Best regards,
>>> Ilya
>>>
>>
>>
>>
>> --
>> Best regards,
>> Ilya
>>
>

[GitHub] ignite pull request #3546: IGNITE-6083 alternate fix version

[voipp]

GitHub user voipp opened a pull request:

https://github.com/apache/ignite/pull/3546

IGNITE-6083 alternate fix version



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/voipp/ignite ignite-6083-2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3546.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3546


commit 236b63bb7f3ebd214a690b168edf14c6c1832c95
Author: voipp 
Date:   2018-02-20T16:09:12Z

IGNITE-6083 alternate fix version




---

[jira] [Created] (IGNITE-7773) Add getRebalanceClearingPartitionsLeft JMX metric to .NET

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-7773:
---

 Summary: Add getRebalanceClearingPartitionsLeft JMX metric to .NET
 Key: IGNITE-7773
 URL: https://issues.apache.org/jira/browse/IGNITE-7773
 Project: Ignite
  Issue Type: Task
  Components: platforms
Reporter: Pavel Kovalenko
 Fix For: 2.5


New metric is introduced in IGNITE-6113 .



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: TeamCity. Ignite RDD tests

[Nikolay Izhikov]

Hello, Dmitriy.

Sorry, I thought I did it by myself.
Thank you, anyway.

В Вт, 20/02/2018 в 15:24 +, Dmitry Pavlov пишет:
> Hi Nikolay,
> 
> A number of TC tests began to fail with link to
> https://issues.apache.org/jira/browse/IGNITE-7727
> 
> I've muted all tests, which I found. Please umute it when issue will be
> fixed.
> 
> Sincerely,
> Dmitriy Pavlov
> 
> пт, 16 февр. 2018 г. в 18:06, vveider :
> 
> > Nikolay, I raised your permissions to Ignite Committer status.
> > Check it out, please.
> > 
> > 
> > 
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > 

signature.asc
Description: This is a digitally signed message part

Re: TeamCity. Ignite RDD tests

[Dmitry Pavlov]

Hi Nikolay,

A number of TC tests began to fail with link to
https://issues.apache.org/jira/browse/IGNITE-7727

I've muted all tests, which I found. Please umute it when issue will be
fixed.

Sincerely,
Dmitriy Pavlov

пт, 16 февр. 2018 г. в 18:06, vveider :

> Nikolay, I raised your permissions to Ignite Committer status.
> Check it out, please.
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[jira] [Created] (IGNITE-7772) All critical system workers health should be covered

[Anton Vinogradov (JIRA)]

Anton Vinogradov created IGNITE-7772:


 Summary: All critical system workers health should be covered
 Key: IGNITE-7772
 URL: https://issues.apache.org/jira/browse/IGNITE-7772
 Project: Ignite
  Issue Type: Task
Reporter: Anton Vinogradov
Assignee: Dmitriy Sorokin






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

MTCGA: Exchange merge tests

[Dmitry Pavlov]

Hi Igniters, Semyon,

We have old flaky failure of relatively new feature 'Exhange Merge' test

https://issues.apache.org/jira/browse/IGNITE-6467

Semyon, did you have a chance to look? Is it possible issue would be
resolved? If not, could you please move it to unassigned?

Calling for exchange experts:
Who can take a look to this issue?

Sincerely,
Dmitriy Pavlov

[GitHub] ignite pull request #3543: IGNITE-7768: No description for org.apache.ignite...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/3543


---

[jira] [Created] (IGNITE-7771) Names of Ignite JMX beans should not be quoted unless required

[Stanislav Lukyanov (JIRA)]

Stanislav Lukyanov created IGNITE-7771:
--

 Summary: Names of Ignite JMX beans should not be quoted unless 
required
 Key: IGNITE-7771
 URL: https://issues.apache.org/jira/browse/IGNITE-7771
 Project: Ignite
  Issue Type: Bug
Reporter: Stanislav Lukyanov
Assignee: Stanislav Lukyanov


Names of Ignite JMX beans and bean groups are currently quoted if they contain 
non-alphanumeric characters. This leads to names with spaces, e.g. Thread 
Pools, appearing as "Thread Pools". Moreover, Thread Pools and "Thread Pools" 
are recognized by JMX as distinct names, so code accessing that MBean needs to 
take that into account.

It would be better not to quote the bean and group names unless they contain 
specific control characters. That way users won't need to quote names in their 
JMX clients.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #3545: ignite-5714

[voipp]

GitHub user voipp opened a pull request:

https://github.com/apache/ignite/pull/3545

ignite-5714

alternate version

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/voipp/ignite ignite-5714-alternate-version

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3545.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3545


commit 316f506742e093996107795250daaef3d36c60cc
Author: voipp 
Date:   2018-02-14T13:51:46Z

new atomiclong counter created. NearTxLocal and DhtTxLocal are set new 
counter instead old threadId




---

Save the date: ApacheCon North America, September 24-27 in Montréal

[Rich Bowen]

Dear Apache Enthusiast,

(You’re receiving this message because you’re subscribed to a user@ or 
dev@ list of one or more Apache Software Foundation projects.)


We’re pleased to announce the upcoming ApacheCon [1] in Montréal, 
September 24-27. This event is all about you — the Apache project community.


We’ll have four tracks of technical content this time, as well as lots 
of opportunities to connect with your project community, hack on the 
code, and learn about other related (and unrelated!) projects across the 
foundation.


The Call For Papers (CFP) [2] and registration are now open. Register 
early to take advantage of the early bird prices and secure your place 
at the event hotel.


Important dates
March 30: CFP closes
April 20: CFP notifications sent
	August 24: Hotel room block closes (please do not wait until the last 
minute)


Follow @ApacheCon on Twitter to be the first to hear announcements about 
keynotes, the schedule, evening events, and everything you can expect to 
see at the event.


See you in Montréal!

Sincerely, Rich Bowen, V.P. Events,
on behalf of the entire ApacheCon team

[1] http://www.apachecon.com/acna18
[2] https://cfp.apachecon.com/conference.html?apachecon-north-america-2018

[GitHub] ignite pull request #3544: ignite-7767 : Updated WalMode values in .NET.

[ilantukh]

GitHub user ilantukh opened a pull request:

https://github.com/apache/ignite/pull/3544

ignite-7767 : Updated WalMode values in .NET.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-7767

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3544.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3544


commit 3b88c418609b4c2d1338c1b6056d77244ef4886c
Author: Ilya Lantukh 
Date:   2018-02-20T14:17:06Z

ignite-7767 : Updated WalMode values in .NET.




---

[jira] [Created] (IGNITE-7770) Ignite Cache 6: testRandomMixedTxConfigurations failed probably after jsr166 removal

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-7770:
--

 Summary: Ignite Cache 6: testRandomMixedTxConfigurations failed 
probably after jsr166 removal
 Key: IGNITE-7770
 URL: https://issues.apache.org/jira/browse/IGNITE-7770
 Project: Ignite
  Issue Type: Task
Reporter: Dmitriy Pavlov
Assignee: Andrey Kuznetsov


Ignite Cache 6: testRandomMixedTxConfigurations failed probably after jsr166 
removal
After appying IGNITE-7518 Get rid of org.jsr166.LongAdder8, 
 IgniteCacheTestSuite6: 
TxRollbackOnTimeoutNearCacheTest.testRandomMixedTxConfigurations (fail rate 
38,6%) 

https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-3733584033131292028=%3Cdefault%3E=testDetails




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7769) Persistence Problem

[JIRA]

Caner Önder created IGNITE-7769:
---

 Summary: Persistence Problem
 Key: IGNITE-7769
 URL: https://issues.apache.org/jira/browse/IGNITE-7769
 Project: Ignite
  Issue Type: Bug
  Components: binary, persistence
Affects Versions: 2.3
 Environment: *Summary:*
*+-+*
*| Active | true |*
*| Total hosts | 5 |*
*| Total nodes | 5 |*
*| Total CPUs | 10 |*
*| Avg. CPU load | 6.17 % |*
*| Avg. free heap | 81.00 % |*
*| Avg. Up time | 00:03:57 |*
*| Snapshot time | 02/20/18, 16:36:01 |*
*+-+*
Reporter: Caner Önder
 Attachments: example-persistent-store.xml

Hİ, i have persistency problem with the conf file which i already attached.

When i reboot the cluster and activate it again, i lose data on every reboot 
and also the old tables which i deleted before, appears again.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Broken tests after IGNITE-7594 merge

[Pavel Tupitsyn]

Ilya,

Please see
modules/platforms/dotnet/Apache.Ignite.Core/Configuration/DataStorageConfiguration.cs:129,
should be changed to match default value in Java.

Pavel

On Tue, Feb 20, 2018 at 3:11 PM, Dmitry Pavlov 
wrote:

> Hi Pavel,
>
> Thank you for pointing this out.
>
> Sincerely,
> Dmitry Pavlov
>
> вт, 20 февр. 2018 г. в 11:48, Pavel Tupitsyn :
>
> > Alexey, Ilya,
> >
> > Recent merge of IGNITE-7594 has broken some tests in master,
> > AND in ignite-2.4 (which concerns me) [1] [2].
> >
> > * Have you run the tests before merging your changes?
> > * Can you please fix this?
> >
> > In particular, you'll have to update
> > the DataStorageConfiguration.DefaultWalMode on .NET side.
> >
> > Thanks,
> > Pavel
> >
> >
> > [1]
> >
> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=
> 1c7b42285f27dbcb5bcc38fe3d7dee8aac5cb873
> >
> > [2] https://ci.ignite.apache.org/viewLog.html?buildId=1102392
> >
>

Re: Ignite Thin clients for Node.js, Python, PHP

[Sergey Kozlov]

Hi

Yes, I've a prototype of python client supporting cache operations only.

I plan to share that after official AI 2.4 release providing thin client
implementation.

On Tue, Feb 20, 2018 at 11:40 AM, Pavel Tupitsyn 
wrote:

> Hi,
>
> As far as I know, Sergey Kozlov  already has some
> Python thin client implementation,
> not sure how much functionality is in there, but it may be a good start.
>
> Sergey, can you share something with us?
>
> Thanks,
> Pavel
>
> On Tue, Feb 20, 2018 at 1:34 AM, Alexey Kukushkin <
> kukushkinale...@gmail.com
> > wrote:
>
> > Also, we could have a Hangouts call or something to share thin client
> > development experience. You can reach me at kukushkinale...@gmail.com.
> >
>



-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com

[GitHub] ignite pull request #3543: IGNITE-7768: No description for org.apache.ignite...

[artemmalykh]

GitHub user artemmalykh opened a pull request:

https://github.com/apache/ignite/pull/3543

IGNITE-7768: No description for 
org.apache.ignite.ml.nn.trainers.distributed.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-7768

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/3543.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3543


commit 0f28f437e60b78a763a7eebc0d51565e0b0e0c80
Author: Artem Malykh 
Date:   2018-02-20T13:26:55Z

IGNITE-7768: Added package-info.




---

[jira] [Created] (IGNITE-7768) No description for org.apache.ignite.ml.nn.trainers.distributed

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-7768:


 Summary: No description for 
org.apache.ignite.ml.nn.trainers.distributed
 Key: IGNITE-7768
 URL: https://issues.apache.org/jira/browse/IGNITE-7768
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Affects Versions: 2.4
Reporter: Ilya Suntsov
Assignee: Artem Malykh


We need to add description for package 
org.apache.ignite.ml.nn.trainers.distributed



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7767) Update WALMode configuration in .NET

[Ilya Lantukh (JIRA)]

Ilya Lantukh created IGNITE-7767:


 Summary: Update WALMode configuration in .NET
 Key: IGNITE-7767
 URL: https://issues.apache.org/jira/browse/IGNITE-7767
 Project: Ignite
  Issue Type: Bug
Reporter: Ilya Lantukh
Assignee: Ilya Lantukh


In https://issues.apache.org/jira/browse/IGNITE-7594 we changed values for 
WALMode enum, but .NET code wasn't modified accordingly.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-7766:
--

 Summary: Ignite Queries 2: Test always failed 
IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
 Key: IGNITE-7766
 URL: https://issues.apache.org/jira/browse/IGNITE-7766
 Project: Ignite
  Issue Type: Task
  Components: sql
Reporter: Dmitriy Pavlov
Assignee: Alexei Scherbakov


   Ignite Queries 2  
 IgniteBinaryCacheQueryTestSuite2: 
IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) 

IgniteCacheQueryNodeRestartTxSelfTest.testRestarts  
Current failure:refs/heads/master   #345No changes  
11 Feb 18 03:03
 
junit.framework.AssertionFailedError: On large page size must retry.
 
Last runs fails with 100% probability.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Broken tests after IGNITE-7594 merge

[Dmitry Pavlov]

Hi Pavel,

Thank you for pointing this out.

Sincerely,
Dmitry Pavlov

вт, 20 февр. 2018 г. в 11:48, Pavel Tupitsyn :

> Alexey, Ilya,
>
> Recent merge of IGNITE-7594 has broken some tests in master,
> AND in ignite-2.4 (which concerns me) [1] [2].
>
> * Have you run the tests before merging your changes?
> * Can you please fix this?
>
> In particular, you'll have to update
> the DataStorageConfiguration.DefaultWalMode on .NET side.
>
> Thanks,
> Pavel
>
>
> [1]
>
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=1c7b42285f27dbcb5bcc38fe3d7dee8aac5cb873
>
> [2] https://ci.ignite.apache.org/viewLog.html?buildId=1102392
>

[jira] [Created] (IGNITE-7765) walSegmentSize can be negative in config

[Alexander Belyak (JIRA)]

Alexander Belyak created IGNITE-7765:


 Summary: walSegmentSize can be negative in config
 Key: IGNITE-7765
 URL: https://issues.apache.org/jira/browse/IGNITE-7765
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.2
Reporter: Alexander Belyak


Grid use default (64Mb) DataStorageConfiguration.walSegmentSize without 
warnings if negative value specified, for example if in xml specified something 
like
 (overflow)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7764) MVCC TX: Locking protocol for Key-Value API

[Roman Kondakov (JIRA)]

Roman Kondakov created IGNITE-7764:
--

 Summary: MVCC TX: Locking protocol for Key-Value API
 Key: IGNITE-7764
 URL: https://issues.apache.org/jira/browse/IGNITE-7764
 Project: Ignite
  Issue Type: New Feature
  Components: sql
Reporter: Roman Kondakov


We need to implement an MVCC-compatible locking protocol for Key-Value API. At 
the moment during transactions with KV operations if entry we are going to 
change is unlocked we do not check if it has been changed by the previous 
transaction.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7763) Ignite CPP tests win32 failure

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-7763:
--

 Summary: Ignite CPP tests win32 failure
 Key: IGNITE-7763
 URL: https://issues.apache.org/jira/browse/IGNITE-7763
 Project: Ignite
  Issue Type: Task
Reporter: Dmitriy Pavlov
Assignee: Igor Sapego


https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePlatformCppWin32
 
aborted
std::exception: Failed to load JVM library.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7762) Add metrics for entry processor ibvocation to .Net

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-7762:


 Summary: Add metrics for entry processor ibvocation to .Net
 Key: IGNITE-7762
 URL: https://issues.apache.org/jira/browse/IGNITE-7762
 Project: Ignite
  Issue Type: Sub-task
  Components: cache
Reporter: Alexey Kuznetsov
Assignee: Pavel Tupitsyn






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #3539: IGNITE-7747 An exception should not be throw if s...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/3539


---

Broken tests after IGNITE-7594 merge

[Pavel Tupitsyn]

Alexey, Ilya,

Recent merge of IGNITE-7594 has broken some tests in master,
AND in ignite-2.4 (which concerns me) [1] [2].

* Have you run the tests before merging your changes?
* Can you please fix this?

In particular, you'll have to update
the DataStorageConfiguration.DefaultWalMode on .NET side.

Thanks,
Pavel


[1]
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=commit;h=1c7b42285f27dbcb5bcc38fe3d7dee8aac5cb873

[2] https://ci.ignite.apache.org/viewLog.html?buildId=1102392

Re: Ignite Thin clients for Node.js, Python, PHP

[Pavel Tupitsyn]

Hi,

As far as I know, Sergey Kozlov  already has some
Python thin client implementation,
not sure how much functionality is in there, but it may be a good start.

Sergey, can you share something with us?

Thanks,
Pavel

On Tue, Feb 20, 2018 at 1:34 AM, Alexey Kukushkin  wrote:

> Also, we could have a Hangouts call or something to share thin client
> development experience. You can reach me at kukushkinale...@gmail.com.
>

[GitHub] ignite pull request #3491: IGNITE-7263 Ignore client configuration for daemo...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/3491


---

[jira] [Created] (IGNITE-7761) EXPLAIN with run time statistics

[Pavel Vinokurov (JIRA)]

Pavel Vinokurov created IGNITE-7761:
---

 Summary: EXPLAIN with run time statistics
 Key: IGNITE-7761
 URL: https://issues.apache.org/jira/browse/IGNITE-7761
 Project: Ignite
  Issue Type: New Feature
  Components: sql
Affects Versions: 2.3
Reporter: Pavel Vinokurov


For performance tuning of the sql queries It is nice to have actual run time 
statistics of the query execution.

Statistics could include elapsed time and the number of rows for each query 
node.

Example:

 
||Rows||Actual Time||Plan Node|| ||
|1|5ms|group by city|Index scan using person.city|
|20|30ms|person.age=5|Full scan(person.age)|
|131231|50ms|person.name='John'|Index scan using person_name_idx|

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)