[jira] [Created] (IGNITE-9059) Extra "'await" in loader service in WC front-end

[Alexander Kalinin (JIRA)]

Alexander Kalinin created IGNITE-9059:
-

 Summary: Extra "'await" in loader service in WC front-end
 Key: IGNITE-9059
 URL: https://issues.apache.org/jira/browse/IGNITE-9059
 Project: Ignite
  Issue Type: Bug
Reporter: Alexander Kalinin


 code like "await this.IgniteLoading.finish('notebooksLoading')" doesn't need 
to have await, as it's doesn't return return promise, This part should be 
cleaned.



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

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

[dpavlov . tasks]

Hi Ignite Developer,

I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I 
hope you can help.

 *New Critical Failure in master Data Structures 
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_DataStructures=%3Cdefault%3E=buildTypeStatusDiv
 Changes may led to failure were done by 
 - somefireone 
http://ci.ignite.apache.org/viewModification.html?modId=826273=false
 - vinokurov.pasha 
http://ci.ignite.apache.org/viewModification.html?modId=826253=false
 - dmitriy.govorukhin 
http://ci.ignite.apache.org/viewModification.html?modId=826250=false
 - kaa.dev 
http://ci.ignite.apache.org/viewModification.html?modId=826246=false
 - vanen31 
http://ci.ignite.apache.org/viewModification.html?modId=826242=false
 - garus.d.g 
http://ci.ignite.apache.org/viewModification.html?modId=826234=false
 - ivandasch 
http://ci.ignite.apache.org/viewModification.html?modId=826229=false
 - av 
http://ci.ignite.apache.org/viewModification.html?modId=826218=false
 - estanilovskiy 
http://ci.ignite.apache.org/viewModification.html?modId=826197=false
 - dmitriy.govorukhin 
http://ci.ignite.apache.org/viewModification.html?modId=826195=false

- If your changes can led to this failure(s), please create issue with 
label MakeTeamCityGreenAgain and assign it to you.
-- If you have fix, please set ticket to PA state and write to dev list 
fix is ready 
-- For case fix will require some time please mute test and set label 
Muted_Test to issue 
- If you know which change caused failure please contact change author 
directly
- If you don't know which change caused failure please send message to 
dev list to find out
Should you have any questions please contact dpav...@apache.org or write to 
dev.list 
Best Regards,
MTCGA.Bot 
Notification generated at Tue Jul 24 03:17:09 MSK 2018 

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

[Denis Magda]

Released, thanks for noting.

--
Denis

On Mon, Jul 23, 2018 at 5:53 AM Ilya Kasnacheev 
wrote:

> Hello!
>
> It doesn't seem that we have 2.6 in Released Versions in JIRA. Only 2.5 is
> available.
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-07-18 23:48 GMT+03:00 Denis Magda :
>
> > Added the step about the version in this file -
> > https://ignite.apache.org/latest
> >
> > --
> > Denis
> >
> > On Wed, Jul 18, 2018 at 9:10 AM Anton Vinogradov  wrote:
> >
> > > It looks like we have to update release page with steps forgotten on
> this
> > > iteration.
> > >
> > >
> > > ср, 18 июл. 2018 г. в 18:16, Andrey Gura :
> > >
> > >> Latest version is updated.
> > >>
> > >> Thanks!
> > >> On Wed, Jul 18, 2018 at 4:50 PM Dmitriy Setrakyan <
> > dsetrak...@apache.org>
> > >> wrote:
> > >> >
> > >> > Andrey Gura, can you please update it?
> > >> >
> > >> > D.
> > >> >
> > >> > On Wed, Jul 18, 2018 at 6:34 AM, Dmitry Pavlov <
> dpavlov@gmail.com
> > >
> > >> > wrote:
> > >> >
> > >> > > Hi Ilya,
> > >> > >
> > >> > > Thank you for noticing this.
> > >> > >
> > >> > > We should somehow update https://ignite.apache.org/latest data. I
> > >> guess
> > >> > > PMCs or site admin can do this update.
> > >> > >
> > >> > > Sincerely,
> > >> > > Dmitriy Pavlov
> > >> > >
> > >> > > ср, 18 июл. 2018 г. в 16:31, Ilya Kasnacheev <
> > >> ilya.kasnach...@gmail.com>:
> > >> > >
> > >> > > > Hello!
> > >> > > >
> > >> > > > Since we have releases 2.6.0, can we perhaps prop up the node
> > start
> > >> > > > message, which is currently still:
> > >> > > >
> > >> > > > [16:28:05] New version is available at ignite.apache.org: 2.4.0
> > >> > > >
> > >> > > > Regards,
> > >> > > >
> > >> > > > --
> > >> > > > Ilya Kasnacheev
> > >> > > >
> > >> > > > 2018-07-17 21:59 GMT+03:00 Denis Magda :
> > >> > > >
> > >> > > > > Andrey G.,
> > >> > > > >
> > >> > > > > As a PMC member and release manager of 2.6, could you please
> > help
> > >> the
> > >> > > > folks
> > >> > > > > to finish this step?
> > >> > > > >
> > >> > > > > --
> > >> > > > > Denis
> > >> > > > >
> > >> > > > > On Tue, Jul 17, 2018 at 9:58 AM Pavel Tupitsyn <
> > >> ptupit...@apache.org>
> > >> > > > > wrote:
> > >> > > > >
> > >> > > > > > I think it makes sense that only PMCs have rights to do so,
> > >> > > > > > especially because publishing a package can not be undone of
> > >> re-done,
> > >> > > > > only
> > >> > > > > > a new version can be published if there is some issue.
> > >> > > > > > Also, restricted SVN area is the only feasible way to share
> > >> secrets
> > >> > > > with
> > >> > > > > > the team that I know of.
> > >> > > > > >
> > >> > > > > > Another approach could be NuGet Organizations, where
> > membership
> > >> is
> > >> > > > > managed
> > >> > > > > > on NuGet website.
> > >> > > > > > What do you think?
> > >> > > > > >
> > >> > > > > > On Tue, Jul 17, 2018 at 7:32 PM Petr Ivanov <
> > >> mr.wei...@gmail.com>
> > >> > > > wrote:
> > >> > > > > >
> > >> > > > > > > Oh, I see.
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > > > I have no access there. I guess only PMC can upload
> packages
> > >> to
> > >> > > > > > nuget.org
> > >> > > > > > > …
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > > > > On 17 Jul 2018, at 18:21, Pavel Tupitsyn <
> > >> ptupit...@apache.org>
> > >> > > > > wrote:
> > >> > > > > > > >
> > >> > > > > > > > Oh sorry I missed the question.
> > >> > > > > > > > * The build script '[Prepare Vote #3] Build NuGet
> > packages'
> > >> > > > produces
> > >> > > > > > the
> > >> > > > > > > > artifacts (.nupkg files).
> > >> > > > > > > > * Then we have to manually upload them to NuGet org,
> which
> > >> > > requires
> > >> > > > > an
> > >> > > > > > > API
> > >> > > > > > > > key or an account with access to these packages
> > >> > > > > > > >
> > >> > > > > > > > API key can be found in [1] (which is linked in [2])
> > >> > > > > > > >
> > >> > > > > > > > Upload can be done with a command like 'ls *.nupkg | % {
> > >> nuget
> > >> > > push
> > >> > > > > > > > $_.FullName APIKEY }' (Powershell),
> > >> > > > > > > > or a similar one on Linux/Mac with .NET Core or Mono.
> > >> > > > > > > >
> > >> > > > > > > > Let me know if you need more details.
> > >> > > > > > > >
> > >> > > > > > > > [1]
> > >> > > > > > >
> > >> > > >
> > >> https://svn.apache.org/repos/private/pmc/ignite/credentials/nuget.org
> > >> > > > > > > > [2] https://cwiki.apache.org/confluence/display/IGNITE/
> > >> > > > > Release+Process
> > >> > > > > > > >
> > >> > > > > > > > On Tue, Jul 17, 2018 at 5:55 PM Petr Ivanov <
> > >> mr.wei...@gmail.com
> > >> > > >
> > >> > > > > > wrote:
> > >> > > > > > > >
> > >> > > > > > > >> Just tell us please HOW it should be done, please.
> > >> > > > > > > >>
> > >> > > > > > > >> With what build or script or other procedure?
> > >> > > > > > > >>
> > >> > > > > > > >>
> > >> > > > > > > >>
> > >> > > > > > > >>
> > >> > > > > > > >>> On 17 Jul 2018, at 17:44, Pavel Tupitsyn <
> > 

