Re: IGNITE-3293 AWS bootstrap scripts patch for Ignite-Cassandra

Finally after a lot of work issue https://issues.apache.org/ jira/browse/IGNITE-3293 merged to master. Igor and Ilya, thanks for your efforts! On Thu, Jun 16, 2016 at 7:52 PM, Alexey Kuznetsov wrote: > I'm reviewed this issue. Comments added to ticket. > > On Mon, Jun

[GitHub] ignite pull request #794: IGNITE-3293 AWS bootstrap scripts patch for Ignite...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/794 --- 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

Re: Ignite 1.7 RELEASE_NOTES

Hi, Pavel and Konstantin Release notes should highlight key features for the released version and the current list looks good on my mind. But we can put as last item something like that "Full list of fixed issues

Re: IGNITE-2294 implementation details

Sergi, OK, all fixed, there's no trace of update operations in public API now, thanks. Will update doc and issue shortly. - Alex 2016-08-04 12:32 GMT+03:00 Sergi Vladykin : > Ok, it is not a problem for us if we will not fail fast on wrong number > of arguments, but

[GitHub] ignite pull request #757: Docker image for Ignite 1.6.0

Github user zshamrock closed the pull request at: https://github.com/apache/ignite/pull/757 --- 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

Re: IGNITE-1192 Implementation (Integration with Spring Data)

I have looked at Querydsl and QbE and I think their support should be postponed.

[GitHub] ignite pull request #923: IGNITE-3625 IGFS: Use common naming for IGFS meta ...

GitHub user tledkov-gridgain opened a pull request: https://github.com/apache/ignite/pull/923 IGNITE-3625 IGFS: Use common naming for IGFS meta and data caches You can merge this pull request into a Git repository by running: $ git pull

IGNITE-1192 Implementation (Integration with Spring Data)

Guys, greetings! I am working on Spring Data integration. There are two ways how we can use Spring Data: 1. generating layer for Ignite usage; 2. using existing Spring Data configuration for persistence (Spring Data JPA, for example, or Mongo). I am sure that we should concentrate on first part

[jira] [Created] (IGNITE-3629) Web Console: Implement test for backend API routes

Maxim Afanasiev created IGNITE-3629: --- Summary: Web Console: Implement test for backend API routes Key: IGNITE-3629 URL: https://issues.apache.org/jira/browse/IGNITE-3629 Project: Ignite

[jira] [Created] (IGNITE-3628) ODBC: Improve data fetching performance.

Igor Sapego created IGNITE-3628: --- Summary: ODBC: Improve data fetching performance. Key: IGNITE-3628 URL: https://issues.apache.org/jira/browse/IGNITE-3628 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-3627) ODBC: Tune ODBC capabilities to match capabilities of the Ignite SQL.

Igor Sapego created IGNITE-3627: --- Summary: ODBC: Tune ODBC capabilities to match capabilities of the Ignite SQL. Key: IGNITE-3627 URL: https://issues.apache.org/jira/browse/IGNITE-3627 Project: Ignite

Re: IGNITE-2294 implementation details

Ok, it is not a problem for us if we will not fail fast on wrong number of arguments, but will fail on the first query execution. Lets just drop this argument counting. We should not show SqlFieldsQuery.isQuery on public API if it is useless for the end users. If this stuff is needed for Jdbc we

[jira] [Created] (IGNITE-3626) ODBC: Performance drop when connecting to Ignite with Tableau on Windows.

Igor Sapego created IGNITE-3626: --- Summary: ODBC: Performance drop when connecting to Ignite with Tableau on Windows. Key: IGNITE-3626 URL: https://issues.apache.org/jira/browse/IGNITE-3626 Project:

Re: IGNITE-2294 implementation details

Sergi, > Why do we need to count query arguments? Can anyone clarify? Say, to make parameter index checks early like all major vendors do. That's why they are counted now. > Also about new public APIs. I don't see why we need SqlFieldsQuery.isQuery, > looks like it has to be optional, so it will

Re: ignite-2310

Guys, Please review the last version of the public API https://issues.apache.org/jira/browse/IGNITE-2310?focusedCommentId=15407375=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15407375 Ambiguity will be fixed on the client side. Tests has been fixed. On 11.07.2016

Re: IGNITE-2294 implementation details

About new public APIs 2. QueryCursor.isResultSet makes sense only for SqlFieldsQuery only in Jdbc. Thus it must be private on QueryCursorEx like fieldsMeta() for example. All in all, there should be no changes on public API at this point. Sergi 2016-08-04 9:05 GMT+03:00 Sergi Vladykin

[GitHub] ignite pull request #918: IGNITE-3359 .NET: Implement IgniteConfiguration.To...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/918 --- 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

Re: IGNITE-2294 implementation details

Also about new public APIs. I don't see why we need SqlFieldsQuery.isQuery, looks like it has to be optional, so it will only confuse users. Sergi 2016-08-04 9:00 GMT+03:00 Sergi Vladykin : > Why do we need to count query arguments? Can anyone clarify? > > Sergi > >

Re: IGNITE-2294 implementation details

Why do we need to count query arguments? Can anyone clarify? Sergi 2016-08-04 5:07 GMT+03:00 Alexey Kuznetsov : > About arguments number. I see following options here: > 1. Somehow use H2 engine to parse SQL string and check results. > 2. Use some other parsing library