[jira] [Created] (IGNITE-7658) visorcmd: add ability to get configuration of certain cache

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-7658:
--

 Summary: visorcmd: add ability to get configuration of certain 
cache
 Key: IGNITE-7658
 URL: https://issues.apache.org/jira/browse/IGNITE-7658
 Project: Ignite
  Issue Type: Improvement
Reporter: Pavel Konstantinov


Currently 'config' command returns only full configuration from a node.

config -id8=@n0   

It is inconvenient in case if a user wants to get the configuration for one 
certain cache.
I suggesting to add a new option to 'config' command to set cache, like:

config -id8=@n0 -c=@c0   - get configuration of cache @c0 from node @n0



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

Re: Apache Ignite 2.4 release

[Nikolay Izhikov]

Hello, Dmitriy.

IGNITE-7337 are merged to master [1]

Do I need to do something more to include this feature into 2.4. release?

[1] 
https://github.com/apache/ignite/commit/7c01452990ad0de0fb84ab4c0424a6d71e5bccba

В Ср, 07/02/2018 в 11:26 -0800, Dmitriy Setrakyan пишет:
> Agree on both, the performance fix and the spark data frames. Let's get
> them into the release.
> 
> However, Raymond is right. We should know how long the performance fix will
> take. If it adds another month to the development, we should include it
> into the next release. I am hoping that it can be done faster though.
> 
> 
> Alexey Goncharuk, Dmitriy Pavlov, any ideas?
> 
> D.
> 
> On Wed, Feb 7, 2018 at 9:07 AM, Nikolay Izhikov  wrote:
> 
> > Hello, Igniters.
> > 
> > Please, consider including IGNITE-7337 - Spark Data Frames: support saving
> > a data frame in Ignite [1] in the 2.4 release.
> > It seems we can merge it into the master in a day or few.
> > 
> > [1] https://issues.apache.org/jira/browse/IGNITE-7337
> > 
> > 
> > В Ср, 07/02/2018 в 08:35 -0800, Denis Magda пишет:
> > > I’m voting for the blocker addition into the release. Sergey K. how will
> > 
> > it affect your testing cycles? Do you need to re-run everything from
> > scratch and how many days you need?
> > > 
> > > —
> > > Denis
> > > 
> > > > On Feb 6, 2018, at 11:29 PM, Alexey Goncharuk <
> > 
> > alexey.goncha...@gmail.com> wrote:
> > > > 
> > > > Guys,
> > > > 
> > > > Thanks to Dmitriy Pavlov we found the ticket [1] which causes a major
> > > > slowdown when page replacement starts. Even though it's not a
> > 
> > regression, I
> > > > suggest we consider it a blocker for 2.4 because this is a huge
> > 
> > performance
> > > > issue which can make it virtually impossible to use native persistence
> > 
> > when
> > > > data size is significantly larger than memory size.
> > > > 
> > > > Any objections?
> > > > 
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-7638
> > > > 
> > > > 2018-01-30 17:10 GMT+03:00 Pavel Tupitsyn :
> > > > 
> > > > > Igniters, I will handle 2.4 release if there are no objections.
> > > > > Let's take a bit more time for testing and start vote by the end of
> > 
> > this
> > > > > week.
> > > > > 
> > > > > Pavel
> > > > > 
> > > > > On Sat, Jan 27, 2018 at 3:32 AM, Denis Magda 
> > 
> > wrote:
> > > > > 
> > > > > > Hi Vyacheslav,
> > > > > > 
> > > > > > According to the previous review notes the impact of the changes
> > 
> > might be
> > > > > > significant, thus, I would recommend us to move the changes to the
> > 
> > next
> > > > > > release.
> > > > > > 
> > > > > > BTW, don’t hesitate to ping reviewers more frequently if there is a
> > > > > > pending/abandon review. We are all the people who are tend to
> > 
> > forget or
> > > > > > miss notifications ;)
> > > > > > 
> > > > > > > On Jan 26, 2018, at 2:04 AM, Vyacheslav Daradur <
> > 
> > daradu...@gmail.com>
> > > > > > 
> > > > > > wrote:
> > > > > > > 
> > > > > > > Hi, Vladimir, it's good news. I'm looking forward to new Ignite
> > > > > 
> > > > > release!
> > > > > > > 
> > > > > > > Could you please share a release schedule for 'varint'
> > 
> > optimizations?
> > > > > > > 
> > > > > > > The task [1] is waiting for review for 5 months.
> > > > > > > 
> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-5097
> > > > > > > 
> > > > > > > 
> > > > > > > On Fri, Jan 26, 2018 at 12:51 PM, Vladimir Ozerov <
> > > > > 
> > > > > voze...@gridgain.com>
> > > > > > wrote:
> > > > > > > > Hi Igniters,
> > > > > > > > 
> > > > > > > > As far as I can see all required tasks and fixes were merged. I
> > > > > 
> > > > > propose
> > > > > > to
> > > > > > > > take several days of silence to test what we've done and start
> > 
> > vote at
> > > > > > 
> > > > > > the
> > > > > > > > beginning of the next week.
> > > > > > > > 
> > > > > > > > Makes sense?
> > > > > > > > 
> > > > > > > > On Mon, Jan 22, 2018 at 8:39 PM, Denis Magda <
> > 
> > dma...@apache.org>
> > > > > 
> > > > > wrote:
> > > > > > > > 
> > > > > > > > > Ok, let’s target Wednesday as a code freeze date.
> > > > > > > > > 
> > > > > > > > > Community members who are involved in 2.4 release please
> > 
> > merge you
> > > > > > 
> > > > > > fixes
> > > > > > > > > and optimizations by that time.
> > > > > > > > > 
> > > > > > > > > —
> > > > > > > > > Denis
> > > > > > > > > 
> > > > > > > > > > On Jan 22, 2018, at 8:24 AM, Anton Vinogradov <
> > 
> > a...@apache.org>
> > > > > 
> > > > > wrote:
> > > > > > > > > > 
> > > > > > > > > > Issues
> > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-6711
> > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-6902
> > > > > > > > > > 
> > > > > > > > > > are in master and ignite-2.4
> > > > > > > > > > 
> > > > > > > > > > On Mon, Jan 22, 2018 at 6:43 PM, Denis Magda <
> > 
> > dma...@apache.org>
> > > > > > 
> > > > > > wrote:
> > > > > > > > > > 
> > > > > > > > > > 

Saving Spark Data Frames merged to master

[Nikolay Izhikov]

Hello, Igniters.

Good news.

IGNITE-7337 [1](Spark Data Frames: support saving a data frame in Ignite) are 
merged to master.

For now we can both - read from and write to Ignite SQL table with Data Frame 
API.
Big thanks to Valentin Kulichenko for a quick review.
So it seems we can include this feature to 2.4 release.

[1] https://issues.apache.org/jira/browse/IGNITE-7337

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

[GitHub] ignite pull request #3438: IGNITE-7337: Implementation of saving DataFrame t...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3496: IGNITE-7657: Minor style fixes: imports, forgotte...

[gg-shq]

GitHub user gg-shq opened a pull request:

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

IGNITE-7657: Minor style fixes: imports, forgotten javadocs, annotations

…ons.

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

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

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

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


commit a8252aa0590913fcbb812c0e0d66213e1a56a743
Author: shq 
Date:   2018-02-08T23:18:47Z

IGNITE-7657: Minor style fixes: imports, forgotten javadocs, annotations.




---

[GitHub] ignite pull request #3495: ignite-7193: IgniteReflectionFactory should prope...

[sk0x50]

GitHub user sk0x50 opened a pull request:

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

ignite-7193: IgniteReflectionFactory should properly handle primitive data 
types



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

$ git pull https://github.com/sk0x50/ignite ignite-7193

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

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


commit 79ab82d1374c307e3b858a3230e59f2a901ce38e
Author: Slava Koptilin 
Date:   2018-02-08T23:17:13Z

