Re: IGNITE-4155 IgniteSemaphoreExample unexpected behavior

Hi Sergey, can you please provide more information? Have you changed the example (if so, can you provide the changes you made?) Is the example executed normally (without node failures)? In the example, semaphore is created in non-failover safe mode, which means it is not safe to use it once it

[GitHub] ignite pull request #1219: ignite-3812

GitHub user akuramshingg opened a pull request: https://github.com/apache/ignite/pull/1219 ignite-3812 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3812 Alternatively you can review and apply

[jira] [Created] (IGNITE-4198) Ignite Kafka sink connector should have an option to transform Kafka values

Roman Shtykh created IGNITE-4198: Summary: Ignite Kafka sink connector should have an option to transform Kafka values Key: IGNITE-4198 URL: https://issues.apache.org/jira/browse/IGNITE-4198 Project:

Re: Apache Ignite 1.8 Release

Current status on DML: - Basic data streamer support implemented (basicness is mostly about configuration - say, currently there's no way to specify streamer's batch size via JDBC driver, but this can be improved easily). - Fixed all minor stuff agreed with Vladimir. - There are some tests that

[jira] [Created] (IGNITE-4197) Rework UPDATE and DELETE in more streaming friendly manner

Alexander Paschenko created IGNITE-4197: --- Summary: Rework UPDATE and DELETE in more streaming friendly manner Key: IGNITE-4197 URL: https://issues.apache.org/jira/browse/IGNITE-4197 Project:

Re: Connecting to Ignite from Tableau

I do agree, though, that we should have a separate page for Tableau documentation. On Tue, Nov 8, 2016 at 10:53 AM, Denis Magda wrote: > I’m planning to put PHP PDO documentation under kind of “Runs Everywhere” > section. Under this section you will be able to find a

Re: TX savepoints

Agree. On Tue, Nov 8, 2016 at 12:38 PM, Sergi Vladykin wrote: > > > > I see your point, but why not add the SQL commands right now and support > > transactions in the same way we support them in the project? > > > > It means that we will support TXs only for direct SQL

[jira] [Created] (IGNITE-4196) H2 debug console is always started on artificial port

Valentin Kulichenko created IGNITE-4196: --- Summary: H2 debug console is always started on artificial port Key: IGNITE-4196 URL: https://issues.apache.org/jira/browse/IGNITE-4196 Project: Ignite

[jira] [Created] (IGNITE-4195) rest-http can't get data if key is Integer or others

Victor.x.qu created IGNITE-4195: --- Summary: rest-http can't get data if key is Integer or others Key: IGNITE-4195 URL: https://issues.apache.org/jira/browse/IGNITE-4195 Project: Ignite Issue

Re: TX savepoints

> > I see your point, but why not add the SQL commands right now and support > transactions in the same way we support them in the project? > It means that we will support TXs only for direct SQL mappings for cache commands: INSERT (putIfAbsent), MERGE by primary key (put) and DELETE by primary

Re: TX savepoints

On Tue, Nov 8, 2016 at 11:51 AM, Sergi Vladykin wrote: > Dmitriy, > > I don't see how we can support it without having all the complex MVCC > machinery that we are creating for 2.0 (and it is very far from being > ready). > I see your point, but why not add the SQL

[jira] [Created] (IGNITE-4193) ODBC: transactional support for DML and SELECT statements

Denis Magda created IGNITE-4193: --- Summary: ODBC: transactional support for DML and SELECT statements Key: IGNITE-4193 URL: https://issues.apache.org/jira/browse/IGNITE-4193 Project: Ignite

[jira] [Created] (IGNITE-4192) JDBC: transactional support for DML and SELECT statements

Denis Magda created IGNITE-4192: --- Summary: JDBC: transactional support for DML and SELECT statements Key: IGNITE-4192 URL: https://issues.apache.org/jira/browse/IGNITE-4192 Project: Ignite

[jira] [Created] (IGNITE-4191) Transactional support at the level of Ignite drivers and DML

Denis Magda created IGNITE-4191: --- Summary: Transactional support at the level of Ignite drivers and DML Key: IGNITE-4191 URL: https://issues.apache.org/jira/browse/IGNITE-4191 Project: Ignite

Re: TX savepoints

Dmitriy, I don't see how we can support it without having all the complex MVCC machinery that we are creating for 2.0 (and it is very far from being ready). Sergi 2016-11-08 20:38 GMT+03:00 Dmitriy Setrakyan : > I am not sure why we don't add the transaction support now,

Re: TX savepoints

I’ve wrapped up the outcomes of the discussion and created JIRA tickets https://issues.apache.org/jira/browse/IGNITE-4188 Sergi, do we already have a ticket created for >> All the SQL statements currently run out of transactions. It is a big

[jira] [Created] (IGNITE-4190) ODBC Driver: support transactional savepoints

Denis Magda created IGNITE-4190: --- Summary: ODBC Driver: support transactional savepoints Key: IGNITE-4190 URL: https://issues.apache.org/jira/browse/IGNITE-4190 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-4189) JDBC Driver: Support transactional savepoints

