[GitHub] ignite pull request: IGNITE-3108 .NET: IgniteConfiguration.Communi...

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-3020 .NET: Ensure that Windows service...

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-3115) List of ODBC minor issues

[Vasilisa Sidorova (JIRA)]

Vasilisa  Sidorova created IGNITE-3115:
--

 Summary: List of ODBC minor issues
 Key: IGNITE-3115
 URL: https://issues.apache.org/jira/browse/IGNITE-3115
 Project: Ignite
  Issue Type: Bug
  Components: odbc
Affects Versions: 1.6
 Environment: Ubuntu 14.04, Win7
Reporter: Vasilisa  Sidorova
Priority: Minor
 Fix For: 1.6


There is the list of minor issues for ODBC feature:

1. Win7:

1.1 install_amd64.cmd ODBC driver installation: 

  1.1.1 The final script output is "32-bit driver can not be found: """. 
It's not necessary to find  32-bit driver. Please, fix it
  1.2.1 It's possible to write path to the folder into registry. Please, 
add path-to-file validation into the script

1.2 Win Administrative Tools GUI:

  1.2.1 DNS settings for Apache Ignite ODBC driver should be disabled (as 
this is not implemented yet)

1.3 Documentation:

  1.3.1 Please, add  information that odbc should be building  individual 
into "Building binaries:" part of the IGNITE_HOME/platforms/cpp/DEVNOTES.txt
  1.3.2 Please relocate instruction "Most likely you will need OS 
administrator privileges to execute these scripts." before run install script 
in the "Installing ODBC driver on Windows" part of  the 
IGNITE_HOME/platforms/cpp/odbc/README.txt

2. Ubuntu - documentation:

2.1 It will be more user-friendly to mention that path to libignite-odbc.so  
should be in the LD_LIBRARY_PATH environment variable in the "Running examples 
on Linux" part of the IGNITE_HOME/platforms/cpp/examples/README.txt
2.2 The command
{noformat}
* libtoolize && aclocal && autoheader && automake --add-missing && autoreconf
{noformat}
is absent in the "Running examples on Linux" part of the 
IGNITE_HOME/platforms/cpp/examples/README.txt



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3114) "IllegalStateException: Row conflict should never happen" during load test

[Ksenia Rybakova (JIRA)]

Ksenia Rybakova created IGNITE-3114:
---

 Summary: "IllegalStateException: Row conflict should never happen" 
during load test
 Key: IGNITE-3114
 URL: https://issues.apache.org/jira/browse/IGNITE-3114
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.6
Reporter: Ksenia Rybakova
Priority: Minor


Configuration:
- 3 drivers at 1 host, 30 servers at 3 hosts;
- all operations are enabled except SCAN_QUERY, SQL_QUERY and CONTINUOUS_QUERY
- for other settings see attached benchmark-cache-load.properties file

Steps to reproduce:
1) Run load test:
 ./bin/benchmark-run-all.sh config/benchmark-cache-load.properties
2) Check all server log files. 

Expected:
No exceptions.

Actual:
"java.lang.IllegalStateException: Row conflict should never happen, unique 
indexes are not supported" exceptions accur while running load test benchmark. 
In my case I noticed that all these exceptions happened only at 20th server 
(1st server node at the 3rd host).

java.lang.IllegalStateException: Row conflict should never happen, unique 
indexes are not supported.
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.doUpdate(GridH2Table.java:410)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:340)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.store(IgniteH2Indexing.java:524)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.store(GridQueryProcessor.java:700)
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.store(GridCacheQueryManager.java:407)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.updateIndex(GridCacheMapEntry.java:3849)
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3309)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:1618)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamerUpdateJob.call(DataStreamerUpdateJob.java:140)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:305)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:50)
at 
org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:80)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:847)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:105)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:810)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request: Ignite JTA and WebSphere Application Server 8...

[ashutakGG]

GitHub user ashutakGG opened a pull request:

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

Ignite JTA and WebSphere Application Server 8.5.5



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

$ git pull https://github.com/gridgain/apache-ignite 
ignite-2959-wsphere-tx-support

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

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


commit 8135802238ece095159c41e8f695526e3ddb0bc3
Author: ashutak 
Date:   2016-03-16T13:45:28Z