Re: Quick questions on segments and page map buckets

[John Wilson]

I'm talking about PageMemoryNostoreImpl here:
https://github.com/apache/ignite/blob/ce8e31e28e16c7c22fe88ab6b1a1304b14f6881d/modules/core/src/main/java/org/apache/ignite/internal/pagemem/impl/PageMemoryNoStoreImpl.java#L109
and
https://github.com/apache/ignite/blob/ce8e31e28e16c7c22fe88ab6b1a1304b14f6881d/modules/core/src/main/java/org/apache/ignite/internal/pagemem/impl/PageMemoryNoStoreImpl.java#L208

Thanks,

On Thu, Jul 12, 2018 at 10:31 AM, Dmitry Pavlov 
wrote:

> Hi, I've double checked code regarding question 1:
>
> PageMemoryImpl#segments segments count (len) comes from sizes array len.
> Sizes array come to page memory from
> GridCacheDatabaseSharedManager.calculateFragmentSizes(). This method which
> gets availableProcessors from runtime (CPU count). I didn't find any shift
> to SEG_BITS.
>
> It can be chaged by DataStorageConfiguration.setConcurrencyLevel() but by
> default is the same with #CPU.
>
> Which is why I mentioned segments count = CPU count by default in wiki.
>
> Recenly some member of community proposed update to offical doc about
> segments count. So now it states #segments=#CPU.
>
> So I guess for 8 CPU we will have 8 segments.
>
> Please correct me if I missing something.
>
> Sincerely,
> Dmitriy Pavlov
>
> ср, 27 июн. 2018 г. в 15:30, Eduard Shangareev <
> eduard.shangar...@gmail.com
> >:
>
> > Dmitry,
> >
> > I mean Chugunov, but I have questioned him. His answer was the A.
> Goncharuk
> > should now the answer.
> >
> > On Wed, Jun 27, 2018 at 2:58 PM, Dmitry Pavlov 
> > wrote:
> >
> > > John, is this question still actual?
> > >
> > > пт, 22 июн. 2018 г. в 15:18, Dmitry Pavlov :
> > >
> > > > Hi Ed,
> > > >
> > > > Which Sergey do you mean? I know a number of contributors.
> > > >
> > > > Sincerely,
> > > >
> > > >
> > > > вт, 19 июн. 2018 г. в 22:15, Eduard Shangareev <
> > > > eduard.shangar...@gmail.com>:
> > > >
> > > >> Hi,
> > > >>
> > > >> 1. It looks weird, yeah. Need to ask Sergey, who has changed it last
> > > time.
> > > >>
> > > >> 2. Because we could reuse memory. For example, after cache destroy
> or
> > > >> something like that.
> > > >>
> > > >> On Tue, Jun 19, 2018 at 9:58 PM, John Wilson <
> sami.hailu...@gmail.com
> > >
> > > >> wrote:
> > > >>
> > > >> > Hi,
> > > >> >
> > > >> > Two quick questions:
> > > >> >
> > > >> >
> > > >> >1. The design documentation here,
> > > >> >https://cwiki.apache.org/confluence/display/IGNITE/
> > > >> > Ignite+Durable+Memory+-+under+the+hood,
> > > >> >states that the default segment count is equal to the number of
> > > >> logical
> > > >> >cores available in the underlying machine. However, the
> segments
> > > >> array
> > > >> > in
> > > >> >PageMemory indicates that the maximum number of segments is: 1
> <<
> > > >> > SEG_BITS.
> > > >> >Since SEG_BITS = 4, the max # segments is 16. Did I miss
> > something
> > > >> here?
> > > >> >2. Reading the code in PageMemoryNoStoreImp, it looks like
> pages
> > > are
> > > >> >allocated segment sequentially in a bump-the-pointer strategy
> > where
> > > >> the
> > > >> >first 8 bytes of a segment hold a pointer to the index of the
> > last
> > > >> >allocated page. If this is true, then I don't understand the
> > point
> > > of
> > > >> >having a page map buckets. Why not use a simple arithmetic
> index
> > *
> > > >> > pageSize
> > > >> >to get the offset of a page?
> > > >> >
> > > >> > Thanks.
> > > >> > John
> > > >> >
> > > >>
> > > >
> > >
> >
>

[jira] [Created] (IGNITE-9058) Update Apache Tomcat dependency version

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-9058:
--

 Summary: Update Apache Tomcat dependency version
 Key: IGNITE-9058
 URL: https://issues.apache.org/jira/browse/IGNITE-9058
 Project: Ignite
  Issue Type: Improvement
Reporter: Dmitriy Pavlov


Update tomcat-servlet-api to newer version (at least 8.0.52,  8.5.31+ or 9.0.8+)
{noformat}

org.apache.tomcat
tomcat-servlet-api
8.0.52

{noformat}

At least Ignite-rest-http, ignite-urideploy, and ignite-web will be affected by 
this change.

It is required to run TC tartget RunAll to check all tests passed, it is 
required to build fabric using DEVNOTES.txt to make sure full build will be 
successfull

Probably it is required to run release step to make sure release candidate can 
be prepared.



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

[jira] [Created] (IGNITE-9057) Update JCraft dependency version in Apache Ignite

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-9057:
--

 Summary: Update JCraft dependency version in Apache Ignite
 Key: IGNITE-9057
 URL: https://issues.apache.org/jira/browse/IGNITE-9057
 Project: Ignite
  Issue Type: Improvement
Reporter: Dmitriy Pavlov
 Fix For: 2.7


Update ignite-ssh dependency version of com.jcraft:jsch to 0.1.54
{noformat}

com.jcraft
jsch
0.1.54

{noformat}

It is required to run TC tartget RunAll to check all tests passed, it is 
required to build fabric using DEVNOTES.txt to make sure full build will be 
successfull

Probably it is required to run release step to make sure release candidate can 
be prepared.




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

[jira] [Created] (IGNITE-9056) BinaryTypeMismatchLoggingTest.testEntryWriteQueryEntities is flaky

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-9056:


 Summary: BinaryTypeMismatchLoggingTest.testEntryWriteQueryEntities 
is flaky
 Key: IGNITE-9056
 URL: https://issues.apache.org/jira/browse/IGNITE-9056
 Project: Ignite
  Issue Type: Test