ignite-7193: IgniteReflectionFactory properly handles primitive types

commit 9eafdee43ed6a99e09dbe437965729beed45cf8f
Author: Slava Koptilin 
Date:   2018-02-08T23:19:12Z

ignite-7193: removed unused import




---

[jira] [Created] (IGNITE-7657) SQL COPY: minor style fixes

[Kirill Shirokov (JIRA)]

Kirill Shirokov created IGNITE-7657:
---

 Summary: SQL COPY: minor style fixes
 Key: IGNITE-7657
 URL: https://issues.apache.org/jira/browse/IGNITE-7657
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.4
Reporter: Kirill Shirokov
Assignee: Kirill Shirokov






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

[GitHub] ignite pull request #3493: Ignite 7464

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Ignite work directory usage?

[Valentin Kulichenko]

Sergey,

These mappings are supposed to be the same on all nodes, so if the file
already exists, we can safely ignore this, or use a lock to avoid
concurrent access. Actually, I think we already fixed this in the past,
it's weird that issue came up again.

But in any case, switching marshaller cache to persistence instead of using
these files makes perfect sense to me, and we definitely should do that.

-Val

On Tue, Feb 6, 2018 at 1:04 AM, Sergey Chugunov 
wrote:

> Folks,
>
> There are several things here.
>
> Firstly user asked the initial question is sitting on Apache 1.x; it is
> clear from exception stack trace he provided.
> So although the issue exists for a while it looks like it doesn't hurt
> users a lot.
>
> Secondly I examined the code managing marshaller mappings and can say that
> it the issue is still here even in the latest version; thus I filed a
> ticket [1] to address it.
>
> ​[1] https://issues.apache.org/jira/browse/IGNITE-7635
>
> Thanks,
> Sergey.
>

[jira] [Created] (IGNITE-7656) Can't query a created cache

[Mike Williams (JIRA)]

Mike Williams created IGNITE-7656:
-

 Summary: Can't query a created cache
 Key: IGNITE-7656
 URL: https://issues.apache.org/jira/browse/IGNITE-7656
 Project: Ignite
  Issue Type: Bug
Reporter: Mike Williams






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

[jira] [Created] (IGNITE-7655) Spark Data Frames: saving data frames into Ignite needs to be documented

[Nikolay Izhikov (JIRA)]

Nikolay Izhikov created IGNITE-7655:
---

 Summary: Spark Data Frames: saving data frames into Ignite needs 
to be documented
 Key: IGNITE-7655
 URL: https://issues.apache.org/jira/browse/IGNITE-7655
 Project: Ignite
  Issue Type: Bug
  Components: spark
Reporter: Nikolay Izhikov
Assignee: Nikolay Izhikov
 Fix For: 2.4


Once IGNITE-7337 is ready for merge.
This new feature of Ignite needs to be documented.



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

[jira] [Created] (IGNITE-7654) Geospatial queries does not work for JDBC/ODBC

[Mikhail Cherkasov (JIRA)]

Mikhail Cherkasov created IGNITE-7654:
-

 Summary: Geospatial queries does not work for JDBC/ODBC
 Key: IGNITE-7654
 URL: https://issues.apache.org/jira/browse/IGNITE-7654
 Project: Ignite
  Issue Type: Bug
  Components: jdbc, odbc, sql, thin client
Affects Versions: 2.3
Reporter: Mikhail Cherkasov
 Fix For: 2.5


Geospatial queries do not work for JDBC/ODBC.

I can create a table with GEOMETRY from sqlline, like this:

 
{code:java}
 CREATE TABLE GEO_TABLE(GID INTEGER PRIMARY KEY, THE_GEOM GEOMETRY);{code}
 

table creation works fine, I can add rows:

 
{code:java}
 INSERT INTO GEO_TABLE(GID, THE_GEOM) VALUES (2, 'POINT(500 505)');{code}
 

but there's no way to select GEOMETRY objects:

 

 
{code:java}
SELECT THE_GEOM FROM GEO_TABLE;{code}
 
{noformat}
Error: class org.apache.ignite.binary.BinaryObjectException: Custom objects are 
not supported (state=5,code=0)
java.sql.SQLException: class org.apache.ignite.binary.BinaryObjectException: 
Custom objects are not supported
at 
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:671)
at 
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:130)
at 
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:299)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265){noformat}
 



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

Re: Teamcity account does not work anymore

[Pavel Tupitsyn]

Dmitry, thanks a lot, works as expected now!

Pavel

On Thu, Feb 8, 2018 at 5:47 PM, Dmitry Pavlov  wrote:

> Could you please check now?
>
> чт, 8 февр. 2018 г. в 16:37, Pavel Tupitsyn :
>
> > Hi Dmitry,
> >
> > I've re-registered using ptupit...@apache.org email, can you give me
> back
> > admin permissions?
> >
> > Thanks,
> > Pavel
> >
> > On Thu, Feb 8, 2018 at 4:26 PM, Dmitry Pavlov 
> > wrote:
> >
> > > Hi Pavel,
> > >
> > > Could you please re-register using gmail or apache email?
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > чт, 8 февр. 2018 г. в 16:03, Pavel Tupitsyn <
> ptupitsyn.apa...@gmail.com
> > >:
> > >
> > > > Igniters,
> > > >
> > > > My teamcity (ci.ignite.apache.org) account "ptupitsin" seems to be
> > > removed
> > > > or disabled.
> > > > Does anyone know what's going on?
> > > >
> > > > Thanks,
> > > > Pavel
> > > >
> > >
> >
>

[GitHub] ignite pull request #2372: IGNITE-425: Implementation of ContinuousQueryWith...

[nizhikov]

Github user nizhikov closed the pull request at:

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


---

Re: Topicality of task IGNITE-6134

[Denis Magda]

Hi Yaroslav,

The task is unassigned. So, you’re free to take over it and raise the questions 
or implementation suggestions here.

—
Denis

> On Feb 8, 2018, at 4:39 AM, Yaroslav Lymar  wrote:
> 
> Hi Igniters!
> 
> I would like to engage the task (IGNITE-6134).
> Judging by the comments, this task was already taken by someone but the
> progress was unknown.
> Is this task still topicality? Сan I get it developed?

Re: Removing "fabric" from Ignite binary package name

[Denis Magda]

Anton,

What’s wrong if we just go ahead and:
- replace “fabric” with “ignite”
- replace “hadoop” with “ignite-hadoop"

—
Denis

> On Feb 8, 2018, at 1:51 AM, Anton Vinogradov  wrote:
> 
> Denis,
> 
> "hadoop" and "fabric" words work on same engine.
> 
> We have special assembly desctiptors, for example:
> dependencies-fabric.xml
> dependencies-fabric-lgpl.xml
> dependencies-hadoop.xml
> release-base.xml
> release-fabric.xml
> release-fabric-base.xml
> release-fabric-lgpl.xml
> release-hadoop.xml
> 
> So, I'ts impossible for now to remove "fabric" without "hadoop" removal.
> Only one case is to make some ditry hack, but that's not a good idea.
> 
> On Thu, Feb 8, 2018 at 11:29 AM, Sergey Kozlov  wrote:
> 
>> +1 hadoop accelerator removing for AI 2.5
>> 
>> Also probably IGFS should be either removed or refactored, e.g. create FS
>> directly over the data region without using "cache" entity as an
>> intermidiate stage
>> 
>> On Thu, Feb 8, 2018 at 2:13 AM, Denis Magda  wrote:
>> 
>>> Anton,
>>> 
>>> I don’t get how the hadoop editions are related to this task. The project
>>> is not named as “data fabric” for a while. Check up the site or docs.
>>> 
>>> The “fabric” word is being removed from all over the places and needs to
>>> be removed from the editions’ names.
>>> 
>>> As for the hadoop future, my personal position is to retire this
>> component
>>> and forget about it. I would restart the conversation again after we done
>>> with 2.4.
>>> 
>>> —
>>> Denis
>>> 
 On Feb 7, 2018, at 2:13 AM, Anton Vinogradov  wrote:
 
 Denis, Petr,
 
 I checked PR and found we have *overcomplicated* logic with "fabric"