WebSphereTmFactory + war 
(http://127.0.0.1:9080/ignite-weblogic-test/jta-test)

commit f235e3f794d17dbb047168c5296780a917909369
Author: ashutak 
Date:   2016-03-16T13:50:00Z

tmp change

commit 74a5c13b106d88a4ffe0b503138a02455e45c67f
Author: ashutak 
Date:   2016-03-16T14:04:09Z

undo tmp chage

commit 868bc6add88a76a2de140e3a8e96a6615f21d225
Author: ashutak 
Date:   2016-03-25T14:03:15Z

 this is works on AWS

commit b1618af3d0cefe7ed6f4505ae0e4565c30dfd5f5
Author: ashutak 
Date:   2016-03-25T14:21:28Z

discovery cfg

commit cfcd7f2519982694d0fa110af044809a59f0352d
Author: ashutak 
Date:   2016-03-25T14:21:53Z

does not work

commit 3742fa3d5750fbf14cb9837a08d6727a333939ef
Author: ashutak 
Date:   2016-03-25T15:31:11Z

working version

commit 809674357f04596c420aaca55d732870c90ca8c8
Author: ashutak 
Date:   2016-03-28T09:35:27Z

TestJtaTxServlet

commit c2b5cef3de13256afd087925f9d74f237f4b03a8
Author: ashutak 
Date:   2016-03-28T09:44:13Z

WebSphereTmFactory

commit 956167e41d1857a3e921010ee62eb71fc088efc4
Author: ashutak 
Date:   2016-04-06T14:56:07Z

Merge branch 'master' into tmp-wsphere-tx-support

commit bac4f28485e24fc2e31f8d691499b60cb445006f
Author: ashutak 
Date:   2016-05-11T13:40:11Z

Merge branch 'ignite-1.6' into ignite-2959-wsphere-tx-support

commit ae7b1a39e3da164b043031c58b827195ce284764
Author: ashutak 
Date:   2016-05-11T15:40:24Z

ignite-2959: CacheReflectionTmFactory added + WebSphereTmFactory moved + 
created websphere-test module




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-3049

[vldpyatkov]

Github user vldpyatkov closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-3049

[vldpyatkov]

GitHub user vldpyatkov opened a pull request:

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

IGNITE-3049

Yardstick sql load tests should read sql quiers from an external file

Merged missing changes.

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

$ git pull https://github.com/vldpyatkov/ignite ignite-3049_new

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

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


commit 726e8c1e18840c0a6f2195dfcd8f9c3ddb830d41
Author: vdpyatkov 
Date:   2016-05-11T15:04:52Z

IGNITE-3049
Yardstick sql load tests should read sql quiers from an external file

Merged missing changes.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] ignite pull request: IGNITE-3108 .NET: IgniteConfiguration.Communi...

[ptupitsyn]

GitHub user ptupitsyn opened a pull request:

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

IGNITE-3108 .NET: IgniteConfiguration.CommunicationSpi



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

$ git pull https://github.com/ptupitsyn/ignite ignite-3108

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

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


commit 9b2785a994f19861db32017fbc2ba2554e025a60
Author: Pavel Tupitsyn 
Date:   2016-05-11T10:51:33Z

IGNITE-3108 .NET: IgniteConfiguration.CommunicationSpi - initial commit

commit 96656d8adb9993a2f5ca9a050900731ece2e1a3f
Author: Pavel Tupitsyn 
Date:   2016-05-11T11:45:01Z

wip

commit 1cd661bf94372d585696701c16894373e0ae05db
Author: Pavel Tupitsyn 
Date:   2016-05-11T11:52:29Z

wip

commit 02774b940209f6b0ea7da584a663065028f504bd
Author: Pavel Tupitsyn 
Date:   2016-05-11T11:55:28Z

wip

commit aa3e4a848cc7135179464ef24de18e546a7f8487
Author: Pavel Tupitsyn 
Date:   2016-05-11T12:07:14Z

wip

commit 31c3fc2e45f71e4214b534137929312896d697f3
Author: Pavel Tupitsyn 
Date:   2016-05-11T12:09:06Z

wip

commit 0515d64d796056c4897b81c0a87e0ea00d9e74bd
Author: Pavel Tupitsyn 
Date:   2016-05-11T12:15:05Z

wip

commit 079203a0983f4e0f495c78235cf410e59e75e607
Author: Pavel Tupitsyn 
Date:   2016-05-11T12:16:15Z

wip

commit fa07b6e039e35e981c08c16181e91640b970a50b
Author: Pavel Tupitsyn 
Date:   2016-05-11T12:27:22Z

wip

commit 72e16aa102cf288eb28956790bb24f51019dfb35
Author: Pavel Tupitsyn 
Date:   2016-05-11T12:31:52Z

All properties done

commit de0140b99fe9c2d6bed4fe0c3f3fe98eac077c37
Author: Pavel Tupitsyn 
Date:   2016-05-11T13:37:30Z

wip