Reporter: Alexey Goncharuk
 Fix For: 2.7


The test fails because the captured message contains more than one occurence of 
the payload value.
Need to investigate the root cause.



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

[GitHub] ignite pull request #4405: IGNITE-9035 Update log4j 2x version in Apache Ign...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4413: IGNITE-8596: Avoid map requests to non-affinity i...

[AMashenkov]

GitHub user AMashenkov opened a pull request:

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

IGNITE-8596: Avoid map requests to non-affinity index segments.



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

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

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

https://github.com/apache/ignite/pull/4413.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 #4413


commit bbf64a298d4eeb7cae3b78c14d86302c530a73dc
Author: Andrey V. Mashenkov 
Date:   2018-07-23T16:14:51Z

IGNITE-8596: Avoid map requests to non-affinity index segments.




---

[GitHub] ignite pull request #4412: IGNITE-9055 Update Cache Based Dataset so that it...

[dmitrievanthony]

GitHub user dmitrievanthony opened a pull request:

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

IGNITE-9055 Update Cache Based Dataset so that it ignores empty parts



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

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

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

https://github.com/apache/ignite/pull/4412.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 #4412


commit 2d723a675aad7e2263cea69fe0198ef118c0515b
Author: Anton Dmitriev 
Date:   2018-07-23T16:18:59Z

IGNITE-9055 Update Cache Based Dataset so that it ignores empty parts.




---

[GitHub] ignite pull request #4411: Ignite 2.5.1 p11

[akalash]

GitHub user akalash opened a pull request:

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

Ignite 2.5.1 p11



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

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

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

https://github.com/apache/ignite/pull/4411.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 #4411


commit b96271866aeb09b434e2b95a457655a44d913254
Author: Alexander Kalinin 
Date:   2018-04-11T10:09:41Z

IGNITE-4091 Web Console: Refactored using of internal Angular API.

(cherry picked from commit 74d2545)

commit 2be10fdcde3c529b866f85a5b74ff3d471c5c9c7
Author: Ilya Kasnacheev 
Date:   2018-04-11T12:32:52Z

IGNITE-8106 Collect suppressed exceptions from causes. - Fixes #3735.

Signed-off-by: Alexey Kuznetsov 

(cherry picked from commit 98ef925)

commit 7f463be9ff6c5d2d84b0aacc888159ffe68bf269
Author: Alexander Paschenko 
Date:   2018-04-11T13:20:16Z

IGNITE-8204: SQL: fixed hangs when lazy flag is enabled. This closes #3785.

commit 7eee6e24736d8c0958e0107471c47ef4035037d8
Author: Alexey Kukushkin 
Date:   2018-04-11T13:29:07Z

IGNITE-8221: Security for thin clients.

commit b6ad3705c1e68683b72d2237037af66fea23a7ae
Author: devozerov 
Date:   2018-04-11T13:44:33Z

IGNITE-8148: JDBC thin: semicolon as delimiter for properties. This closes 
#3794.

commit e6c30e17c6f0f1852fa781078ee54ccf8c654846
Author: Pavel Kovalenko 
Date:   2018-04-11T11:12:50Z

IGNITE-7871 Check local join future on error. - Fixes #3793.

Signed-off-by: dpavlov 

commit 2769981a5df64f3cd0c38b7599c49580c66192fa
Author: Aleksey Plekhanov 
Date:   2018-04-11T15:24:51Z

IGNITE-6892 OOM should be covered by failure handling

Signed-off-by: Andrey Gura 

commit 687194461f445be9902752f38f873d321cde1d85
Author: Ilya Borisov 
Date:   2018-04-06T04:17:05Z

IGNITE-7996 Move configuration form templates.

(cherry picked from commit c2c03a9)

commit 9955728a72e0f9c11faa313a521d4566b5a93dc1
Author: Ilya Borisov 
Date:   2018-04-06T04:19:07Z

IGNITE-7996 Move config state module index.

(cherry picked from commit d5e0be0)

commit 536d8b2080b93505e67206a240385baced150674
Author: Ilya Borisov 
Date:   2018-04-06T04:20:13Z

IGNITE-7996 Use configuration.state for state registration only.

(cherry picked from commit 2800ef0)

commit a2d9f97c0ae77e81344849bc2c3cba2d3964cf01
Author: Ilya Borisov 
Date:   2018-04-06T04:20:39Z

IGNITE-7996 Rename configuration.state to states.

(cherry picked from commit 14dd2df)

commit 1d5f45b4eb900a3c4cc0bedb8919b35f2a0032c8
Author: Ilya Borisov 
Date:   2018-04-06T04:22:20Z

IGNITE-7996 Move configuration assets into page-configure module.

(cherry picked from commit d02e87b)

commit a5a83d211a572b8419866fabbc31975168157729
Author: Alexey Kuznetsov 
Date:   2018-04-12T04:21:23Z

IGNITE-7996 Merge with master.

commit dbf2d722b0563a9637cc72fe2fcdf3dbd07291fc
Author: devozerov 
Date:   2018-04-12T07:37:36Z

IGNITE-8042: .NET thin client: authentication support. This closes #3790.

commit 72259b01e0c6d72794eca4c28c9d9d848b0ff97f
Author: dmitrievanthony 
Date:   2018-04-12T08:16:22Z

IGNITE-8176: Integrate gradient descent linear regression with partition 
based dataset

this closes #3787

(cherry picked from commit df6356d)

commit f143ad0057ddb326f6d8199bf660b354913e6b61
Author: devozerov 
Date:   2018-04-12T12:02:57Z

IGNITE-8135: SQL: authentication for CREATE TABLE and DROP TABLE commands. 
This closes #3801.

commit 2c4a7a2e366d7308485ae5cc95d4b60e66b09589
Author: devozerov 
Date:   2018-04-12T12:13:51Z

IGNITE-8230: SQL: Fixed backup number propagation in CREATE TABLE command. 
This closes #3803.

commit 80f4340f61742988aaf9437eb08ed76644a1c8ca
Author: Pavel Kovalenko 
Date:   2018-04-12T11:29:43Z

IGNITE-7871 Fixed condition for cache partitions validation. - Fixes #3804.

Signed-off-by: dpavlov 

(cherry picked from commit 7a1d0ea)

commit dfe17074593d9d12cbab7b60aa73e73c37bbffb7
Author: Anton Kurbanov 
Date:   2018-04-12T17:31:50Z

IGNITE-8110 GridCacheWriteBehindStore.Flusher thread uses the wrong 
transformation from milliseconds to nanoseconds. - Fixes #3742.

Signed-off-by: dpavlov 

(cherry picked from commit adaedb4)

commit fe99497528cd040ab3b4d5f7bfc40e788393a5ed
Author: Andrey Kuznetsov 
Date:   2018-04-12T18:23:28Z

IGNITE-7983: NPE fixed in transactions

Signed-off-by: Andrey Gura 

commit 6a77dd8b182091fe4e38850098c6334597c14a6d
Author: zaleslaw 
Date:   2018-04-13T09:49:56Z

IGNITE-7829: Adopt kNN regression example to the new Partitioned Dataset

this closes #3798

(cherry picked from commit 8550d61)

commit 

[GitHub] ignite pull request #4410: Ignite 2.4.7 p1

[dkarachentsev]

GitHub user dkarachentsev opened a pull request:

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

Ignite 2.4.7 p1



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

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

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