>> and
 "hadoop" postfixs.
 
 Do we really need to assembly 2 editions?
 "Hadoop" edition still valued?
 
 My proposal is to get rid of "hadoop" edition and replace it with
 instruction of how to use "fabric" edition instead.
 Instruction will be pretty easy -> move "hadoop" folder from "optional"
>>> to
 root directory :)
 
 In that case we can just remove all postfix logic from maven poms and
 simplify release process.
 
 On Thu, Dec 28, 2017 at 9:20 PM, Denis Magda 
>> wrote:
 
> Petr, thanks for solving it!
> 
> Hope that Anton V. or some other build master will double-check the
> changes and merge them.
> 
> —
> Denis
> 
>> On Dec 28, 2017, at 8:29 AM, Petr Ivanov 
>> wrote:
>> 
>> IGNITE-7251 is done, needs review and some additional tests. See PR
> #3315 [1].
>> 
>> 
>> [1] https://github.com/apache/ignite/pull/3315 <
> https://github.com/apache/ignite/pull/3315>
>> 
>> 
>> 
>>> On 20 Dec 2017, at 23:15, Denis Magda  wrote:
>>> 
>>> Petr, thanks, such a swift turnaround!
>>> 
>>> Have you found the one who can asses and review the changes?
>>> 
>>> Maintainers label might be helpful. Just ping them directly:
>>> https://cwiki.apache.org/confluence/display/IGNITE/How+
> to+Contribute#HowtoContribute-ReviewProcessandMaintainers <
> https://cwiki.apache.org/confluence/display/IGNITE/How+
> to+Contribute#HowtoContribute-ReviewProcessandMaintainers>
>>> 
>>> 
>>> —
>>> Denis
>>> 
 On Dec 20, 2017, at 12:24 AM, Petr Ivanov 
>>> wrote:
 
 Assigned myself — done the same work while preparing RPM package.
 But for fixing DEVNOTES.txt waiting for review and merge of
> IGNITE-7107 [1].
 
 
 [1] https://issues.apache.org/jira/browse/IGNITE-7107
 
 
 
> On 19 Dec 2017, at 22:55, Denis Magda  wrote:
> 
> All the bids were accepted and the verdict is executed:
> https://issues.apache.org/jira/browse/IGNITE-7251 <
> https://issues.apache.org/jira/browse/IGNITE-7251>
> 
> Who is ready to pick this up?
> 
> —
> Denis
> 
>> On Dec 19, 2017, at 5:35 AM, Anton Vinogradov <
> avinogra...@gridgain.com> wrote:
>> 
>> +1б фо шур
>> 
>> On Tue, Dec 19, 2017 at 9:59 AM, Vladimir Ozerov <
> voze...@gridgain.com>
>> wrote:
>> 
>>> +1б вуаштшеудн
>>> 
>>> On Tue, Dec 19, 2017 at 2:34 AM, Valentin Kulichenko <
>>> valentin.kuliche...@gmail.com> wrote:
>>> 
 +1
 
 On Mon, Dec 18, 2017 at 12:24 PM, Dmitriy Setrakyan <
>>> dsetrak...@apache.org
> 
 wrote:
 
> +1 (completely agree)
> 
> On Mon, Dec 18, 2017 at 10:21 AM, Denis Magda <
>>> dma...@apache.org>
>>> wrote:
> 
>> Igniters,
>> 
>> Apache 

[GitHub] ignite pull request #3469: IGNITE-7606: delayed page write during page repla...

[asfgit]

Github user asfgit closed the pull request at:

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


---

[GitHub] ignite pull request #3494: IGNITE-7438 LSQR solver for Linear Regression

[dmitrievanthony]

GitHub user dmitrievanthony opened a pull request:

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

IGNITE-7438 LSQR solver for Linear Regression



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

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

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

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


commit 1fd21f05fa7f288e42d19126f4d4ea9a3a7f902f
Author: dmitrievanthony 
Date:   2018-01-16T15:55:04Z

IGNITE-7437 Initial version of d-learn framework in ML module.

commit 104b3bb9badcea4d0d907cca39624cc84ef9544d
Author: dmitrievanthony 
Date:   2018-01-16T20:05:04Z

IGNITE-7437 Introduce DLearnContextTransformers into ML module.

commit 006b749e4742698f837582b3224a93468c88511e
Author: dmitrievanthony 
Date:   2018-01-16T20:18:39Z

IGNITE-7437 Introduce DLearnContextTransformers into ML module (fix 
compilation issues).

commit d8696b6210dccaa92f4de459a9590f9e0896c7db
Author: dmitrievanthony 
Date:   2018-01-17T08:26:52Z

IGNITE-7437 Move dataset API into d-learn context wrapper to avoid 
introducing an additional util classes.

commit c03e58ef67debc2a2e42bfd9f829bfe5c5a60a45
Author: dmitrievanthony 
Date:   2018-01-17T10:30:16Z

IGNITE-7437 Add ability to close learning context.

commit 8cdc9c516f8a248f177e4a5fe9a49b027aba96e3
Author: dmitrievanthony 
Date:   2018-01-17T11:28:43Z

IGNITE-7437 Reformat code and javadoc.

commit 146c0785b2c125baf3216c6dd2ad8c38fec9f5a8
Author: dmitrievanthony 
Date:   2018-01-17T15:20:04Z

IGNITE-7437 Add affinity tests for d-learn context factory.

commit be830a8e133facb69fd1a6166b3ca4ec6a7de25b
Author: dmitrievanthony 
Date:   2018-01-17T15:22:15Z

Merge branch 'master' into ignite-7437

commit 6c4f191081019c91a4b78f40bdf6f52a9f46eb47
Author: dmitrievanthony 
Date:   2018-01-17T16:07:08Z

IGNITE-7437 Add dataset loading examples (cache and local) for d-learn.

commit 21b648b182305c34a061e55d7d2b287165c362eb
Author: dmitrievanthony 
Date:   2018-01-17T16:40:12Z

IGNITE-7437 Add dataset transformation example for d-learn.

commit 87194ba42c7dd3250e0dac30dd11bb1a1283022c
Author: dmitrievanthony 
Date:   2018-01-19T16:21:59Z

IGNITE-7437 Use affinityCall/affinityRun in cache d-learn context
implementation to guarantee partitions reservation during computation.

commit a553f12f3fb0c3b64470d2e3002a5eb49013614c
Author: dmitrievanthony 
Date:   2018-01-19T16:32:10Z

IGNITE-7437 Reformat code.

commit 03a6bfe1b47a259e1cf400762dca427ab4ecf928
Author: dmitrievanthony 
Date:   2018-01-19T17:32:49Z

IGNITE-7437 Update Javadoc.

commit e9c63f9f7f5f55dc60d9ac0b9bddb4f8ad9f6a67
Author: dmitrievanthony 
Date:   2018-01-22T08:51:37Z

IGNITE-7437 Update Javadoc.

commit 7ebd20a6ef1eca6063013a5f8a8361ae4f76a609
Author: dmitrievanthony 
Date:   2018-01-23T22:23:24Z

IGNITE-7437 Introduce IDD (Ignite Distributed Dataset) as a prototype.

commit 3c11f600b920fe19f57ca4203be5ac44219c4f52
Author: dmitrievanthony 
Date:   2018-01-24T16:50:12Z

IGNITE-7437 Introduce DLC (Distributed Learning Context).

commit 8381bd827cae78478532bf0e55446ff38b1d9e3a
Author: dmitrievanthony 
Date:   2018-01-25T10:35:26Z

IGNITE-7437 Update DLC and add examples.

commit c21e43406a1a1d398277bc40a818d87752afb11a
Author: dmitrievanthony 
Date:   2018-01-25T17:03:53Z

