[jira] [Created] (IGNITE-3821) Web console: exception on clicking Showquery after scan

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-3821:
--

 Summary: Web console: exception on clicking Showquery after scan
 Key: IGNITE-3821
 URL: https://issues.apache.org/jira/browse/IGNITE-3821
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov
Assignee: Andrey Novikov


start demo
scan
next
show query
{code}
11:41:27.984 Error: e.queryArgs.query is null
t.defaulthttps://staging-console.gridgain.com/app.cd7e3ceffba3eec415ba.js:9:1211
anonymous/fn@https://staging-console.gridgain.com/common.a226e813cf92d65f293b.js
 line 27 > Function:2:341
t@https://staging-console.gridgain.com/common.a226e813cf92d65f293b.js:26:2231
[275]/https://staging-console.gridgain.com/common.a226e813cf92d65f293b.js:28:18011
En/this.$gethttps://staging-console.gridgain.com/common.a226e813cf92d65f293b.js:26:12405
En/this.$gethttps://staging-console.gridgain.com/common.a226e813cf92d65f293b.js:26:12637
[275]/https://staging-console.gridgain.com/common.a226e813cf92d65f293b.js:28:18061
[755]/https://staging-console.gridgain.com/vendor.bcd603665fb745ac0256.js:101:2383
[755]/https://staging-console.gridgain.com/vendor.bcd603665fb745ac0256.js:101:437
1common.a226e813cf92d65f293b.js:25:29330
o/<()common.a226e813cf92d65f293b.js:25
bt/this.$get

[jira] [Created] (IGNITE-3820) Web console: 'undo' apper in wrong section

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-3820:
--

 Summary: Web console: 'undo' apper in wrong section
 Key: IGNITE-3820
 URL: https://issues.apache.org/jira/browse/IGNITE-3820
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov
Assignee: Dmitriyff
Priority: Minor


Create a new cache - Save.
Open Memory section and open Mode drop down list but do not select any item.
Observing - 'undo' appear in the General section.



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

Re: Pull request for IGNITE-3699

[Valentin Kulichenko]

Hi Amir,

I reviewed your changes and left my comments in the ticket.

-Val

On Wed, Aug 31, 2016 at 8:17 AM, Amir Akhmedov 
wrote:

> Hi community,
>
> I raised a pull request [1] Can you please review it?
>
> [1] https://github.com/apache/ignite/pull/1011
>
> Thanks.
>

[GitHub] ignite pull request #1024: IGNITE-3819: Added prints for ODBC errors.

[isapego]

GitHub user isapego opened a pull request:

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

IGNITE-3819: Added prints for ODBC errors.



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

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

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

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


commit 12fd4976f482ebc43831754645e34042c9073b2d
Author: sboikov 
Date:   2016-08-25T09:29:04Z

Fixed GridQueryParsingTest.

commit dabd86c62e39eb983ef3d198c8b8ee96d2623c84
Author: Andrey Novikov 
Date:   2016-08-31T09:00:19Z

IGNITE-3811 Fixed query for merge with complex key on SQL Server.

commit 70e69cb7aa08c268b07920838add4a40e28fe25d
Author: isapego 
Date:   2016-08-31T13:47:11Z

IGNITE-3390: Added DSN configuration window.

commit 12f532986677c30a716f73aeaa7d3587dd701f55
Author: sboikov 
Date:   2016-09-01T14:05:15Z

Merge remote-tracking branch 'remotes/community/ignite-1.6.6' into 
ignite-1.6.7

commit 392b0143a18d48869d1f8ec93f328b1e59f7a105
Author: isapego 
Date:   2016-09-01T16:18:08Z

IGNITE-3819: Added prints for ODBC errors.




---
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.
---

IGNITE-3601 Read-only optimistic transaction shouldn't throw an exception if entry version was not changed.

[Vladislav Pyatkov]

Hi,

I prepared PR[1] for read only transaction.

[1]: https://github.com/apache/ignite/pull/1001

[jira] [Created] (IGNITE-3819) ODBC: Print stack trace on error.

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-3819:
---

 Summary: ODBC: Print stack trace on error.
 Key: IGNITE-3819
 URL: https://issues.apache.org/jira/browse/IGNITE-3819
 Project: Ignite
  Issue Type: Task
  Components: odbc
Reporter: Igor Sapego






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

[GitHub] ignite pull request #1023: IGNITE-3613 IGFS: IgfsImpl.size() doesn't take se...

[tledkov-gridgain]

GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-3613 IGFS: IgfsImpl.size() doesn't take secondary file system in 
count.



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

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

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

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