commit 5565d18a611422d98e2cc4778d6d8571c06000f4
Author: Pavel Tupitsyn 
Date:   2016-05-11T13:39:51Z

read/write done

commit c38fb18ae11927d15a37f01522f272a12579bd2e
Author: Pavel Tupitsyn 
Date:   2016-05-11T13:47:08Z

wip

commit c7e330471d22653354c524ad216d20a05eeb6c99
Author: Pavel Tupitsyn 
Date:   2016-05-11T13:53:32Z

wip

commit 39998947836ef037639e3fb18590966360826b6f
Author: Pavel Tupitsyn 
Date:   2016-05-11T13:56:17Z

wip

commit d2f44b6bbe6dbebe8c8740ad48ae85504ad28220
Author: Pavel Tupitsyn 
Date:   2016-05-11T13:58:05Z

wip

commit b54b2b7cae096506d19cf1356230db88fda05d31
Author: Pavel Tupitsyn 
Date:   2016-05-11T14:05:10Z

test added

commit e188c409ced77d7a5d890cda4e9223974ff3cf9b
Author: Pavel Tupitsyn 
Date:   2016-05-11T14:07:19Z

fix defaults

commit 04a778d15fae648776f849503c7cd3b710331030
Author: Pavel Tupitsyn 
Date:   2016-05-11T14:11:19Z

wip

commit 01ec5980f9ca1d2d5a3853513f51526ed076e029
Author: Pavel Tupitsyn 
Date:   2016-05-11T14:15:09Z

wip

commit 242cc97047c7d15c3367697a2afb8eb87ad7be45
Author: Pavel Tupitsyn 
Date:   2016-05-11T14:17:29Z

fix test

commit de83a78ef18735d3f5c0eb0896138dc449d2c3cb
Author: Pavel Tupitsyn 
Date:   2016-05-11T14:24:12Z

Update XSD

commit e967dc319bf40b3e7cfd87f1b4a12a11ec568aee
Author: Pavel Tupitsyn 
Date:   2016-05-11T14:27:35Z

XML config test added




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-3113) CPP: Improve documentation.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-3113:
---

 Summary: CPP: Improve documentation.
 Key: IGNITE-3113
 URL: https://issues.apache.org/jira/browse/IGNITE-3113
 Project: Ignite
  Issue Type: Task
  Components: documentation
Affects Versions: 1.5.0.final
Reporter: Igor Sapego
Assignee: Igor Sapego
 Fix For: 1.6


Current C++ documentation is poor and does not give much of information about 
the classes and methods. Improve documentation adding more detailed information 
about the classes and methods usage, fail cases and maybe provide some simple 
guidelines/explanations of the methods usage.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request: Ignite db x

[avinogradovgg]

GitHub user avinogradovgg opened a pull request:

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

Ignite db x



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

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

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

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






---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [jira] [Commented] (IGNITE-2693) withKeepBinary and non-binary marshallers

[Dood]

Anyone willing to help me a bit to finish this ticket for 1.6? :-) Thanks!

On 4/12/2016 6:03 AM, Vladimir Ozerov (JIRA) wrote:

 [ 
https://issues.apache.org/jira/browse/IGNITE-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15237114#comment-15237114
 ]

Vladimir Ozerov commented on IGNITE-2693:
-

Hi Oddo,

Any news on the matter?

Vladimir.


withKeepBinary and non-binary marshallers
-

 Key: IGNITE-2693
 URL: https://issues.apache.org/jira/browse/IGNITE-2693
 Project: Ignite
  Issue Type: Bug
  Components: general
Reporter: Sergey Kozlov
Assignee: Oddo
  Labels: newbie
 Fix For: 1.6


Currently the user is able to set {{.withKeepBinary()}} for any used 
marshaller. But it obviously causes ClassCastException for non-binary 
marshallers and should be available only for binary marshaller.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Introduction and Contribution Help

[Myles Baker]

Hi all, 

I just wanted to introduce myself - I am interested in Ignite and have been 
lurking for a while. I’ve been working in high performance computing for my 
entire career, starting at NASA followed by working at software companies and 
providing consulting services. I deal with data problems daily and appreciate 
data grids for scalability and performance challenges. 

So, the next step for my interest in Ignite is to start contributing to the 
project and understanding it at a deeper level technically. I’ve been following 
the  
instructions
 for contributing https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Workflow>,
 but I'm having trouble finding a good entry point for me to start 
contributing. I found a few newbie tickets that might be a good place to start: 
IGNITE-2049  and IGNITE-2895 
. However, these either use 
specific systems that I can’t test or reference the EA process, which I’m 
unfamiliar with. 