https://github.com/apache/ignite/pull/4410.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 #4410


commit 9c6a52250e058c4546aef0d0ecee977c07076a1a
Author: Alexey Kuznetsov 
Date:   2018-02-02T10:09:37Z

IGNITE-7612 Web Console: Refactored mongoose schemas to separate module.

(cherry picked from commit 71db707)

commit 89e15830dedcb46f24d9cc9b922ba3b013331a18
Author: Vasiliy Sisko 
Date:   2018-02-12T10:22:10Z

Web Agent: Fixed wrong config of IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE in 
demo startup.

(cherry picked from commit 1a6e544)

commit 18966673570425192e1b89fbb2c63d164b47eaca
Author: Vasiliy Sisko 
Date:   2018-02-12T13:24:30Z

IGNITE-7578 Actualized client connector configuration.

(cherry picked from commit 819d746)

commit 237063efa35c54bb9e9800ecf63ea223ec20a9ef
Author: alexdel 
Date:   2018-02-19T04:25:24Z

IGNITE-7650 Extracted signin/signup form to separate page, improved landing 
page.

(cherry picked from commit 1925674)

commit 679aeca7a3ff60a9dd478966d3949107d302d5db
Author: Andrey Novikov 
Date:   2018-02-19T07:56:07Z

IGNITE-7650 Fixed headers.

(cherry picked from commit 67922b3)

commit 5d5a6a05ec49f895e8a5edd505e496dcfe58a208
Author: Vasiliy Sisko 
Date:   2018-02-21T04:21:02Z

IGNITE-6094 Web Agent: Enabled persistent in demo mode.

(cherry picked from commit 3c35900)

commit e35d8cfb06f52765959fc2e1883bf70fe0259f45
Author: Alexander Kalinin 
Date:   2018-02-21T07:03:20Z

IGNITE-7320 Web Console - Fixed table headers for Safari.

(cherry picked from commit 04a025b)

commit 20cb1439f48b9a3c985f65784af36ef2c6f45e4f
Author: Andrey Novikov 
Date:   2018-02-22T02:54:05Z

IGNITE-7650 Fixed counties codes.

(cherry picked from commit fc40261)

commit 50d1389cd60e148005701e3450c8ae9998fd5fc9
Author: Alexey Kuznetsov 
Date:   2018-02-22T03:28:32Z

IGNITE-6287 Web Console: Fixed regression for EXPLAIN.

(cherry picked from commit 2bee8f8)

commit 330e502d5effea485254151ebf9b666e67d68475
Author: Alexander Kalinin 
Date:   2018-02-26T08:13:52Z

IGNITE-7729. Web Console. Added roles support in E2E tests.

(cherry picked from commit a83b264)

commit 3579db951abec81b7201ad91326ddc73ee828387
Author: Vasiliy Sisko 
Date:   2018-01-26T03:22:50Z

IGNITE-7392 Visor Cmd: Added missing word 'factory'.

(cherry picked from commit c0b14e5)

commit c125fa2068b62ab5286888ab2a16b5b034964dfd
Author: Vasiliy Sisko 
Date:   2018-02-12T03:13:06Z

IGNITE-2093 Visor CMD: Added support to scan near cache.

(cherry picked from commit a5a907b)

commit 2f074c05492439e1860a6920fff2861a071b58a8
Author: Alexey Kuznetsov 
Date:   2018-02-28T11:53:26Z

IGNITE-7578 Backport for ignite-2.4.3.

commit 8b1e77bac2d4fe125463f8978ca905d34a45b82f
Author: Alexey Kuznetsov 
Date:   2018-02-28T11:57:53Z

ignite-2.4.3 Fixed versions list.

commit bad7053586cccbbae4eb3d6dcba0d1ada5d2d2f2
Author: Alexey Kuznetsov 
Date:   2018-03-01T09:18:17Z

IGNITE-6920 Fixed missed require.

(cherry picked from commit fe89fc4)

commit 0294cf293ea35a355f18b218b842ec60e2583f42
Author: devozerov 
Date:   2018-03-01T12:11:39Z

Merge branch 'ignite-2.4' into ignite-2.4.3

commit e899d0a0fa8fb1692ddc7f74ee43dc9ca50f885d
Author: Pavel Kovalenko 
Date:   2018-03-01T12:41:52Z

IGNITE-7717 Fixed missed updateTopologyVersion call in case of a merged 
exchange - Fixes #3536.

Signed-off-by: Alexey Goncharuk 

commit 1948dc73f36ddfda6bc55b9c1ea7421fb8c62ff1
Author: Sergey Kosarev 
Date:   2018-02-12T03:51:57Z

IGNITE-7485 Added support for authentication parameters in control.sh.

(cherry picked from commit f53c48a)

commit 20611b28b89adde162ad380cb3a6d9bd4608eb8b
Author: Vasiliy Sisko 
Date:   2018-03-01T16:13:53Z

IGNITE-7462 Web Console: Actualized configuration generation.

(cherry picked from commit 30fab74)

commit d4a07b6f195be963cc7f48bb4d63829e348948cf
Author: alexdel 
Date:   2018-03-02T02:30:29Z

IGNITE-7033 Web console: Adjusted width of columns on admin page.

(cherry picked from commit 6733a4d)

commit e6dda9769568bcd1538005e21256d2ff3a1f7b73
Author: devozerov 
Date:   2018-03-02T10:48:31Z

Merge branch 'ignite-2.4' into ignite-2.4.3

commit f9ce2c07046a1a413ea69ef5d32f91af70c06863
Author: Dmitriy Govorukhin 
Date:   2018-03-02T12:11:50Z

IGNITE-7865 Supported serializerVersion method for WAL manager - Fixes 
#3594.

Signed-off-by: Alexey Goncharuk 

(cherry picked from 

[GitHub] ignite pull request #4338: IGNITE-8968 Failed to shutdown node due to "Error...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4409: IGNITE-9045 additional check for NodeStoppingExce...

[sergey-chugunov-1985]

GitHub user sergey-chugunov-1985 opened a pull request:

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

IGNITE-9045 additional check for NodeStoppingException before changing tx 
future state



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

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

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

https://github.com/apache/ignite/pull/4409.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 #4409


commit d21b9913f5c0b930968d137469bb4ab234b82fca
Author: Sergey Chugunov 
Date:   2018-07-23T15:25:06Z

IGNITE-9045 additional check for NodeStoppingException before changing tx 
future state




---

[GitHub] ignite pull request #4401: IGNITE-9049 fix write SWITCH_SEGMENT_RECORD in th...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4358: IGNITE-8998 Send reconnect exception without part...

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Documenting Ignite

[Artem Budnikov]

Hi everyone,

I created an issue in the Apache INFRA project: 
https://issues.apache.org/jira/browse/INFRA-16803


Cheers,

Artem


On 19.07.2018 22:58, Dmitry Pavlov wrote:

I appologize, initially I misundersood proposal. I've concluded that new
doc issue will be created automatically by closing original ticket, - this
can be done by plugin only.

If we just introduce flag or combobox for indicate doc is required, there
is no technical issues, it is defenetely possible. So +1 from my side
without concerns.

чт, 19 июл. 2018 г. в 22:02, Denis Magda :


Ok, if all our doc writers are in the agreement then let's give a couple of
days to our fellow Igniters to share alternate opinions.

Artem, if you don't hear back by Monday then feel free to create an INFRA
ticket.

--
Denis

On Thu, Jul 19, 2018 at 10:43 AM Prachi Garg  wrote:


I totally agree with Denis's point -

"Another benefit of having "Docs Required" flag enabled by default, is

that

Artem and Prachi can see all such tickets months and weeks before a
release, figure out details from source code contributors and complete

the

docs in advance."

On Wed, Jul 18, 2018 at 2:49 PM, Dmitry Pavlov 
wrote:


Yes, I agree. My concern is related only to process implementation

aspect,

I wonder if it is technically possible.

Generally I like idea of automatic control.

ср, 18 июл. 2018 г. в 23:21, Denis Magda :


Hi folks,

Artem's proposal might simplify and make our doc tickets tracking less
error-prone. The current approach implies that a contributor keeps in

mind

what needs to go to the docs. If he/she has a good memory, a doc JIRA
counterpart will be created once the contribution is accepted. But the
practice shows that the memory lets us down :)