commit dabd86c62e39eb983ef3d198c8b8ee96d2623c84
Author: Andrey Novikov 
Date:   2016-08-31T09:00:19Z

IGNITE-3811 Fixed query for merge with complex key on SQL Server.

commit 70e69cb7aa08c268b07920838add4a40e28fe25d
Author: isapego 
Date:   2016-08-31T13:47:11Z

IGNITE-3390: Added DSN configuration window.

commit 0434bf5476249cab91bcd36b064d40cb2c499699
Author: tledkov-gridgain 
Date:   2016-09-01T15:08:29Z

IGNITE-3613 IGFS: IgfsImpl.size() doesn't take secondary file system in 
count.




---
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.
---

IGNITE-532 Implement IgniteAkkaStreamer to stream data from Akka actors.

[chandresh pancholi]

Hi,

I have raised PR[1] for JIRA tickets[2].

Please review and let me know if any changes required.

[1] https://github.com/apache/ignite/pull/1019
[2]https://issues.apache.org/jira/browse/IGNITE-532

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

[GitHub] ignite pull request #1019: IGNITE-532 - Implement IgniteAkkaStreamer to stre...

[chandresh-pancholi]

GitHub user chandresh-pancholi opened a pull request:

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

IGNITE-532 - Implement IgniteAkkaStreamer to stream data from Akka actors



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

$ git pull https://github.com/chandresh-pancholi/ignite master

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

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


commit 936a105e75c894914867e47cb97df5af62c9316e
Author: chandresh-pancholi 
Date:   2016-09-01T11:51:33Z

IGNITE-532 - Implement IgniteAkkaStreamer to stream data from Akka actors




---
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 #1018: Ignite 3817

[alexpaschenko]

GitHub user alexpaschenko opened a pull request:

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

Ignite 3817



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

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

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

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


commit ca1381facd9a83b723fbeaed85a76672b05e5d25
Author: EdShangGG 
Date:   2016-08-30T11:53:46Z

Merge remote-tracking branch 'ignite-gg/ignite-1.7.2' into gg-master

commit b0810667bc396d2787f734eeaf9f55f5204c4d65
Author: Alexander Paschenko 
Date:   2016-08-31T13:10:32Z

Merge remote-tracking branch 'origin/master'

commit ee91ab3532c1c278c28c95a12e4ec76b4a54883e
Author: Alexander Paschenko 
Date:   2016-09-01T10:21:50Z

Merge remote-tracking branch 'origin/master'

commit 2218805e543c28916e312cb32793ddfcc71b07c8
Author: Alexander Paschenko 
Date:   2016-09-01T10:30:01Z

IGNITE-3817 Consider schema presence flag on building binary object from 
another object




---
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 #1017: IGNITE-3809: Fix for ArrayIndexOutOfBoundsExcepti...

[shroman]

GitHub user shroman opened a pull request:

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

IGNITE-3809: Fix for ArrayIndexOutOfBoundsException in GridUnsafeLru.



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

$ git pull https://github.com/shroman/ignite ignite-3809

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

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


commit ad91f65d804134f2fd25fc42ebc98610948785d3
Author: shtykh_roman 
Date:   2016-09-01T09:41:20Z

IGNITE-3809: ArrayIndexOutOfBoundsException in GridUnsafeLru.




---
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 #997: IGNITE-3789 Test for EntryProcessor/partition evts

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-1192 Implementation (Integration with Spring Data)

[Eduard Shangareev]

Greetings, guys.

So, the current implementation was found adequate for the first version.
But there are two issues which Semen found.

1) now cache name is bound to a repository at compile time, could you
please try to investigate if a more flexible binding is possible?
2) as I see now all spring-data integrations are hosted here -
https://github.com/spring-projects, Could you please investigated how
ignite integration can be added there?

First one, I don't see possibilities to provide cache names from Spring
configuration to repository factory (except system properties).
Second, I haven't found how to publish our spring-data implementation to
spring-projects repository.

I will continue the investigation.
But maybe someone already knows the answers.


On Tue, Aug 9, 2016 at 2:46 PM, Eduard Shangareev <
eduard.shangar...@gmail.com> wrote:

> Guys, I have made a pull request.
>
> https://github.com/apache/ignite/pull/931
> 
>
> New module spring-data was added.
>
> The example of repository:
>
> @RepositoryConfig(cacheName = "cache")
> public interface FirstRepository extends IgniteRepository {
> /** */
> public List findByFirstName(String val);
>
> /** */
> public List findByFirstNameContaining(String val);
>
> /** */
> public List findByFirstNameRegex(String val, Pageable pageable);
>
> /** */
> public Collection findTopByFirstNameContaining(String val);
>
> /** */
> public Iterable findFirst10ByFirstNameLike(String val);
>
> /** */
> public int countByFirstNameLike(String val);
>
> /** */
> public int countByFirstNameLikeAndSecondNameLike(String like1, String 
> like2);
>
> /** */
> public int countByFirstNameStartingWithOrSecondNameStartingWith(String 
> like1, String like2);
>
> /** */
> public List> findBySecondNameLike(String 
> val);
>
> /** */
> public Cache.Entry findTopBySecondNameLike(String val);
>
> /** */
> public Person findTopBySecondNameStartingWith(String val);
>
> /** */
> @Query("firstName = ?")
> public List simpleQuery(String val);
>
> /** */
> @Query("firstName REGEXP ?")
> public List queryWithSort(String val, Sort sort);
>
> /** */
> @Query("SELECT * FROM Person WHERE firstName REGEXP ?")
> public List queryWithPageable(String val, Pageable pageable);
>
> /** */
> @Query("SELECT secondName FROM Person WHERE firstName REGEXP ?")
> public List selectField(String val, Pageable pageable);
>
> /** */
> @Query("SELECT _key, secondName FROM Person WHERE firstName REGEXP ?")
> public List selectSeveralField(String val, Pageable pageable);
>
> /** */
> @Query("SELECT count(1) FROM (SELECT DISTINCT secondName FROM Person 
> WHERE firstName REGEXP ?)")
> public int countQuery(String val);
> }
>
>
> A user should extend IgniteRepository and provide cache name via
> @RepositoryConfig.
>
> IgniteRepository extends CrudRepository and deprecates unsupported
> operation (without id).
>
>
>
>
>
> On Tue, Aug 9, 2016 at 12:06 AM, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
>> Eduard,
>>
>> It's up to you :) I'm just saying that we should split the big task into
>> smaller ones.
>>
>> -Val
>>
>> On Mon, Aug 8, 2016 at 3:57 AM, Eduard Shangareev <
>> eduard.shangar...@gmail.com> wrote:
>>
>> > Hi, Valentin.
>> > I am going to close these ticket with some prototype and create new ones
>> > (maybe, with umbrella one).
>> >
>> > Will it work?
>> >
>> > On Sat, Aug 6, 2016 at 8:03 AM, Valentin Kulichenko <
>> > valentin.kuliche...@gmail.com> wrote:
>> >
>> > > Hi Eduard,
>> > >
>> > > This is too much information :)
>> > >
>> > > I think you should create separate tickets for different aspects of
>> > Spring
>> > > Data integration and use IGNITE-1192 only as an umbrella, because
>> > otherwise
>> > > it will be flooded by comments. This will allow to implement this
>> > > functionality step by step and track the progress better.
>> > >
>> > > Agree?
>> > >
>> > > -Val
>> > >
>> > > On Fri, Aug 5, 2016 at 4:17 AM, Eduard Shangareev <
>> > > eduard.shangar...@gmail.com> wrote:
>> > >
>> > > > So there is no async support for query, therefore we can't support
>> > > futures
>> > > > as return type (paragraph 2).
>> > > >
>> > > > On Thu, Aug 4, 2016 at 6:08 PM, Eduard Shangareev <
>> > > > eduard.shangar...@gmail.com> wrote:
>> > > >
>> > > > > I have looked at Querydsl and QbE and I think their support
>> should be
>> > > > > postponed.
>> > > > >
>> > > >
>> > >
>> >
>>
>
>

[jira] [Created] (IGNITE-3816) CacheJdbcPojoStore check for column names should be case insensitive

[Alexey Kuznetsov (JIRA)]

Alexey Kuznetsov created IGNITE-3816:


 Summary: CacheJdbcPojoStore check for column names should be case 
insensitive
 Key: IGNITE-3816
 URL: https://issues.apache.org/jira/browse/IGNITE-3816
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.6
Reporter: Alexey Kuznetsov
Assignee: Alexey Kuznetsov
 Fix For: 1.8


Current logic just put column names as is and if user defined them in low 
register an NPE will be thrown because later search for column will be with 
upper case. Also if column not found a proper Excepton should be thrown, not 
NPE.



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

new committer: Saikat Maitra

[Denis Magda]

The Project Management Committee (PMC) for Apache Ignite has asked Saikat 
Maitra to become a committer and we are pleased to announce that they have 
accepted.

Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.
Being a PMC member enables assistance with the management
and to guide the direction of the project.

—
Denis