Any opinions? Other tickets that might be a better entry point for someone who 
has programmed in the JVM before? 

Thanks, 
Myles

[GitHub] ignite pull request: Ignite services with different class loaders ...

[ashutakGG]

Github user ashutakGG closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (IGNITE-3112) .NET: Allow merging Spring XML config with .NET config

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3112:
--

 Summary: .NET: Allow merging Spring XML config with .NET config
 Key: IGNITE-3112
 URL: https://issues.apache.org/jira/browse/IGNITE-3112
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 1.6
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.6


Introduce IgniteConfiguration.MergeSpringConfig bool property.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3111) .NET: Configure SSL without Spring

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3111:
--

 Summary: .NET: Configure SSL without Spring
 Key: IGNITE-3111
 URL: https://issues.apache.org/jira/browse/IGNITE-3111
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 1.6
Reporter: Pavel Tupitsyn
 Fix For: 1.7


User should be able to configure SLL in .NET terms without Spring and Java 
KeyStore.
See https://apacheignite.readme.io/docs/ssltls.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3110) Incorrect error messages on SQL page

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-3110:
--

 Summary: Incorrect error messages on SQL page
 Key: IGNITE-3110
 URL: https://issues.apache.org/jira/browse/IGNITE-3110
 Project: Ignite
  Issue Type: Sub-task
Reporter: Pavel Konstantinov
Assignee: Andrey Novikov






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] ignite pull request: IGNITE-2805: Transactions implementation for ...

[asfgit]

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Ignite 1.6 release timelines

[Igor Sapego]

Hi,

I have also finished transactions API for the C++ [1] and
it is also going to be included to 1.6. It is already merged to
release branch.

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

Best Regards,
Igor

On Wed, May 11, 2016 at 1:49 PM, Sergey Kozlov  wrote:

> The following issues found for 1.6 recently:
>
> IGNITE-3109 IgfsMapReduceExample fails ClassNotFoundException
> 
>  - critical
> IGNITE-3107 Help for tasks/events should be rephrased
> 
>  - trivial, doc issue
>
> On Wed, May 11, 2016 at 8:56 AM, Yakov Zhdanov 
> wrote:
>
> > Guys,
> >
> > I moved most of the tickets to 1.7 version.
> >
> > I had to leave the following tickets untouched (~80 tickets):
> > 1. labeled with - community important performance customer - Denis,
> > Vladimir and Val can you please review these tickets and move non-urgent
> > ones. You can use query below
> > 2. with status "in progress". Please everyone having such tickets move it
> > yourself or finish it in 1.6
> > 3. with status "patch available". Committers, please split the reviews
> and
> > let's include checked/tested fixes to 1.6. Others should be moved.
> >
> > Sam, can you please review and merge -
> > https://issues.apache.org/jira/browse/IGNITE-2744 - Optimize
> "unwindEvict"
> > call in GridCacheIoManager.processMessage().
> > 
> >
> > Query for p1:
> >
> > project = IGNITE AND fixVersion = 1.6 AND resolution = Unresolved AND
> > status not in ("Patch Available", "in progress") AND (labels in
> (community,
> > important, performance, perfomance, customer)) ORDER BY status DESC, due
> > ASC, priority DESC, created ASC
> >
> > Thanks!
> >
> > --Yakov
> >
> > 2016-05-11 9:47 GMT+06:00 Dmitriy Setrakyan :
> >
> > > Igniters,
> > >
> > > I just did a search on 1.6 issues and looks like we have 293 unresolved
> > > issues for 1.6. Obviously we are not going to be fixing all of them and
> > > most of them will have to be moved to 1.7.
> > >
> > > Yakov, given that you have most experience with Jira and have been
> > managing
> > > it before, do you mind moving the tickets? Here is the link to the
> > filter:
> > >
> > > http://bit.ly/24Mrddg
> > >
> > > Also, if anything needs to be addressed in 1.6, please list these
> tickets
> > > here, in this thread.
> > >
> > > Thanks,
> > > D.
> > >
> > > On Tue, May 10, 2016 at 6:00 AM, Pavel Tupitsyn <
> ptupit...@gridgain.com>
> > > wrote:
> > >
> > > > Dmitriy, yes, many of them do. I'll create 1.6 version on
> > > > apacheignite-net.readme.io and document them this week (task:
> > > > IGNITE-3101).
> > > >
> > > > Pavel.
> > > >
> > > > On Tue, May 10, 2016 at 3:52 PM, Dmitriy Setrakyan <
> > > dsetrak...@apache.org>
> > > > wrote:
> > > >
> > > > > Thanks Pavel, do any of these features require new documentation?
> > > > >
> > > > > On Tue, May 10, 2016 at 5:16 AM, Pavel Tupitsyn <
> > > ptupit...@gridgain.com>
> > > > > wrote:
> > > > >
> > > > > > Hi, here is a list of major .NET features included in 1.6 (all
> > closed
> > > > and
> > > > > > merged):
> > > > > >
> > > > > > * LINQ Provider for SQL queries (IGNITE-1630)
> > > > > > * NuGet distribution (IGNITE-1626)
> > > > > > * C#, app.config and web.config configuration (instead of Spring
> > XML)
> > > > > > (IGNITE-1906, IGNITE-2380)
> > > > > > * Atomic data structures (IGNITE-1563)
> > > > > > * Universal AnyCPU binaries (instead of separate x64/x86)
> > > (IGNITE-2694)
> > > > > > * Call Java services (IGNITE-2686)
> > > > > > * Java-based continuous query filters (IGNITE-2977)
> > > > > > * Mixed-cluster Compute (IGNITE-2621)
> > > > > > * Compute task cancellation (IGNITE-2228)
> > > > > > * Binary format compact footers (IGNITE-2702)
> > > > > > * Raw mode reflective serialization (IGNITE-1419)
> > > > > > * Automatic Java detection: no need for JAVA_HOME (IGNITE-2866)
> > > > > >
> > > > > > Thanks,
> > > > > > Pavel.
> > > > > >
> > > > > >
> > > > > > On Thu, May 5, 2016 at 5:01 PM, Igor Sapego <
> isap...@gridgain.com>
> > > > > wrote:
> > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > > IGNITE-1786 is fully merged to master.
> > > > > > >
> > > > > > > Best Regards,
> > > > > > > Igor
> > > > > > >
> > > > > > > On Wed, May 4, 2016 at 6:59 PM, Dmitriy Setrakyan <
> > > > > dsetrak...@apache.org
> > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Resending (fixed links)
> > > > > > > >
> > > > > > > > On Wed, May 4, 2016 at 8:46 AM, Dmitriy Setrakyan <
> > > > > > dsetrak...@apache.org
> > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Igniters,
> > > > > > > > >
> > > > > > > > > Looks like we are almost done with the outstanding issues,
> > > mainly
> > > > > > ODBC
> > > > > > > > > support and cache concurrent map changes. As far as the
> > > > concurrent
> > > > > > map,