IGNITE-7437 Update DLC and add examples.

commit 9d72b1cb7b8129fe3290fe6ab2bd8433f90f9aae
Author: dmitrievanthony 
Date:   2018-01-26T17:14:39Z

IGNITE-7437 Update DLC and add examples.

commit f83153e16b1dba9eed6c6e26b717726f8b416c96
Author: dmitrievanthony 
Date:   2018-01-27T15:15:06Z

IGNITE-7437 Updated javadoc and tests, removed d-learn part.

commit c39b3ebf2d0793a1044c75663fa9cbbcb0777ae7
Author: dmitrievanthony 
Date:   2018-01-27T15:17:34Z

IGNITE-7437 Remove d-learn part from examples.

commit a00ff930217c5d99901dc7491d5148b89f9c8788
Author: dmitrievanthony 
Date:   2018-01-29T11:09:39Z

IGNITE-7437 Update examples for partition based dataset.

commit 616c18e52b4bcd44b47f13c1eab37bcf16df3259
Author: dmitrievanthony 
Date:   2018-01-29T11:20:37Z

IGNITE-7437 Add package-info.java files.

commit ef092a6c1893199cb5542eabdd20d05b30327a6a
Author: dmitrievanthony 
Date:   2018-01-29T11:22:24Z

[GitHub] ignite pull request #3493: Ignite 9486

[slukyano]

GitHub user slukyano opened a pull request:

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

Ignite 9486



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

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

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

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


commit 610cd3604b302aea424fbe41681599fbe25868de
Author: Stanislav Lukyanov 
Date:   2018-02-08T15:02:59Z

IGNITE-7464: Add property to configure time between node connection attempts

commit 8cadb5f13ef3ddd6c4a3e6634fb41b66ec7bb1c5
Author: Stanislav Lukyanov 
Date:   2018-02-08T15:10:09Z

IGNITE-7464: Add TcpDiscoverySpiReconnectDelayTest to a test suite.




---

Re: Teamcity account does not work anymore

[Dmitry Pavlov]

Could you please check now?

чт, 8 февр. 2018 г. в 16:37, Pavel Tupitsyn :

> Hi Dmitry,
>
> I've re-registered using ptupit...@apache.org email, can you give me back
> admin permissions?
>
> Thanks,
> Pavel
>
> On Thu, Feb 8, 2018 at 4:26 PM, Dmitry Pavlov 
> wrote:
>
> > Hi Pavel,
> >
> > Could you please re-register using gmail or apache email?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 8 февр. 2018 г. в 16:03, Pavel Tupitsyn  >:
> >
> > > Igniters,
> > >
> > > My teamcity (ci.ignite.apache.org) account "ptupitsin" seems to be
> > removed
> > > or disabled.
> > > Does anyone know what's going on?
> > >
> > > Thanks,
> > > Pavel
> > >
> >
>

[GitHub] ignite pull request #3492: IGNITE-7398 Disabled MBean registration for cache...

[pvinokurov]

GitHub user pvinokurov opened a pull request:

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

IGNITE-7398 Disabled MBean registration for cache group if IGNITE_MBE…



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

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

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

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


commit a39f2f899842ca03e2f9ab90c336f8fa246b8843
Author: pvinokurov 
Date:   2018-02-08T14:22:43Z

IGNITE-7398 Disabled MBean registration for cache group if 
IGNITE_MBEANS_DISABLED set to true




---

Re: IgniteSet implementation: changes required

[Pavel Pereslegin]

Hello, Igniters!

We have some issues with current IgniteSet implementation ([1], [2], [3], [4]).

As was already described in this conversation, the main problem is
that current IgniteSet implementation maintains plain Java sets on
every node (see CacheDataStructuresManager.setDataMap). These sets
duplicate backing-cache entries, both primary and backup. size() and
iterator() calls issue distributed queries to collect/filter data from
all setDataMap's.

I believe we can solve specified issues if each instance of IgniteSet
will have separate internal cache that will be destroyed on close.

What do you think about such major change? Do you have any thoughts or
objections?

[1] https://issues.apache.org/jira/browse/IGNITE-7565
[2] https://issues.apache.org/jira/browse/IGNITE-5370
[3] https://issues.apache.org/jira/browse/IGNITE-5553
[4] https://issues.apache.org/jira/browse/IGNITE-6474


2017-10-31 5:53 GMT+03:00 Dmitriy Setrakyan :
> Hi Andrey,
>
> Thanks for a detailed email. I think your suggestions do make sense. Ignite
> cannot afford to have a distributed set that is not fail-safe. Can you
> please focus only on solutions that provide consistent behavior in case of
> topology changes and failures and document them in the ticket?
>
> https://issues.apache.org/jira/browse/IGNITE-5553
>
> D.
>
> On Mon, Oct 30, 2017 at 3:07 AM, Andrey Kuznetsov  wrote:
>
>> Hi, Igniters!
>>
>> Current implementation of IgniteSet is fragile with respect to cluster
>> recovery from a checkpoint. We have an issue (IGNITE-5553) that addresses
>> set's size() behavior, but the problem is slightly broader. The text below
>> is my comment from Jira issue. I encourage you to discuss it.
>>
>> We can put current set size into set header cache entry. This will fix
>> size(), but we have broken iterator() implementation as well.
>>
>> Currently, set implementation maintains plain Java sets on every node, see
>> CacheDataStructuresManager.setDataMap. These sets duplicate backing-cache
>> entries, both primary and backup. size() and iterator() calls issue
>> distributed queries to collect/filter data from all setDataMap's. And
>> setDataMaps remain empty after cluster is recovered from checkpoint.
>>
>> Now I see the following options to fix the issue.
>>
>> #1 - Naive. Iterate over all datastructure-backing caches entries during
>> recover from checkpoint procedure, filter set-related entries and refill
>> setDataMap's.
>> Pros: easy to implement
>> Cons: inpredictable time/memory overhead.
>>
>> #2 - More realistic. Avoid node-local copies of cache data. Maintain linked
>> list in datastructure-backing cache: key is set item, value is next set
>> item. List head is stored in set header cache entry (this set item is
>> youngest one). Iterators build on top of this structure are fail-fast.
>> Pros: less memory overhead, no need to maintain node-local mirrors of cache
>> data
>> Cons: iterators are not fail-safe.
>>
>> #3 - Option #2 modified. We can store reference counter and 'removed' flag
>> along with next item reference. This allows to make iterators fail safe.
>> Pros: iterators are fail-safe
>> Cons: slightly more complicated implementation, may affect performance,
>> also I see no way to handle active iterators on remote nodes failures.
>>
>>
>> Best regards,
>>
>> Andrey.
>>

[jira] [Created] (IGNITE-7653) Issue with saved license causes snapshot test fails

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-7653:
-

 Summary: Issue with saved license causes snapshot test fails
 Key: IGNITE-7653
 URL: https://issues.apache.org/jira/browse/IGNITE-7653
 Project: Ignite
  Issue Type: Bug
Reporter: Eduard Shangareev
Assignee: Peter Ivanov


Example of fails
https://ggtc.gridgain.com/viewLog.html?buildId=1082616=buildResultsDiv=id8xIgniteGridGainTestsJava8_DbXSnapshotsSecurity#testNameId-6967724399324938567

{code}
org.apache.ignite.IgniteCheckedException: Snapshot feature is not allowed by 
the licence.
{code}

It happens time to time. We rely on default license in tests where Ultimate 
features are enabled.
But on some agents license file is presented which would be read by nodes and 
because of it ultimate features would be disabled.

Another observation is that it happens only with windows-agents.



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

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

[pvinokurov]

GitHub user pvinokurov opened a pull request:

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

IGNITE-7263 Ignore client configuration for daemon node



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

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

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

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


commit 4a1b6b874cc1b39ce3f10ada4c824dfc82c999c6
Author: pvinokurov 
Date:   2018-02-08T13:34:52Z