Another benefit of having "Docs Required" flag enabled by default, is

that

Artem and Prachi can see all such tickets months and weeks before a
release, figure out details from source code contributors and complete

the

docs in advance.

--
Denis

On Wed, Jul 18, 2018 at 8:39 AM Artem Budnikov <
a.budnikov.ign...@gmail.com> wrote:


Dmitry,

The goal I had in mind by proposing that suggestion was to rectify

the

fact that JIRA issues for documentation are created on an ad-hoc

basis,

and often issues are created when the lack of documentation becomes

an

issue for somebody. So we need to be more proactive.

I think manual tracking of issues is possible but as efficient as the
current situation with the docs. Manual tracking will have to be

shared

between multiple contributors and performed outside of JIRA, which

has

its own limitation. If you have any suggestions for improvement

without

creating fields in JIRA, please share your thoughts.

If you are concerned that it's not possible to add a field, then we
should contact Apache Infra and find out.


Best regards,

Artem Budnikov


On 18.07.2018 16:14, Dmitry Pavlov wrote:

Hi Artem,

I sometimes receive feedback that Ignite docs has potential for
improvement, while I found our docs quite intuitive and simple to
understand. So if experienced tech writer will join community it

could

benefit all of us, and users, of course. So you're very welcome to

the

community!

About idea of fields introduction I guess we will need assistance

of

Apache

Infra team, because Ignite shares JIRA with all other Apache

project.

And

I'm not sure that technical implementation of proposed process is

even

possible without plugins. Could we consider some manual processing

of

completed issues in relation to doc requrement?

Sincerely,
Dmitriy Pavlov

ср, 18 июл. 2018 г. в 15:06, Artem Budnikov <

a.budnikov.ign...@gmail.com>:

Hi Igniters,

Being a technical writer, I'm going to contribute to Ignite's
documentation, and I believe documentation is an important part of

every

product, especially such a complex product as Apache Ignite.

I'd like to put forward a suggestion on how to increase our

chances

of

making Ignite documentation more comprehensive. The basic idea is

to

have a Jira issue with the Component field set to "Documentation"

for

every feature that needs to be documented. This will ensure that

there

are documentation issues that cover the entire product

functionality.

Then someone can take on an issue and contribute an article on the

subject.

This is how I envision it to work technically. A new field

(checkbox)

is

added to the Apache Ignite Jira project. The checkbox indicates

that

the

feature requested in this issue needs to be documented. The

checkbox is

selected by default. If the feature does not require

documentation,

then

the author unchecks the checkbox. If it does require

documentation,

the

author creates a related Jira issue selecting "Documentation" in

the

Component field, providing details on what exactly should be

documented.

The field is called "Requires documentation" or similarly. It

could

be

also useful to create a new issue type for documentation issues
exclusively.

Once this is done, we'll be 

[GitHub] ignite pull request #4408: ignite 9040 - alternative fix

[sergey-chugunov-1985]

GitHub user sergey-chugunov-1985 opened a pull request:

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

ignite 9040 - alternative fix



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

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

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

https://github.com/apache/ignite/pull/4408.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 #4408


commit 1a76eab2912f7b8925c051c76763e87511d4
Author: Sergey Chugunov 
Date:   2018-07-20T14:27:05Z

IGNITE-9040 new FailureHandler for node segmentation special case, test for 
the root cause error

commit bba7a826401d3ea18cf43f660795853db222f6b0
Author: Sergey Chugunov 
Date:   2018-07-23T14:05:45Z

IGNITE-9040 alternative fix for stop-on-segmentation issue

commit 4636e9bc73437a2cb5a078299e8cdd842df27776
Author: Sergey Chugunov 
Date:   2018-07-23T14:57:57Z

IGNITE-9040 quick impl to guarantee STOPPED_ON_SEGMENTATION state




---

[jira] [Created] (IGNITE-9055) [ML] SVM throws NPE in case of empty partitions

[Anton Dmitriev (JIRA)]

Anton Dmitriev created IGNITE-9055:
--

 Summary: [ML] SVM throws NPE in case of empty partitions
 Key: IGNITE-9055
 URL: https://issues.apache.org/jira/browse/IGNITE-9055
 Project: Ignite
  Issue Type: Bug
  Components: ml
Affects Versions: 2.5, 2.6
Reporter: Anton Dmitriev
 Fix For: 2.7