Re: Ignite 1.6 release timelines

[Sergey Kozlov]

The following issues found for 1.6 recently:

IGNITE-3109 IgfsMapReduceExample fails ClassNotFoundException

 - critical
IGNITE-3107 Help for tasks/events should be rephrased

 - trivial, doc issue

On Wed, May 11, 2016 at 8:56 AM, Yakov Zhdanov  wrote:

> Guys,
>
> I moved most of the tickets to 1.7 version.
>
> I had to leave the following tickets untouched (~80 tickets):
> 1. labeled with - community important performance customer - Denis,
> Vladimir and Val can you please review these tickets and move non-urgent
> ones. You can use query below
> 2. with status "in progress". Please everyone having such tickets move it
> yourself or finish it in 1.6
> 3. with status "patch available". Committers, please split the reviews and
> let's include checked/tested fixes to 1.6. Others should be moved.
>
> Sam, can you please review and merge -
> https://issues.apache.org/jira/browse/IGNITE-2744 - Optimize "unwindEvict"
> call in GridCacheIoManager.processMessage().
> 
>
> Query for p1:
>
> project = IGNITE AND fixVersion = 1.6 AND resolution = Unresolved AND
> status not in ("Patch Available", "in progress") AND (labels in (community,
> important, performance, perfomance, customer)) ORDER BY status DESC, due
> ASC, priority DESC, created ASC
>
> Thanks!
>
> --Yakov
>
> 2016-05-11 9:47 GMT+06:00 Dmitriy Setrakyan :
>
> > Igniters,
> >
> > I just did a search on 1.6 issues and looks like we have 293 unresolved
> > issues for 1.6. Obviously we are not going to be fixing all of them and
> > most of them will have to be moved to 1.7.
> >
> > Yakov, given that you have most experience with Jira and have been
> managing
> > it before, do you mind moving the tickets? Here is the link to the
> filter:
> >
> > http://bit.ly/24Mrddg
> >
> > Also, if anything needs to be addressed in 1.6, please list these tickets
> > here, in this thread.
> >
> > Thanks,
> > D.
> >
> > On Tue, May 10, 2016 at 6:00 AM, Pavel Tupitsyn 
> > wrote:
> >
> > > Dmitriy, yes, many of them do. I'll create 1.6 version on
> > > apacheignite-net.readme.io and document them this week (task:
> > > IGNITE-3101).
> > >
> > > Pavel.
> > >
> > > On Tue, May 10, 2016 at 3:52 PM, Dmitriy Setrakyan <
> > dsetrak...@apache.org>
> > > wrote:
> > >
> > > > Thanks Pavel, do any of these features require new documentation?
> > > >
> > > > On Tue, May 10, 2016 at 5:16 AM, Pavel Tupitsyn <
> > ptupit...@gridgain.com>
> > > > wrote:
> > > >
> > > > > Hi, here is a list of major .NET features included in 1.6 (all
> closed
> > > and
> > > > > merged):
> > > > >
> > > > > * LINQ Provider for SQL queries (IGNITE-1630)
> > > > > * NuGet distribution (IGNITE-1626)
> > > > > * C#, app.config and web.config configuration (instead of Spring
> XML)
> > > > > (IGNITE-1906, IGNITE-2380)
> > > > > * Atomic data structures (IGNITE-1563)
> > > > > * Universal AnyCPU binaries (instead of separate x64/x86)
> > (IGNITE-2694)
> > > > > * Call Java services (IGNITE-2686)
> > > > > * Java-based continuous query filters (IGNITE-2977)
> > > > > * Mixed-cluster Compute (IGNITE-2621)
> > > > > * Compute task cancellation (IGNITE-2228)
> > > > > * Binary format compact footers (IGNITE-2702)
> > > > > * Raw mode reflective serialization (IGNITE-1419)
> > > > > * Automatic Java detection: no need for JAVA_HOME (IGNITE-2866)
> > > > >
> > > > > Thanks,
> > > > > Pavel.
> > > > >
> > > > >
> > > > > On Thu, May 5, 2016 at 5:01 PM, Igor Sapego 
> > > > wrote:
> > > > >
> > > > > > Hello,
> > > > > >
> > > > > > IGNITE-1786 is fully merged to master.
> > > > > >
> > > > > > Best Regards,
> > > > > > Igor
> > > > > >
> > > > > > On Wed, May 4, 2016 at 6:59 PM, Dmitriy Setrakyan <
> > > > dsetrak...@apache.org
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Resending (fixed links)
> > > > > > >
> > > > > > > On Wed, May 4, 2016 at 8:46 AM, Dmitriy Setrakyan <
> > > > > dsetrak...@apache.org
> > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Igniters,
> > > > > > > >
> > > > > > > > Looks like we are almost done with the outstanding issues,
> > mainly
> > > > > ODBC
> > > > > > > > support and cache concurrent map changes. As far as the
> > > concurrent
> > > > > map,
> > > > > > > we
> > > > > > > > had a performance drop, and I think it is pretty important
> that
> > > we
> > > > > > > address
> > > > > > > > it prior to the release.
> > > > > > > >
> > > > > > > > Can we please get an update for these tickets?
> > > > > > > >
> > > > > > > > IGNITE-2948 <
> https://issues.apache.org/jira/browse/IGNITE-2948
> > >
> > > -
> > > > > > > > Optimize usage of GridCacheConcurrentMap
> > > > > > > > IGNITE-1786 <
> https://issues.apache.org/jira/browse/IGNITE-1786
> > >
> > > -
> > > > > Need
> > > > > > > to
> > > > > > > > implement ODBC 