IGNITE-7263 Ignore client configuration for daemon node




---

Re: Teamcity account does not work anymore

[Pavel Tupitsyn]

Hi Dmitry,

I've re-registered using ptupit...@apache.org email, can you give me back
admin permissions?

Thanks,
Pavel

On Thu, Feb 8, 2018 at 4:26 PM, Dmitry Pavlov  wrote:

> Hi Pavel,
>
> Could you please re-register using gmail or apache email?
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 8 февр. 2018 г. в 16:03, Pavel Tupitsyn :
>
> > Igniters,
> >
> > My teamcity (ci.ignite.apache.org) account "ptupitsin" seems to be
> removed
> > or disabled.
> > Does anyone know what's going on?
> >
> > Thanks,
> > Pavel
> >
>

[GitHub] ignite pull request #3486: Ignite 7263

[pvinokurov]

Github user pvinokurov closed the pull request at:

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


---

[GitHub] ignite pull request #3490: IGNITE-7540 Sequential checkpoints cause overwrit...

[Jokser]

GitHub user Jokser opened a pull request:

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

IGNITE-7540 Sequential checkpoints cause overwrite of already cleaned & 
freed offheap page



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

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

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

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


commit 17bdf9459a3234eefbd379506a1d0895cd88d3a5
Author: Pavel Kovalenko 
Date:   2018-02-08T13:32:40Z

IGNITE-7540 Prevent page memory metadata corruption during checkpoint and 
group destroying.




---

Re: Teamcity account does not work anymore

[Dmitry Pavlov]

Hi Pavel,

Could you please re-register using gmail or apache email?

Sincerely,
Dmitriy Pavlov

чт, 8 февр. 2018 г. в 16:03, Pavel Tupitsyn :

> Igniters,
>
> My teamcity (ci.ignite.apache.org) account "ptupitsin" seems to be removed
> or disabled.
> Does anyone know what's going on?
>
> Thanks,
> Pavel
>

Re: Continuous Query With Transformer are ready for merge

[Nikolay Izhikov]

Anton,

The merge is done!

Thank you, very much.
Your help can't be overestimated.

В Чт, 08/02/2018 в 12:38 +0300, Anton Vinogradov пишет:
> Looks like no one have objections.
> 
> Nikolay,
> Let's merge.
> 
> On Tue, Feb 6, 2018 at 8:45 PM, Nikolay Izhikov  wrote:
> 
> > Hello, Igniters.
> > 
> > Improvement of Continuous Query public API are ready for merge.
> > AFAIK Anton Vinogradov and Yakov Zhdanov are happy with proposed API. [1]
> > 
> > With this improvement we can transform entry on the server node before
> > sending it to the listener to reduce network utilization.
> > 
> > Example of usage:
> > 
> > ```
> > ContinuousQueryWithTransformer cqwt = new
> > ContinuousQueryWithTransformer<>();
> > 
> > cqwt.setRemoteTransformerFactory(FactoryBuilder.factoryOf(new
> > IdTransformer()));
> > 
> > CQWTListener lsnr = new CQWTListener();
> > 
> > cqwt.setLocalListener(lsnr);
> > 
> > cache.query(cqwt);
> > 
> > public static class IdTransformer implements IgniteClosure extends Long, ? extends Value>, Long> {
> >@Override public Long apply(CacheEntryEvent > Value> event) {
> >return event.getValue().id;
> >}
> > }
> > 
> > public static class CQWTListener implements EventListener {
> >@Override public void onUpdated(Iterable ids) {
> >for (Long id : ids)
> >   consume(id);
> >}
> > }
> > 
> > ```
> > 
> > Implementation checked on TC, benchmarks [2][3] passed as well and we’re
> > ready to merge changes to the master branch.
> > 
> > Any objections?
> > 
> > [1] https://github.com/apache/ignite/pull/2372
> > [2] https://github.com/nizhikov/ignite-425-benchmark
> > [3] https://issues.apache.org/jira/browse/IGNITE-425?
> > focusedCommentId=16353812=com.atlassian.jira.
> > plugin.system.issuetabpanels:comment-tabpanel#comment-16353812

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

Teamcity account does not work anymore

[Pavel Tupitsyn]

Igniters,

My teamcity (ci.ignite.apache.org) account "ptupitsin" seems to be removed
or disabled.
Does anyone know what's going on?

Thanks,
Pavel

[GitHub] ignite pull request #3489: Deprecated WALMode.DEFAULT.

[ilantukh]

GitHub user ilantukh opened a pull request:

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

Deprecated WALMode.DEFAULT.



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

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

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

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


commit 4925ffc10ce8e8287980eaec38b587512568a302
Author: Alexey Goncharuk 
Date:   2018-01-17T12:26:03Z

IGNITE-7453 Use GridUnsafe.cleanDirectBuffer in PageSnapshot

commit bcd68a058683b2f17b7ac60471b6e7aab3e4f6de
Author: Pavel Tupitsyn 
Date:   2018-01-17T12:38:20Z

IGNITE-7301 .NET: Baseline topology

This closes #3352

commit 66b96316a7775ce8a6e2ff4475185d5929e4998b
Author: devozerov 
Date:   2018-01-17T12:54:17Z

Merge branch 'master' into ignite-2.4

commit 268481c1cf7fe57df24be130eb67c3e3a13afe01
Author: Alexey Goncharuk 
Date:   2018-01-17T13:50:34Z

IGNITE-7453 Use GridUnsafe.cleanDirectBuffer in WalStat

commit db0cd105719c8ae713b13b34d9dca0a8cd45d377
Author: Pavel Tupitsyn 
Date:   2018-01-17T14:05:25Z

IGNITE-6776 .NET: Thin client: Add SQL & LINQ example

This closes #3390

commit c214db879101aa5660e2a50b11cd20964c0bc114
Author: Andrey Gura 
Date:   2018-01-17T12:42:41Z

ignite-7450 FileWriteAheadLogManager always uses RandomAccessFileIOFactory 
now

commit 75c27d5e49d7458e46eb46e6f87a445c3f1320ea
Author: Alexey Kuznetsov 
Date:   2018-01-18T02:25:19Z

IGNITE-7274 Web Console: Support multiple statements on Queries screen.
(cherry picked from commit 1926783)

commit 36cc822935387b2150e690c29bc6992dca0563f7
Author: Dmitriy Shabalin 
Date:   2018-01-18T04:49:08Z

IGNITE-7306 Web Console: Fixed export data from tables.
(cherry picked from commit 1bb60ec)

commit d753298b4012894b56f5c9218325211cd84a21d5
Author: Peter Ivanov 
Date:   2018-01-18T06:18:53Z

IGNITE-7107 Apache Ignite RPM packages

* added changelog to package specification

This closes #3396

commit 63445893f1bc75dc9777184499f7eabc1d4e51b1
Author: Denis Mekhanikov 
Date:   2018-01-18T08:36:18Z

IGNITE-3935 Use PeerDeployAware for streamer transformer - Fixes #3378.

Signed-off-by: Alexey Goncharuk 

commit f3f9f2a24b23027cf0c835140322e41a788932ae
Author: Pavel Tupitsyn 
Date:   2018-01-18T09:05:12Z

IGNITE-7413 Fix SqlDmlExample

This closes #3389

commit 1daa7c41bf1460a4d9a2b0c26a7a317f2fca3fb7
Author: Alexey Kuznetsov 
Date:   2018-01-18T10:14:53Z

IGNITE-7461 UI tools: Actualized data storage configuration.
(cherry picked from commit 577e632)

commit cf0080210d24d9dd8b057f959446fac5f8a4ca01
Author: dpavlov 
Date:   2018-01-18T10:53:29Z

IGNITE-7380 Implemented pluggable Direct IO - Fixes #3226.

Signed-off-by: Alexey Goncharuk 