Denis Magda created IGNITE-4189: --- Summary: JDBC Driver: Support transactional savepoints Key: IGNITE-4189 URL: https://issues.apache.org/jira/browse/IGNITE-4189 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-4188) Savepoints support inside of Ignite Transactions

Denis Magda created IGNITE-4188: --- Summary: Savepoints support inside of Ignite Transactions Key: IGNITE-4188 URL: https://issues.apache.org/jira/browse/IGNITE-4188 Project: Ignite Issue Type:

Re: Connecting to Ignite from Tableau

I’m planning to put PHP PDO documentation under kind of “Runs Everywhere” section. Under this section you will be able to find a reference to our .NET, C++ client docs as well as information about REST API. Tableau should be added under the new “Tools Integrations” section. Could you create a

Re: TX savepoints

I am not sure why we don't add the transaction support now, given that we are going to support insert, update, and delete statements. On Tue, Nov 8, 2016 at 4:50 AM, Sergi Vladykin wrote: > All the SQL statements currently run out of transactions. It is a big > feature

[jira] [Created] (IGNITE-4187) "Remote node ID is not as expected" when client SSL certificate is signed by untrusted CA

Ksenia Rybakova created IGNITE-4187: --- Summary: "Remote node ID is not as expected" when client SSL certificate is signed by untrusted CA Key: IGNITE-4187 URL: https://issues.apache.org/jira/browse/IGNITE-4187

[jira] [Created] (IGNITE-4186) .NET: "Invalid session release request" exception in IgniteSessionStateStoreProvider.SetAndReleaseItemExclusive

Ksenia Rybakova created IGNITE-4186: --- Summary: .NET: "Invalid session release request" exception in IgniteSessionStateStoreProvider.SetAndReleaseItemExclusive Key: IGNITE-4186 URL:

[GitHub] ignite pull request #1218: IGNITE-4145: "No query result found for request" ...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1218 IGNITE-4145: "No query result found for request" exception when running multiple queries concurrently.Fixed Race condition has fixed. You can merge this pull request into a Git repository by

[GitHub] ignite pull request #1217: IGNITE-4120: Deadlock Detection Example

GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1217 IGNITE-4120: Deadlock Detection Example You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4120 Alternatively

Re: TX savepoints

Denis, As far as I know, there is no support for savepoints in ODBC API. ODBC drivers which implement it just detect "SAVEPOINT" keyword in query to implement this kind of functionality. Best Regards, Igor On Tue, Nov 8, 2016 at 3:50 PM, Sergi Vladykin wrote: > All

Re: TX savepoints

All the SQL statements currently run out of transactions. It is a big feature for 2.0 Sergi 2016-11-08 15:09 GMT+03:00 Igor Sapego : > Hi, > > Currently, we do not support transaction in ODBC at all. I'm not quite sure > about JDBC, but I believe we do not support them

[jira] [Created] (IGNITE-4185) Apache.Ignite.AspNet.IgniteOutputCacheProvider: System.NullReferenceException when igniteConfiguration is missed

Ksenia Rybakova created IGNITE-4185: --- Summary: Apache.Ignite.AspNet.IgniteOutputCacheProvider: System.NullReferenceException when igniteConfiguration is missed Key: IGNITE-4185 URL:

Re: Connecting to Ignite from Tableau

Maybe we should have a page with notes for any widespread product which we tested with Ignite. We going to have a page for PDO soon so why not to make a page for Tableau? Best Regards, Igor On Tue, Nov 8, 2016 at 12:02 PM, Dmitriy Setrakyan wrote: > I think we should

Re: ODBC processor default behaviour

Denis, Good point. I'll do that. Best Regards, Igor On Tue, Nov 8, 2016 at 1:42 AM, Denis Magda wrote: > Thanks to this old discussion I was finally able to form an understanding > on how Ignite ODBC driver connects to the cluster and executes SQL queries > over it. > >

[GitHub] ignite pull request #1215: IGNITE-4175: SQL: JdbcResultSet class wasNull() m...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1215 IGNITE-4175: SQL: JdbcResultSet class wasNull() method should return true on NULL fields Trivial fix. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1216: IGNITE-4175: SQL: JdbcResultSet class wasNull() m...

GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/1216 IGNITE-4175: SQL: JdbcResultSet class wasNull() method should return true on NULL fields Trivial fix. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1215: IGNITE-4175: SQL: JdbcResultSet class wasNull() m...

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

[GitHub] ignite pull request #1210: IGNITE-4175: SQL: JdbcResultSet class wasNull() m...

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

IGNITE-4155 IgniteSemaphoreExample unexpected behavior

Hello folks, I found a reason why *IgniteSemaphoreExample* hangs when started twice without restarting a cluster; and it doesn't seem minor to me anymore. >From here I'm going to refer to example's code so please have it opened. So, when the first instance of node running example code finishes

Re: Connecting to Ignite from Tableau

I think we should have minimal documentation about Tableu, describing the steps, and a screenshot. Even though it seems trivial to us, it will not be as trivial to users. On Mon, Nov 7, 2016 at 10:51 PM, Vladimir Ozerov wrote: > Denis, > > I am not sure it requires