[jira] [Created] (IGNITE-3109) IgfsMapReduceExample fails ClassNotFoundException

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-3109:
-

 Summary: IgfsMapReduceExample fails ClassNotFoundException
 Key: IGNITE-3109
 URL: https://issues.apache.org/jira/browse/IGNITE-3109
 Project: Ignite
  Issue Type: Bug
  Components: IGFS
Affects Versions: 1.6
 Environment: Windows 10, Oracle JDK 1.7.0_80
Reporter: Sergey Kozlov
Priority: Critical
 Fix For: 1.6


1. Run the external node {{bin\ignite.bat 
examples\config\filesystem\example-igfs.xml}}
2. Run {{IgfsMapReduceExample}} with arguments {{\companies.txt 
(GERMANY|BRAZIL)}}:
{noformat}
[13:41:27] Topology snapshot [ver=2, servers=2, clients=0, CPUs=8, heap=4.5GB]

>>> IGFS map reduce example started.

Copying file to IGFS: 
C:\Work\apache-ignite-fabric-1.6.0-QASK1101-bin\examples\companies.txt
[13:41:29,722][ERROR][sys-#19%null%][GridTaskWorker] Failed to obtain remote 
job result policy for result from ComputeTask.result(..) method (will fail the 
whole task): GridJobResultImpl 
[job=o.a.i.i.processors.igfs.IgfsJobImpl@57196a65, sib=GridJobSiblingImpl 
[sesId=b52286f9451-e52c1381-bad9-4161-ab15-ad22c870a7d0, 
jobId=fa2286f9451-e52c1381-bad9-4161-ab15-ad22c870a7d0, 
nodeId=b2c68a38-383c-4a9f-b176-ec4633de3c8e, isJobDone=false], 
jobCtx=GridJobContextImpl 
[jobId=fa2286f9451-e52c1381-bad9-4161-ab15-ad22c870a7d0, timeoutObj=null, 
attrs={}], node=TcpDiscoveryNode [id=b2c68a38-383c-4a9f-b176-ec4633de3c8e, 
addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 192.168.2.107, 
2001:0:5ef5:79fb:2090:2da4:b079:309d], sockAddrs=[work-pc/192.168.2.107:47500, 
/0:0:0:0:0:0:0:1:47500, work-pc/192.168.2.107:47500, /127.0.0.1:47500, 
/192.168.2.107:47500, /2001:0:5ef5:79fb:2090:2da4:b079:309d:47500], 
discPort=47500, order=1, intOrder=1, lastExchangeTime=1462963287286, loc=false, 
ver=1.6.0#20160511-sha1:bd6a67f2, isClient=false], ex=class 
o.a.i.IgniteException: Failed to find class with given class loader for 
unmarshalling (make sure same version of all classes are available on all nodes 
or enable peer-class-loading): sun.misc.Launcher$AppClassLoader@1b3e02ed, 
hasRes=true, isCancelled=false, isOccupied=true]
class org.apache.ignite.IgniteException: Remote job threw user exception 
(override or implement ComputeTask.result(..) method if you would like to have 
automatic failover for this exception).
at 
org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker$3.apply(GridTaskWorker.java:912)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker$3.apply(GridTaskWorker.java:905)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6491)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:905)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:801)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:995)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1220)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:847)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:105)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:810)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteException: Failed to find class with 
given class loader for unmarshalling (make sure same version of all classes are 
available on all nodes or enable peer-class-loading): 
sun.misc.Launcher$AppClassLoader@1b3e02ed
at 
org.apache.ignite.internal.processors.job.GridJobWorker.initialize(GridJobWorker.java:424)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1089)
at 
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1766)
... 7 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to find class 
with given class loader for unmarshalling (make sure same version of all 
classes are available on all nodes or enable peer-class-loading): 
sun.misc.Launcher$AppClassLoader@1b3e02ed
at 
org.apache.ignite.marshaller.optimized.OptimizedMarshaller.unmarshal(OptimizedMarshaller

[jira] [Created] (IGNITE-3108) .NET: IgniteConfiguration.CommunicationSpi

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-3108:
--

 Summary: .NET: IgniteConfiguration.CommunicationSpi
 Key: IGNITE-3108
 URL: https://issues.apache.org/jira/browse/IGNITE-3108
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Affects Versions: 1.6
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.6


CommunicationSpi is very important for configuring clusters. 
Should be propagated to .NET so that users don't have to fall back to Spring 
XML.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3107) Help for tasks/events should be rephrased

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-3107:
-

 Summary: Help for tasks/events should be rephrased
 Key: IGNITE-3107
 URL: https://issues.apache.org/jira/browse/IGNITE-3107
 Project: Ignite
  Issue Type: Bug
  Components: visor