commit dd06d0bd7ef266bfbe156e858b312d1ac86e8982
Author: Pavel Tupitsyn 
Date:   2018-01-18T12:55:49Z

IGNITE-7465 .NET: Fix SqlDdlExample failure with standalone node

commit 57479ec564e1761716da3d5f9feb7a64c396a9f9
Author: Pavel Tupitsyn 
Date:   2018-01-18T13:45:54Z

.NET: Fix CacheLocalTest.TestTxDeadlockDetection

commit bd6be8a4653322905a3b63850c7e033ce3801ce5
Author: Pavel Tupitsyn 
Date:   2018-01-18T18:25:05Z

.NET: Thin client: Fix OP_BINARY_TYPE_GET schema passing format

commit 97564d160586d6d57d300937e6b8877994e35fc7
Author: rkondakov 
Date:   2018-01-19T08:24:51Z

IGNITE-6456: Ability to separately enable or disable JDBC, ODBC and thin 
client endpoints. This closes #3309.

commit d50274ca8875c9680c12e8786ac355a787ba95e0
Author: Yakov Zhdanov 
Date:   2018-01-18T17:57:17Z

Javadoc enhancements - added @see

commit cb2d3cf22388ab19fb2d34ae5bdfc8f1b608db75
Author: Dmitriy Govorukhin 
Date:   2018-01-18T14:14:26Z

IGNITE-7471 Use soft reference for checkpoint entry contents to avoid 
excessive memory usage

commit 3965923369870bb4e8e57e3332c1a1eb1e5f5ed3
Author: rkondakov 
Date:   2018-01-19T09:00:55Z

IGNITE-6772: SQL exception messages became more informative. This closes 
#3342.

commit ba68cb0fa87f776fcd0499d030c333f182611f41
Author: devozerov 
Date:   2018-01-19T09:03:52Z

Merge remote-tracking branch 'origin/ignite-2.4' into ignite-2.4

commit b54c0c8786bd74aa0abb208f537c29f0c4be4b1e
Author: tledkov-gridgain 
Date:   2018-01-19T09:09:34Z

IGNITE-7248: JDBC: fixed schema resolution for streaming 

[jira] [Created] (IGNITE-7652) ContinuousQueryWithTransformer needs to be documented

[Nikolay Izhikov (JIRA)]

Nikolay Izhikov created IGNITE-7652:
---

 Summary: ContinuousQueryWithTransformer needs to be documented
 Key: IGNITE-7652
 URL: https://issues.apache.org/jira/browse/IGNITE-7652
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.5
Reporter: Nikolay Izhikov
Assignee: Nikolay Izhikov
 Fix For: 2.5


As long as IGNITE-425 merged to master ContinuousQueryWithTransformer API needs 
to be documented. Example has to be provided as well.



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

Topicality of task IGNITE-6134

[Yaroslav Lymar]

 Hi Igniters!

I would like to engage the task (IGNITE-6134).
Judging by the comments, this task was already taken by someone but the
progress was unknown.
Is this task still topicality? Сan I get it developed?

[GitHub] ignite pull request #3233: IGNITE-6625 JDBC thin: support SSL connection to ...

[asfgit]

Github user asfgit closed the pull request at:

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


---

Re: Unit testing of persistence & durable memory

[Dmitry Pavlov]

Hi Dmitriy,

This suite is needed for isolated methods tests and classes tests. Because
Ignite became not only in-memory solution, persistence enabled integration
tests were introduced also. These disk-enabled tests and/or tests with a
number of node startup-shutdown may require sufficient time and I/O
resouarces to complete.

In the same time there is a lot of situations needs to be covered by
product, but these situations may be not easy to reproduce in integration
testing. For such case 'PDS Unit tests suite' and first tests were created.

I hope this approach will become popular, especially for checking corner
cases.

Sincerely,
Dmitriy Pavlov

чт, 8 февр. 2018 г. в 3:58, Dmitriy Setrakyan :

> Thanks Dmitriy! Is it possible to start Ignite instance in the tests if
> needed or is it only needed for basic isolated method tests?
>
> D.
>
> On Wed, Feb 7, 2018 at 6:24 AM, Dmitry Pavlov 
> wrote:
>
> > Hi Igniters,
> >
> > Recently new unit tests suite was added to TC run chain, it is PDS unit
> > test suite. See
> >
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_
> > IgnitePdsUnitTests
> > and corresponding suite in code
> > org.apache.ignite.testsuites.IgnitePdsUnitTestSuite
> >
> > This suite contain JUnit4 styled unit tests. Such tests never start
> Ignite
> > instance, but checks only one aspect/unit behaviour of PDS/Durable
> > memory/etc.
> >
> > If it is required. tests may use Mockito to stub unnecessary Ignite
> context
> > elements and provide required behaviour. There are no real cluster
> building
> > and/or real HDD disk usage, and such tests are quite fast (each <5s to
> run)
> > and each test is quite small.
> >
> > Suite code was recently merged to master with throttling changes. Now it
> > contains only 9 tests, but I am sure it will became full of tests. Please
> > feel free to add yours.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
>

EvictableEntry.isCached() state meaning

[Andrey Kuznetsov]

Hi Igniters!

I can't comprehend the meaning of the following note in javadoc for
EvictableEntry.isCached() method.

"If entry is not in cache (e.g. has been removed) {@code false} is
returned. In this case all operations on this entry will cause creation of
a new entry in cache."

That is, if I call getKey() or getValue() on removed entry it will be
resurrected in cache? This sounds too magically. Could someone explain the
real message of the phrase, please?

--
Best regards,
  Andrey Kuznetsov.

[jira] [Created] (IGNITE-7651) Assertion error on cache start

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-7651:
-

 Summary: Assertion error on cache start
 Key: IGNITE-7651
 URL: https://issues.apache.org/jira/browse/IGNITE-7651
 Project: Ignite
  Issue Type: Bug
Reporter: Eduard Shangareev


{code:java}
java.lang.AssertionError: calculatedOffset=16384, allocated=8192, 
headerSize=4096
at 
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore.read(FilePageStore.java:341)
at 
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:322)
at 
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:306)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:658)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:578)
at 
org.apache.ignite.internal.processors.cache.persistence.DataStructure.acquirePage(DataStructure.java:130)
at 
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.init(PagesList.java:167)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.reuse.ReuseListImpl.(ReuseListImpl.java:56)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.initDataStructures(GridCacheOffheapManager.java:103)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.start(IgniteCacheOffheapManagerImpl.java:131)
at 
org.apache.ignite.internal.processors.cache.CacheGroupContext.start(CacheGroupContext.java:893)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCacheGroup(GridCacheProcessor.java:1979)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1869)
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCachesOnLocalJoin(GridCacheProcessor.java:1759)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:769)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:651)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{code}



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

[jira] [Created] (IGNITE-7650) Web Console: Rework signin page.

[Alexander Kalinin (JIRA)]

Alexander Kalinin created IGNITE-7650:
-

 Summary: Web Console: Rework signin page.
 Key: IGNITE-7650
 URL: https://issues.apache.org/jira/browse/IGNITE-7650
 Project: Ignite
  Issue Type: Improvement
  Components: wizards
Reporter: Alexander Kalinin
Assignee: Alexander Kalinin


* Add landing screen on signin page
 * Refactor signin controller to component.



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

Re: Removing "fabric" from Ignite binary package name

[Anton Vinogradov]

Denis,

"hadoop" and "fabric" words work on same engine.

We have special assembly desctiptors, for example:
dependencies-fabric.xml
dependencies-fabric-lgpl.xml
dependencies-hadoop.xml
release-base.xml
release-fabric.xml
release-fabric-base.xml
release-fabric-lgpl.xml
release-hadoop.xml

So, I'ts impossible for now to remove "fabric" without "hadoop" removal.
Only one case is to make some ditry hack, but that's not a good idea.

On Thu, Feb 8, 2018 at 11:29 AM, Sergey Kozlov  wrote:

> +1 hadoop accelerator removing for AI 2.5
>
> Also probably IGFS should be either removed or refactored, e.g. create FS
> directly over the data region without using "cache" entity as an
> intermidiate stage
>
> On Thu, Feb 8, 2018 at 2:13 AM, Denis Magda  wrote:
>
> > Anton,
> >
> > I don’t get how the hadoop editions are related to this task. The project
> > is not named as “data fabric” for a while. Check up the site or docs.
> >
> > The “fabric” word is being removed from all over the places and needs to
> > be removed from the editions’ names.
> >
> > As for the hadoop future, my personal position is to retire this
> component
> > and forget about it. I would restart the conversation again after we done
> > with 2.4.
> >
> > —
> > Denis
> >
> > > On Feb 7, 2018, at 2:13 AM, Anton Vinogradov  wrote:
> > >
> > > Denis, Petr,
> > >
> > > I checked PR and found we have *overcomplicated* logic with "fabric"
> and
> > > "hadoop" postfixs.
> > >
> > > Do we really need to assembly 2 editions?
> > > "Hadoop" edition still valued?
> > >
> > > My proposal is to get rid of "hadoop" edition and replace it with
> > > instruction of how to use "fabric" edition instead.
> > > Instruction will be pretty easy -> move "hadoop" folder from "optional"
> > to
> > > root directory :)
> > >
> > > In that case we can just remove all postfix logic from maven poms and
> > > simplify release process.
> > >
> > > On Thu, Dec 28, 2017 at 9:20 PM, Denis Magda 
> wrote:
> > >
> > >> Petr, thanks for solving it!
> > >>
> > >> Hope that Anton V. or some other build master will double-check the
> > >> changes and merge them.
> > >>
> > >> —
> > >> Denis
> > >>
> > >>> On Dec 28, 2017, at 8:29 AM, Petr Ivanov 
> wrote:
> > >>>
> > >>> IGNITE-7251 is done, needs review and some additional tests. See PR
> > >> #3315 [1].
> > >>>
> > >>>
> > >>> [1] https://github.com/apache/ignite/pull/3315 <
> > >> https://github.com/apache/ignite/pull/3315>
> > >>>
> > >>>
> > >>>
> >  On 20 Dec 2017, at 23:15, Denis Magda  wrote:
> > 
> >  Petr, thanks, such a swift turnaround!
> > 
> >  Have you found the one who can asses and review the changes?
> > 
> >  Maintainers label might be helpful. Just ping them directly:
> >  https://cwiki.apache.org/confluence/display/IGNITE/How+
> > >> to+Contribute#HowtoContribute-ReviewProcessandMaintainers <
> > >> https://cwiki.apache.org/confluence/display/IGNITE/How+
> > >> to+Contribute#HowtoContribute-ReviewProcessandMaintainers>
> > 
> > 
> >  —
> >  Denis
> > 
> > > On Dec 20, 2017, at 12:24 AM, Petr Ivanov 
> > wrote:
> > >
> > > Assigned myself — done the same work while preparing RPM package.
> > > But for fixing DEVNOTES.txt waiting for review and merge of
> > >> IGNITE-7107 [1].
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-7107
> > >
> > >
> > >
> > >> On 19 Dec 2017, at 22:55, Denis Magda  wrote:
> > >>
> > >> All the bids were accepted and the verdict is executed:
> > >> https://issues.apache.org/jira/browse/IGNITE-7251 <
> > >> https://issues.apache.org/jira/browse/IGNITE-7251>
> > >>
> > >> Who is ready to pick this up?
> > >>
> > >> —
> > >> Denis
> > >>
> > >>> On Dec 19, 2017, at 5:35 AM, Anton Vinogradov <
> > >> avinogra...@gridgain.com> wrote:
> > >>>
> > >>> +1б фо шур
> > >>>
> > >>> On Tue, Dec 19, 2017 at 9:59 AM, Vladimir Ozerov <
> > >> voze...@gridgain.com>
> > >>> wrote:
> > >>>
> >  +1б вуаштшеудн
> > 
> >  On Tue, Dec 19, 2017 at 2:34 AM, Valentin Kulichenko <
> >  valentin.kuliche...@gmail.com> wrote:
> > 
> > > +1
> > >
> > > On Mon, Dec 18, 2017 at 12:24 PM, Dmitriy Setrakyan <
> >  dsetrak...@apache.org
> > >>
> > > wrote:
> > >
> > >> +1 (completely agree)
> > >>
> > >> On Mon, Dec 18, 2017 at 10:21 AM, Denis Magda <
> > dma...@apache.org>
> >  wrote:
> > >>
> > >>> Igniters,
> > >>>
> > >>> Apache Ignite binary releases still include “fabric” word in
> > >> their
> > > names:
> > >>> https://ignite.apache.org/download.cgi#binaries <
> > >>> 

Re: Continuous Query With Transformer are ready for merge

[Anton Vinogradov]

Looks like no one have objections.

Nikolay,
Let's merge.

On Tue, Feb 6, 2018 at 8:45 PM, Nikolay Izhikov  wrote:

> Hello, Igniters.
>
> Improvement of Continuous Query public API are ready for merge.
> AFAIK Anton Vinogradov and Yakov Zhdanov are happy with proposed API. [1]
>
> With this improvement we can transform entry on the server node before
> sending it to the listener to reduce network utilization.
>
> Example of usage:
>
> ```
> ContinuousQueryWithTransformer cqwt = new
> ContinuousQueryWithTransformer<>();
>
> cqwt.setRemoteTransformerFactory(FactoryBuilder.factoryOf(new
> IdTransformer()));
>
> CQWTListener lsnr = new CQWTListener();
>
> cqwt.setLocalListener(lsnr);
>
> cache.query(cqwt);
>
> public static class IdTransformer implements IgniteClosure, Long> {
>@Override public Long apply(CacheEntryEvent Value> event) {
>return event.getValue().id;
>}
> }
>
> public static class CQWTListener implements EventListener {
>@Override public void onUpdated(Iterable ids) {
>for (Long id : ids)
>   consume(id);
>}
> }
>
> ```
>
> Implementation checked on TC, benchmarks [2][3] passed as well and we’re
> ready to merge changes to the master branch.
>
> Any objections?
>
> [1] https://github.com/apache/ignite/pull/2372
> [2] https://github.com/nizhikov/ignite-425-benchmark
> [3] https://issues.apache.org/jira/browse/IGNITE-425?
> focusedCommentId=16353812=com.atlassian.jira.
> plugin.system.issuetabpanels:comment-tabpanel#comment-16353812

[jira] [Created] (IGNITE-7649) transformer instance is not properly transfers into SqlQuery request.

[Stanilovsky Evgeny (JIRA)]

Stanilovsky Evgeny created IGNITE-7649:
--

 Summary: transformer instance is not properly transfers into 
SqlQuery request.
 Key: IGNITE-7649
 URL: https://issues.apache.org/jira/browse/IGNITE-7649
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.3
Reporter: Stanilovsky Evgeny
Assignee: Stanilovsky Evgeny
 Fix For: 2.5


to reproduce this case we need some simple changes in existing test: 
GridCacheQueryTransformerSelfTest#testKeepBinary

change:
{code:java}
List res = binaryCache.query(new ScanQuery(), 
transformer).getAll();{code}
into:
{code:java}
List res = binaryCache.query(new ScanQuery().setPageSize(2), transformer).getAll();{code}



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

[jira] [Created] (IGNITE-7648) Revert IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.

[Alexei Scherbakov (JIRA)]

Alexei Scherbakov created IGNITE-7648:
-

 Summary: Revert IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.
 Key: IGNITE-7648
 URL: https://issues.apache.org/jira/browse/IGNITE-7648
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.3
Reporter: Alexei Scherbakov
Assignee: Alexei Scherbakov
 Fix For: 2.5


IGNITE_ENABLE_FORCIBLE_NODE_KILL system property was introduced in IGNITE-5718 
as a way to prevent unnecessary node drops in case of short network problems.