Method `calculateUpdates` throws NPE in case of empty partitions. Reduce 
function user in this method doesn't handle correctly empty arguments (`(a, b) 
-> a == null ? b : a.plus(b))`).

We need to fix this reduce function or update Partition Based Dataset so that 
it doesn't emit empty arguments.



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

[GitHub] ignite pull request #4404: IGNITE-9051 'Remove unnecessary ssh tests'

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4407: IGNITE-8930: Cursors are closed properly by ODBC ...

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-8930: Cursors are closed properly by ODBC  now



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

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

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

https://github.com/apache/ignite/pull/4407.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 #4407


commit cf5269b554a43e6add7fe67d5d9f1481a7858246
Author: Igor Sapego 
Date:   2018-07-23T13:05:06Z

IGNITE-8930: Added test

commit 8525b8d8a0de153ae94177fdaa2d3ae74c23f0d2
Author: Igor Sapego 
Date:   2018-07-23T13:11:28Z

IGNITE-8930: Fix




---

[GitHub] ignite pull request #4166: IGNITE-8131 ZookeeperDiscoverySpiTest#testClientR...

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Implementing custom affinity logic

[Dmitry Pavlov]

Hi,

 In case these questions are not related to some PR/Issue or contribution,
than user list probably is better place to ask these questions.

Sincerely,
Dmitriy Pavlov

пн, 23 июл. 2018 г. в 13:24, kotamrajuyashasvi :

> Hi
>
> I m working on an ignite project where I want to have certain records to be
> collocated based
> on a custom calculated value which is obtained from the fields of the
> primary key object.
>
> For example the Primary key pojos have fields a,b,c. I want all records
> having same value of (a+b)/c
> collocated on same node/partition.
>
> I have gone through the ignite documentation and found that custom
> AffinityKeyMapper is the
> one that can be used. Also there is an option to use custom Affinity
> function but extra logic has to be added for partition to node mapping
> etc..
>
> 1. How can I achieve my above requirement? What are the correct options and
> where can
> I get a working example of custom AffinityKeyMapper or AffinityFunction
> ?
>
> 2. Once after achieving custom affinity how to test if all records are
> getting collocated as expected. One
> option that I found was to use scan query and scan a particular
> partition and test each record if it
> should actually belong to the scanned partition. But if there are huge
> number of records I'm facing
> OOM while running scan query for a partition. So I would like to know
> how to achieve this/ test to
> confirm for sure the collocation is as expected.
>
> 3. What is the performance impact of using custom affinity logic when
> compared to using no affinity and
> using @AffinityKeyMapped annotation to achieve affinity where the
> scenario is to collocate based on
> a single field.
>
> 4. When using @AffinityKeyMapped or no affinity is used, is
>
>
> org.apache.ignite.internal.processors.cache.GridCacheDefaultAffinityKeyMapper
> is used as default
> AffinityKeyMapper ? or there is any other default module that is used
> for calculating affinity ?
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[GitHub] ignite pull request #4406: IGNITE-9036 change version jersey2 from 2.6.5 to ...

[dgarus]

GitHub user dgarus opened a pull request:

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

IGNITE-9036 change version jersey2 from 2.6.5 to 2.9.6



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

$ git pull https://github.com/dgarus/ignite ignte-9036

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

https://github.com/apache/ignite/pull/4406.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 #4406


commit 472f34239619af530db9c7a69decb7428af23da5
Author: Garus Denis 
Date:   2018-07-23T13:04:52Z

IGNITE-9036 change version jersey2 from 2.6.5 to 2.9.6




---

Re: Apache Ignite 2.7: scope, time and release manager

[Dmitry Pavlov]

Hi Denis, Nikolay,

I've issued a number of tickets to update dependencies versions. I would
like all these updates are available within 2.7.

Sincerely,
Dmitriy Pavlov

сб, 21 июл. 2018 г. в 3:28, Pavel Petroshenko :

> Hi Denis, Nikolay,
>
> The proposed 2.7 release timing sounds reasonable to me.
> Python [1], PHP [2], and Node.js [3] thin clients should take the train.
>
> p.
>
> [1] https://jira.apache.org/jira/browse/IGNITE-7782
> [2] https://jira.apache.org/jira/browse/IGNITE-7783
> [3] https://jira.apache.org/jira/browse/IGNITE-
>
>
> On Fri, Jul 20, 2018 at 2:35 PM, Denis Magda  wrote:
>
> > Igniters,
> >
> > Let's agree on the time and the scope of 2.7. As for the release manager,
> > we had a conversation with Nikolay Izhikov and he decided to try the role
> > out. Thanks, Nikolay!
> >
> > Nikolay, we need to prepare a page like that [1] once the release terms
> are
> > defined.
> >
> > I propose us to roll Ignite 2.7 at the end of September. Folks who are
> > working on SQL, core, C++/NET, thin clients, ML, service grid
> > optimizations, data structures please enlist what you're ready to
> deliver.
> >
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6
> >
>

[jira] [Created] (IGNITE-9054) ScanQuery responses are serialized with Optimized Marshaller

[Ilya Kasnacheev (JIRA)]

Ilya Kasnacheev created IGNITE-9054:
---

 Summary: ScanQuery responses are serialized with Optimized 
Marshaller
 Key: IGNITE-9054
 URL: https://issues.apache.org/jira/browse/IGNITE-9054
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.5
Reporter: Ilya Kasnacheev
 Attachments: 22530.diff

When you do ContinuousQuery on a cache, its initial query sends results via 
OptimizedMarshaller (which has binary compatibility implications) but its 
continuous part uses BinaryMarshaller. They should both be using 
BinaryMarshaller. Fix seems to be one-liner, see patch and userlist thread.



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

Re: [RESULT] [VOTE] Apache Ignite 2.6.0 Release (RC1)

[Ilya Kasnacheev]

Hello!

It doesn't seem that we have 2.6 in Released Versions in JIRA. Only 2.5 is
available.

Regards,

-- 
Ilya Kasnacheev

2018-07-18 23:48 GMT+03:00 Denis Magda :

> Added the step about the version in this file -
> https://ignite.apache.org/latest
>
> --
> Denis
>
> On Wed, Jul 18, 2018 at 9:10 AM Anton Vinogradov  wrote:
>
> > It looks like we have to update release page with steps forgotten on this
> > iteration.
> >
> >
> > ср, 18 июл. 2018 г. в 18:16, Andrey Gura :
> >
> >> Latest version is updated.
> >>
> >> Thanks!
> >> On Wed, Jul 18, 2018 at 4:50 PM Dmitriy Setrakyan <
> dsetrak...@apache.org>
> >> wrote:
> >> >
> >> > Andrey Gura, can you please update it?
> >> >
> >> > D.
> >> >
> >> > On Wed, Jul 18, 2018 at 6:34 AM, Dmitry Pavlov  >
> >> > wrote:
> >> >
> >> > > Hi Ilya,
> >> > >
> >> > > Thank you for noticing this.
> >> > >
> >> > > We should somehow update https://ignite.apache.org/latest data. I
> >> guess
> >> > > PMCs or site admin can do this update.
> >> > >
> >> > > Sincerely,
> >> > > Dmitriy Pavlov
> >> > >
> >> > > ср, 18 июл. 2018 г. в 16:31, Ilya Kasnacheev <
> >> ilya.kasnach...@gmail.com>:
> >> > >
> >> > > > Hello!
> >> > > >
> >> > > > Since we have releases 2.6.0, can we perhaps prop up the node
> start
> >> > > > message, which is currently still:
> >> > > >
> >> > > > [16:28:05] New version is available at ignite.apache.org: 2.4.0
> >> > > >
> >> > > > Regards,
> >> > > >
> >> > > > --
> >> > > > Ilya Kasnacheev
> >> > > >
> >> > > > 2018-07-17 21:59 GMT+03:00 Denis Magda :
> >> > > >
> >> > > > > Andrey G.,
> >> > > > >
> >> > > > > As a PMC member and release manager of 2.6, could you please
> help
> >> the
> >> > > > folks
> >> > > > > to finish this step?
> >> > > > >
> >> > > > > --
> >> > > > > Denis
> >> > > > >
> >> > > > > On Tue, Jul 17, 2018 at 9:58 AM Pavel Tupitsyn <
> >> ptupit...@apache.org>
> >> > > > > wrote:
> >> > > > >
> >> > > > > > I think it makes sense that only PMCs have rights to do so,
> >> > > > > > especially because publishing a package can not be undone of
> >> re-done,
> >> > > > > only
> >> > > > > > a new version can be published if there is some issue.
> >> > > > > > Also, restricted SVN area is the only feasible way to share
> >> secrets
> >> > > > with
> >> > > > > > the team that I know of.
> >> > > > > >
> >> > > > > > Another approach could be NuGet Organizations, where
> membership
> >> is
> >> > > > > managed
> >> > > > > > on NuGet website.
> >> > > > > > What do you think?
> >> > > > > >
> >> > > > > > On Tue, Jul 17, 2018 at 7:32 PM Petr Ivanov <
> >> mr.wei...@gmail.com>
> >> > > > wrote:
> >> > > > > >
> >> > > > > > > Oh, I see.
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > I have no access there. I guess only PMC can upload packages
> >> to
> >> > > > > > nuget.org
> >> > > > > > > …
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > > On 17 Jul 2018, at 18:21, Pavel Tupitsyn <
> >> ptupit...@apache.org>
> >> > > > > wrote:
> >> > > > > > > >
> >> > > > > > > > Oh sorry I missed the question.
> >> > > > > > > > * The build script '[Prepare Vote #3] Build NuGet
> packages'
> >> > > > produces
> >> > > > > > the
> >> > > > > > > > artifacts (.nupkg files).
> >> > > > > > > > * Then we have to manually upload them to NuGet org, which
> >> > > requires
> >> > > > > an
> >> > > > > > > API
> >> > > > > > > > key or an account with access to these packages
> >> > > > > > > >
> >> > > > > > > > API key can be found in [1] (which is linked in [2])
> >> > > > > > > >
> >> > > > > > > > Upload can be done with a command like 'ls *.nupkg | % {
> >> nuget
> >> > > push
> >> > > > > > > > $_.FullName APIKEY }' (Powershell),
> >> > > > > > > > or a similar one on Linux/Mac with .NET Core or Mono.
> >> > > > > > > >
> >> > > > > > > > Let me know if you need more details.
> >> > > > > > > >
> >> > > > > > > > [1]
> >> > > > > > >
> >> > > >
> >> https://svn.apache.org/repos/private/pmc/ignite/credentials/nuget.org
> >> > > > > > > > [2] https://cwiki.apache.org/confluence/display/IGNITE/
> >> > > > > Release+Process
> >> > > > > > > >
> >> > > > > > > > On Tue, Jul 17, 2018 at 5:55 PM Petr Ivanov <
> >> mr.wei...@gmail.com
> >> > > >
> >> > > > > > wrote:
> >> > > > > > > >
> >> > > > > > > >> Just tell us please HOW it should be done, please.
> >> > > > > > > >>
> >> > > > > > > >> With what build or script or other procedure?
> >> > > > > > > >>
> >> > > > > > > >>
> >> > > > > > > >>
> >> > > > > > > >>
> >> > > > > > > >>> On 17 Jul 2018, at 17:44, Pavel Tupitsyn <
> >> ptupit...@apache.org
> >> > > >
> >> > > > > > wrote:
> >> > > > > > > >>>
> >> > > > > > > >>> Peter,
> >> > > > > > > >>>
> >> > > > > > > >>> I can do it anytime when we confirm the right Artifacts
> >> build.
> >> > > > > > > >>> Can you please clarify what " Before uploading, please
> >> check
> >> > > this
> >> > > > > [1]
> >> > > > > > > >> build.
> >> > > > > > > >>> " is about?
> >> > > > > > > >>>
> >> > > > > > > >>> Thanks,
> 

[GitHub] ignite pull request #4399: Ignite 8820 fix

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4405: IGNITE-9035 Update log4j 2x version in Apache Ign...

[SomeFire]

GitHub user SomeFire opened a pull request:

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

IGNITE-9035 Update log4j 2x version in Apache Ignite



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

$ git pull https://github.com/SomeFire/ignite ignite-9035

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

https://github.com/apache/ignite/pull/4405.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 #4405


commit 9d2c8f409b0d8d3782cf421a6ab1b69750bfbcc1
Author: Dmitrii Ryabov 
Date:   2018-07-23T11:43:05Z

IGNITE-9035 Update log4j 2x version in Apache Ignite




---

[GitHub] ignite pull request #4404: IGNITE-9051 'Remove unnecessary ssh tests'

[1vanan]

GitHub user 1vanan opened a pull request:

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

IGNITE-9051 'Remove unnecessary ssh tests'



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

$ git pull https://github.com/1vanan/ignite IGNITE-9051

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

https://github.com/apache/ignite/pull/4404.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 #4404


commit 6e971c0b26f41c59ff534d1c1b5a95543fd39f3e
Author: Fedotov 
Date:   2018-07-23T10:55:49Z

remove unnecessary tests




---

[jira] [Created] (IGNITE-9053) testReentrantLockConstantTopologyChangeNonFailoverSafe can hang in case of broken tx

[Anton Vinogradov (JIRA)]

Anton Vinogradov created IGNITE-9053:


 Summary: testReentrantLockConstantTopologyChangeNonFailoverSafe 
can hang in case of broken tx
 Key: IGNITE-9053
 URL: https://issues.apache.org/jira/browse/IGNITE-9053
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Anton Vinogradov


-GridCachePartitionedDataStructuresFailoverSelfTest#testReentrantLockConstantTopologyChangeNonFailoverSafe
-GridCachePartitionedDataStructuresFailoverSelfTest#testCountDownLatchConstantTopologyChange
 
can hang in case of broken tx
{noformat}
 Pending transactions:
[2018-07-15 14:13:41,210][WARN 
][exchange-worker-#1596354%partitioned.GridCachePartitionedDataStructuresFailoverSelfTest1%][diagnostic]
 >>> [txVer=AffinityTopologyVersion [topVer=7, minorTopVer=0], exchWait=true, 
tx=GridDhtTxLocal [nearNodeId=1392b1bd-c807-4479-9bfe-fc9f7050, 
nearFutId=14ffca0a461-999e75d0-a333-4bd6-a2a2-7f143d0af773, nearMiniId=1, 
nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion 
[topVer=143133203, order=1531653200153, nodeOrder=1], 
super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false, nearNodes=[], 
dhtNodes=[], explicitLock=false, super=IgniteTxLocalAdapter 
[completedBase=null, sndTransformedVals=false, depEnabled=false, 
txState=IgniteTxStateImpl [activeCacheIds=[1968300681], recovery=false, 
txMap=[IgniteTxEntry [key=KeyCacheObjectImpl [part=494, 
val=GridCacheInternalKeyImpl [name=structure, 
grpName=default-volatile-ds-group], hasValBytes=true], cacheId=1968300681, 
txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=494, 
val=GridCacheInternalKeyImpl [name=structure, 
grpName=default-volatile-ds-group], hasValBytes=true], cacheId=1968300681], 
val=[op=NOOP, val=null], prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, 
val=null], entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1, 
conflictVer=null, explicitVer=null, dhtVer=null, filters=[], 
filtersPassed=false, filtersSet=false, entry=GridDhtCacheEntry [rdrs=[], 
part=494, super=GridDistributedCacheEntry [super=GridCacheMapEntry 
[key=KeyCacheObjectImpl [part=494, val=GridCacheInternalKeyImpl 
[name=structure, grpName=default-volatile-ds-group], hasValBytes=true], 
val=CacheObjectImpl [val=null, hasValBytes=true], ver=GridCacheVersion 
[topVer=143133201, order=1531653200154, nodeOrder=2], hash=2095426867, 
extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc 
[locs=[GridCacheMvccCandidate [nodeId=1bf28b00-feed-412b-a20b-ca9fc111, 
ver=GridCacheVersion [topVer=143133203, order=1531653200157, nodeOrder=2], 
threadId=1947290, id=31143709, topVer=AffinityTopologyVersion [topVer=7, 
minorTopVer=0], reentry=null, otherNodeId=1392b1bd-c807-4479-9bfe-fc9f7050, 
otherVer=GridCacheVersion [topVer=143133203, order=1531653200153, nodeOrder=1], 
mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null, serOrder=null, 
key=KeyCacheObjectImpl [part=494, val=GridCacheInternalKeyImpl [name=structure, 
grpName=default-volatile-ds-group], hasValBytes=true], 
masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
 prevVer=null, nextVer=null]], rmts=null]], flags=2]]], prepared=0, 
locked=false, nodeId=null, locMapped=false, expiryPlc=null, 
transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null, 
xidVer=GridCacheVersion [topVer=143133203, order=1531653200157, 
nodeOrder=2, super=IgniteTxAdapter [xidVer=GridCacheVersion 
[topVer=143133203, order=1531653200157, nodeOrder=2], writeVer=null, 
implicit=false, loc=true, threadId=1947290, startTime=1531653200578, 
nodeId=1bf28b00-feed-412b-a20b-ca9fc111, startVer=GridCacheVersion 
[topVer=143133203, order=1531653200157, nodeOrder=2], endVer=null, 
isolation=REPEATABLE_READ, concurrency=PESSIMISTIC, timeout=0, 
sysInvalidate=false, sys=true, plc=2, commitVer=null, finalizing=NONE, 
invalidParts=null, state=ACTIVE, timedOut=false, topVer=AffinityTopologyVersion 
[topVer=7, minorTopVer=0], duration=20632ms, onePhaseCommit=false], size=1
{noformat}



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

Implementing custom affinity logic

[kotamrajuyashasvi]

Hi

I m working on an ignite project where I want to have certain records to be
collocated based 
on a custom calculated value which is obtained from the fields of the
primary key object.

For example the Primary key pojos have fields a,b,c. I want all records
having same value of (a+b)/c 
collocated on same node/partition. 
 
I have gone through the ignite documentation and found that custom
AffinityKeyMapper is the 
one that can be used. Also there is an option to use custom Affinity
function but extra logic has to be added for partition to node mapping etc..

1. How can I achieve my above requirement? What are the correct options and
where can
I get a working example of custom AffinityKeyMapper or AffinityFunction
?

2. Once after achieving custom affinity how to test if all records are
getting collocated as expected. One
option that I found was to use scan query and scan a particular
partition and test each record if it 
should actually belong to the scanned partition. But if there are huge
number of records I'm facing 
OOM while running scan query for a partition. So I would like to know
how to achieve this/ test to 
confirm for sure the collocation is as expected.

3. What is the performance impact of using custom affinity logic when
compared to using no affinity and 
using @AffinityKeyMapped annotation to achieve affinity where the
scenario is to collocate based on 
a single field.

4. When using @AffinityKeyMapped or no affinity is used, is 
   
org.apache.ignite.internal.processors.cache.GridCacheDefaultAffinityKeyMapper
is used as default 
AffinityKeyMapper ? or there is any other default module that is used
for calculating affinity ?




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

[GitHub] ignite pull request #4403: IGNITE-9009 Don't process backup updates for loca...

[dmekhanikov]

GitHub user dmekhanikov opened a pull request:

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

IGNITE-9009 Don't process backup updates for local continuous queries.



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

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

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

https://github.com/apache/ignite/pull/4403.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 #4403


commit c75df5c917646fa75b155afd0b79a0f26d809b45
Author: Denis Mekhanikov 
Date:   2018-07-23T09:21:07Z

IGNITE-9009 Don't process backup updates for local continuous queries.




---

[GitHub] ignite pull request #4165: IGNITE-8747: Remove\RemoveAll shouldn't report of...

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---

[GitHub] ignite pull request #4110: IGNITE-8681: Introduce expiry throttling.

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---

[GitHub] ignite pull request #4151: Ignite-8681: check if 8503 fix test issues.

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---

[jira] [Created] (IGNITE-9052) Add possibility to configure Ignite instance name for springData repository in IgniteRepositoryFactoryBean

[Evgenii Zhuravlev (JIRA)]

Evgenii Zhuravlev created IGNITE-9052:
-

 Summary: Add possibility to configure Ignite instance name for 
springData repository in IgniteRepositoryFactoryBean
 Key: IGNITE-9052
 URL: https://issues.apache.org/jira/browse/IGNITE-9052
 Project: Ignite
  Issue Type: Improvement
Reporter: Evgenii Zhuravlev


This configuration can be used to access 2 different clusters from 2 
repositories in one spring context



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

[GitHub] ignite pull request #4271: ignite-8892: Get rid of CacheQuery.keepAll flag.

[AMashenkov]

Github user AMashenkov closed the pull request at:

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


---

[jira] [Created] (IGNITE-9051) Remove unnecessary ssh tests

[Ivan Fedotov (JIRA)]

Ivan Fedotov created IGNITE-9051:


 Summary: Remove unnecessary ssh tests
 Key: IGNITE-9051
 URL: https://issues.apache.org/jira/browse/IGNITE-9051
 Project: Ignite
  Issue Type: Test
Reporter: Ivan Fedotov
Assignee: Ivan Fedotov


Now in IgniteProjectionStartStopRestartSelfTest there are two unnecessary tests 
[1], [2] that duplicate other tests. Its duplicate testStopNodesByIds and 
testRestartNodesByIds respectively because order of ids is not important: if we 
go deeper in ignite.cluster().stopNodes() method, we can see that in 
ClusterIgniteImpl [3] all nodes id will be collected in HashSet in forNodesIds 
method [4]. 

So testStopNodesByIdsC and testRestartNodesByIdsC should be removed.

[1][https://github.com/apache/ignite/blob/master/modules/ssh/src/test/java/org/apache/ignite/internal/IgniteProjectionStartStopRestartSelfTest.java#L701]

[2][https://github.com/apache/ignite/blob/master/modules/ssh/src/test/java/org/apache/ignite/internal/IgniteProjectionStartStopRestartSelfTest.java#L917]

[3][https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/cluster/IgniteClusterImpl.java#L250]

[4][https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/cluster/ClusterGroupAdapter.java#L454]



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

[GitHub] ignite pull request #4397: IGNITE-9042 Transaction with small timeout may le...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #4402: IGNITE-9034 Add Estimator API support to TensorFl...

[dmitrievanthony]

GitHub user dmitrievanthony opened a pull request:

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

IGNITE-9034 Add Estimator API support to TensorFlow cluster on top of 
Apache Ignite



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

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

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

https://github.com/apache/ignite/pull/4402.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 #4402


commit a0e7a08acb1bb6b535cdb14047dd0bdf3bbb6868
Author: Anton Dmitriev 
Date:   2018-07-19T16:15:14Z

IGNITE-9034 First version of TensorFlow job submitter, chief and user
script runners.

commit 387bcf44fea6eb7c1807d51e435e7f030906ed50
Author: Anton Dmitriev 
Date:   2018-07-19T16:15:46Z

Merge branch 'master' of https://github.com/apache/ignite into ignite-9034

commit 3f302197d10940d84a296b6b33aa07f670eff2e0
Author: Anton Dmitriev 
Date:   2018-07-20T16:37:17Z

IGNITE-9034 Update TensorFlow cluster manager.




---

[jira] [Created] (IGNITE-9050) WALIterator should throws exception if iterator stopped in the WALArchive but not in WALWork

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-9050:
--

 Summary: WALIterator should throws exception if iterator stopped 
in the WALArchive but not in WALWork
 Key: IGNITE-9050
 URL: https://issues.apache.org/jira/browse/IGNITE-9050
 Project: Ignite
  Issue Type: Bug
Reporter: Dmitriy Govorukhin


The iterator will stop iteration if next WAL record pointer is not equals 
expected (WalSegmentTailReachedException), if it happens during iteration over 
segments in WAL archive, this means WAL is corrupted and we cannot ignore this, 
WAL log is not fully read.



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

[GitHub] ignite pull request #2859: IGNITE-6635

[devozerov]

Github user devozerov closed the pull request at:

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


---