Affects Versions: 1.6
Reporter: Sergey Kozlov
Priority: Trivial
 Fix For: 1.6


{noformat}
 |   | of Event Storage SPI that is responsible for temporary storage of 
generated   |
 |   | events on each node can also affect the functionality of this 
command.|
 |   |  
 |
-|   | By default - all events are enabled and Ignite stores last 10,000 
local   |
+|   | By default - all events are disabled and Ignite stores last 10,000 
local  |
 |   | events on each node. Both of these defaults can be changed in 
configuration.  |
 
+---+{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-3106) Yardstick can't parse /config/queries.txt with license header

[Ilya Suntsov (JIRA)]

Ilya Suntsov created IGNITE-3106:


 Summary: Yardstick can't parse /config/queries.txt with license 
header
 Key: IGNITE-3106
 URL: https://issues.apache.org/jira/browse/IGNITE-3106
 Project: Ignite
  Issue Type: Task
  Components: general
Affects Versions: 1.6
Reporter: Ilya Suntsov
Priority: Blocker
 Fix For: 1.6


File yardstick/config/queries.txt contains queries that used for load tests. 
Yardstick can't parse this file with this license header:
{noformat}
# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements.  See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License.  You may obtain a copy of the License at
#
#  http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
{noformat}

Yardstick reads line in upper case and tried to execute it as query:
{noformat}
ERROR: Shutting down benchmark driver to unexpected exception.
Type '--help' for usage.
javax.cache.CacheException: class org.apache.ignite.IgniteException: Failed to 
parse query: # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 
implied.
<-->at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:674)
<-->at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.doSqlQuery(IgniteCacheRandomOperationBenchmark.java:858)
<-->at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeRandomOperation(IgniteCacheRandomOperationBenchmark.java:553)
<-->at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.executeOutOfTx(IgniteCacheRandomOperationBenchmark.java:495)
<-->at 
org.apache.ignite.yardstick.cache.load.IgniteCacheRandomOperationBenchmark.test(IgniteCacheRandomOperationBenchmark.java:158)
<-->at 
org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:176)
<-->at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteException: Failed to parse query: # 
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
<-->at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.queryTwoStep(GridQueryProcessor.java:811)
<-->at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:665)
<-->... 6 more
{noformat}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [IGNITE-2323] Improvments for http client

[chandresh pancholi]

Hi Dmitriy,

I have assigned it already to myself :) :) .
I have been busy with office work lately and didn't get a chance to
contribute.

Please provide any input regarding ignite-2323 so that it will help me to
start working on it.

Thanks


On Wed, May 11, 2016 at 12:45 PM, Dmitriy Setrakyan  wrote:

> Hi Chandresh,
>
> Welcome to the Ignite community!
>
> Please review the following sections on our Wiki and Website to get
> familiar with the development process:
>
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> https://ignite.apache.org/community/contribute.html#contribute
>
> Also, please let us know your Jira username, so we could add you to the
> list of Ignite contributors. This way you will be able to assign this
> ticket to yourself.
>
> Looking forward to your contributions.
>
> Thanks,
> D.
>
> On Tue, May 10, 2016 at 11:50 PM, chandresh pancholi <
> chandreshpancholi...@gmail.com> wrote:
>
> > Hi,
> >
> > I would like to work on ticket Improvments for http client [IGNITE-2323].
> >
> > Please suggest where to start or whats the entry point ?
> >
> > Thanks in advance.
> >
> > --
> > Chandresh Pancholi
> > Senior Software Engineer
> > Flipkart.com
> > Email-id:chandresh.panch...@flipkart.com
> > Contact:08951803660
> >
>



-- 
Chandresh Pancholi
Senior Software Engineer
Flipkart.com
Email-id:chandresh.panch...@flipkart.com
Contact:08951803660

Re: [IGNITE-2323] Improvments for http client

[Dmitriy Setrakyan]

Hi Chandresh,

Welcome to the Ignite community!

Please review the following sections on our Wiki and Website to get
familiar with the development process:

https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
https://ignite.apache.org/community/contribute.html#contribute

Also, please let us know your Jira username, so we could add you to the
list of Ignite contributors. This way you will be able to assign this
ticket to yourself.

Looking forward to your contributions.

Thanks,
D.

On Tue, May 10, 2016 at 11:50 PM, chandresh pancholi <
chandreshpancholi...@gmail.com> wrote:

> Hi,
>
> I would like to work on ticket Improvments for http client [IGNITE-2323].
>
> Please suggest where to start or whats the entry point ?
>
> Thanks in advance.
>
> --
> Chandresh Pancholi
> Senior Software Engineer
> Flipkart.com
> Email-id:chandresh.panch...@flipkart.com
> Contact:08951803660
>

[IGNITE-2323] Improvments for http client

[chandresh pancholi]

Hi,

I would like to work on ticket Improvments for http client [IGNITE-2323].

Please suggest where to start or whats the entry point ?

Thanks in advance.

-- 
Chandresh Pancholi
Senior Software Engineer
Flipkart.com
Email-id:chandresh.panch...@flipkart.com
Contact:08951803660

Re: Added documentation for Continuous Mapping, and Cron based scheduling

[Yakov Zhdanov]

Prachi, pages look good to me.

--Yakov

2016-05-11 3:14 GMT+06:00 Prachi Garg :

> Engineers,
>
> Can someone please review the documentation for -
>
>- Continuous Mapping -
>http://apacheignite.gridgain.org/v1.5/docs/continuous-mapping
>- CRON based scheduling -
>http://apacheignite.gridgain.org/v1.5/docs/cron-based-scheduling
>
> I will make it public and copy it to v1.6 after it is reviewed.
>
>
> Thanks,
> -Prachi
>