I suppose it's wrong decision to fix it in such way.

We had faced some issues in our production due to lack of automatic kicking of 
ill-behaving nodes (on example, hanging due to long GC pauses) until we 
realised the necessity of changing default behavior via property.

Right solution is to kick nodes only if failure threshold is reached. Such 
behavior should be always enabled.

 



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

[jira] [Created] (IGNITE-7647) Apache Ignite RPM packages

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7647:


 Summary: Apache Ignite RPM packages
 Key: IGNITE-7647
 URL: https://issues.apache.org/jira/browse/IGNITE-7647
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov
Assignee: Peter Ivanov


Repack RPM specification to:
* be able to build package from source code
* divide single package into multiple packages (core + optional).



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

Re: Removing "fabric" from Ignite binary package name

[Sergey Kozlov]

+1 hadoop accelerator removing for AI 2.5

Also probably IGFS should be either removed or refactored, e.g. create FS
directly over the data region without using "cache" entity as an
intermidiate stage

On Thu, Feb 8, 2018 at 2:13 AM, Denis Magda  wrote:

> Anton,
>
> I don’t get how the hadoop editions are related to this task. The project
> is not named as “data fabric” for a while. Check up the site or docs.
>
> The “fabric” word is being removed from all over the places and needs to
> be removed from the editions’ names.
>
> As for the hadoop future, my personal position is to retire this component
> and forget about it. I would restart the conversation again after we done
> with 2.4.
>
> —
> Denis
>
> > On Feb 7, 2018, at 2:13 AM, Anton Vinogradov  wrote:
> >
> > Denis, Petr,
> >
> > I checked PR and found we have *overcomplicated* logic with "fabric" and
> > "hadoop" postfixs.
> >
> > Do we really need to assembly 2 editions?
> > "Hadoop" edition still valued?
> >
> > My proposal is to get rid of "hadoop" edition and replace it with
> > instruction of how to use "fabric" edition instead.
> > Instruction will be pretty easy -> move "hadoop" folder from "optional"
> to
> > root directory :)
> >
> > In that case we can just remove all postfix logic from maven poms and
> > simplify release process.
> >
> > On Thu, Dec 28, 2017 at 9:20 PM, Denis Magda  wrote:
> >
> >> Petr, thanks for solving it!
> >>
> >> Hope that Anton V. or some other build master will double-check the
> >> changes and merge them.
> >>
> >> —
> >> Denis
> >>
> >>> On Dec 28, 2017, at 8:29 AM, Petr Ivanov  wrote:
> >>>
> >>> IGNITE-7251 is done, needs review and some additional tests. See PR
> >> #3315 [1].
> >>>
> >>>
> >>> [1] https://github.com/apache/ignite/pull/3315 <
> >> https://github.com/apache/ignite/pull/3315>
> >>>
> >>>
> >>>
>  On 20 Dec 2017, at 23:15, Denis Magda  wrote:
> 
>  Petr, thanks, such a swift turnaround!
> 
>  Have you found the one who can asses and review the changes?
> 
>  Maintainers label might be helpful. Just ping them directly:
>  https://cwiki.apache.org/confluence/display/IGNITE/How+
> >> to+Contribute#HowtoContribute-ReviewProcessandMaintainers <
> >> https://cwiki.apache.org/confluence/display/IGNITE/How+
> >> to+Contribute#HowtoContribute-ReviewProcessandMaintainers>
> 
> 
>  —
>  Denis
> 
> > On Dec 20, 2017, at 12:24 AM, Petr Ivanov 
> wrote:
> >
> > Assigned myself — done the same work while preparing RPM package.
> > But for fixing DEVNOTES.txt waiting for review and merge of
> >> IGNITE-7107 [1].
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-7107
> >
> >
> >
> >> On 19 Dec 2017, at 22:55, Denis Magda  wrote:
> >>
> >> All the bids were accepted and the verdict is executed:
> >> https://issues.apache.org/jira/browse/IGNITE-7251 <
> >> https://issues.apache.org/jira/browse/IGNITE-7251>
> >>
> >> Who is ready to pick this up?
> >>
> >> —
> >> Denis
> >>
> >>> On Dec 19, 2017, at 5:35 AM, Anton Vinogradov <
> >> avinogra...@gridgain.com> wrote:
> >>>
> >>> +1б фо шур
> >>>
> >>> On Tue, Dec 19, 2017 at 9:59 AM, Vladimir Ozerov <
> >> voze...@gridgain.com>
> >>> wrote:
> >>>
>  +1б вуаштшеудн
> 
>  On Tue, Dec 19, 2017 at 2:34 AM, Valentin Kulichenko <
>  valentin.kuliche...@gmail.com> wrote:
> 
> > +1
> >
> > On Mon, Dec 18, 2017 at 12:24 PM, Dmitriy Setrakyan <
>  dsetrak...@apache.org
> >>
> > wrote:
> >
> >> +1 (completely agree)
> >>
> >> On Mon, Dec 18, 2017 at 10:21 AM, Denis Magda <
> dma...@apache.org>
>  wrote:
> >>
> >>> Igniters,
> >>>
> >>> Apache Ignite binary releases still include “fabric” word in
> >> their
> > names:
> >>> https://ignite.apache.org/download.cgi#binaries <
> >>> https://ignite.apache.org/download.cgi#binaries>
> >>>
> >>> For instance, this is a full name of the previous release -
> >>> apache-ignite-fabric-2.3.0-bin.
> >>> It’s a little oversight on our side because the project has not
> >> been
> >>> positioned as a fabric for a while.
> >>>
> >>> Proposal! Remove “fabric” from the name and have the binary
> >> releases
> >> named
> >>> as - apache-ignite-{version}-bin.
> >>>
> >>> If we’re in consensus then let’s make the change in 2.4.
> >>>
> >>> —
> >>> Denis
> >>>
> >>
> >
> 
> >>
> >
> 
> >>>
> >>
> >>
>
>


-- 
Sergey Kozlov
GridGain Systems
www.gridgain.com

[jira] [Created] (IGNITE-7646) OSGI tests fail to unlock build directory causing following builds to fail to start

[Peter Ivanov (JIRA)]

Peter Ivanov created IGNITE-7646:


 Summary: OSGI tests fail to unlock build directory causing 
following builds to fail to start
 Key: IGNITE-7646
 URL: https://issues.apache.org/jira/browse/IGNITE-7646
 Project: Ignite
  Issue Type: Task
Reporter: Peter Ivanov


After running test suite [Ignite Tests 2.4+ \[Java 8\] Ignite 
OSGi|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgniteOSGi]
 under Windows based agent, following builds fail to start with error
{code}
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle1\version0.0\bundle.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle2\version0.0\bundle.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle3\version0.0\bundle.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle4\version0.0\bundle.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle5\version0.0\bundle.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle6\version0.0\bundle.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle7\version0.0\bundle.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\bundle8\version0.0\bundle.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\cache\cache.lock
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\data\log\karaf.log
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.apache.karaf.diagnostic.boot-4.0.2.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.apache.karaf.jaas.boot-4.0.2.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.apache.karaf.main-4.0.2.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\boot\org.osgi.core-6.0.0.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\javax.annotation-api-1.2.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.karaf.exception-4.0.2.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.bundles.xalan-2.7.2_2.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.bundles.xalan-serializer-2.7.2_1.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.activation-api-1.1-2.5.0.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.jaxb-api-2.2-2.5.0.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.jaxp-api-1.4-2.5.0.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.jaxws-api-2.2-2.5.0.jar
[16:30:24]Failed to delete file: 
C:\BuildAgent\work\bd85361428dcdb1\modules\osgi\target\paxexam\unpack\f12af441-dfed-411b-9784-87dafedfac4f\lib\endorsed\org.apache.servicemix.specs.saaj-api-1.3-2.5.0.jar
[16:30:24]Failed to delete file: