[jira] [Created] (IGNITE-8626) ODBC: Can not compile ODBC with OpenSSL 1.1

Igor Sapego created IGNITE-8626: --- Summary: ODBC: Can not compile ODBC with OpenSSL 1.1 Key: IGNITE-8626 URL: https://issues.apache.org/jira/browse/IGNITE-8626 Project: Ignite Issue Type: Bug

Re: Node.js Thin Client @ npmjs

Well, all other clients have the same version as Ignite. Are there any reasons to make a Node.js client some kind of a special case? Best Regards, Igor On Thu, May 24, 2018 at 8:21 PM, Dmitriy Setrakyan wrote: > On Thu, May 24, 2018 at 10:03 AM, Pavel Petroshenko

Re: Node.js Thin Client @ npmjs

1. Sounds OK for me. 2. Since Node.js client is going to be included in Ignite releases, I guess it make sense to align its version with the version of Ignite, i.e. 2.6, etc... Best Regards, Igor On Thu, May 24, 2018 at 9:02 AM, Pavel Petroshenko wrote: >

Re: Dose Iginte implement lock and latch in transaction，and where is the code ？

Re-sending to dev-list. Best Regards, Igor On Sat, May 19, 2018 at 6:02 PM, zhouxy1123 wrote: > Dose Iginte implement lock and latch in transaction，and where is the code ？ > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

Re: Apache Ignite 2.4+ Go language client

By the way, Alexandr, Do you want to donate your client to Apache Ignite, so we are going to include it in our release, or would you prefer keep it separate? Best Regards, Igor On Thu, May 10, 2018 at 1:09 PM, Igor Sapego <isap...@apache.org> wrote: > Aleksandr, > I'm curre

Re: Thin clients features wiki page

> platforms/dotnet/Apache.Ignite.Core/Client/IIgniteClient.cs > > On Wed, May 16, 2018 at 12:34 PM, Guru Stron <gurustronpub...@gmail.com> > wrote: > > > Hi Igor, > > > > Nice one! > > > > On 16 May 2018 at 11:26, Igor Sapego <isap...@apache.org> wro

Re: Avoid JIRA comments deletion

I totally agree. There is no sense in most cases in deletion of commentaries. There is even less sense, when you can look into ticket history and see all the removed comments anyway. Best Regards, Igor On Wed, May 16, 2018 at 12:27 PM, Dmitry Pavlov wrote: > Hi

Re: supporting different configuration format json,yaml...

gt; > > are > > > > > to stay with XML if switching to another configuration format > > requires > > > > > significant effort. > > > > > > > > > > BTW, first time I heard about JSON from [1] : " JSON is like XML,

Re: Thin clients features wiki page

t; wrote: > > > Igor, > > > > That's a valid point. Will see how it goes. As for the new documentation > > engine, there are no more arguments. We will try to migrate within 2.6. > > Just need to find more contributors who would help with this. > > > > -- &

Re: supporting different configuration format json,yaml...

kse...@gmail.com> wrote: > Igor, > > Just get one of the config samples and translate it directly to YAML: > XML - https://pastebin.com/wtQXXq8f > YAML - https://pastebin.com/akGu3e81 > > 2018-05-15 18:49 GMT+03:00 Igor Sapego <isap...@apache.org>: > > >

Re: supporting different configuration format json,yaml...

aspect > > > and this task is out of product scope. > > > > > > > > > > > > On Tue, May 15, 2018 at 12:56 PM, Dmitriy Setrakyan > > > <dsetrak...@apache.org> wrote: > > > > I still do not understand *why* do we need to add additi

[jira] [Created] (IGNITE-8495) CPP Thin: Implement thin client start and connection establishment

Igor Sapego created IGNITE-8495: --- Summary: CPP Thin: Implement thin client start and connection establishment Key: IGNITE-8495 URL: https://issues.apache.org/jira/browse/IGNITE-8495 Project: Ignite

[jira] [Created] (IGNITE-8494) CPP Thin: Implement Thin CPP client

Igor Sapego created IGNITE-8494: --- Summary: CPP Thin: Implement Thin CPP client Key: IGNITE-8494 URL: https://issues.apache.org/jira/browse/IGNITE-8494 Project: Ignite Issue Type: New Feature

Re: supporting different configuration format json,yaml...

I don't think we need to add new formats on server side as there may be a lot of different formats for different clients. On the other hand, supporting additional formats may be non trivial and error-prone, while adding little to a user experience. For clients, I see no problem in adding for

Re: Thin clients features wiki page

t; Maybe worth to add type registration functionality: >> - complex object type registration (supported by NodeJS) >> - enum type registration (not supported by NodeJS) >> - type name registration (not supported by NodeJS) >> >> Also, maybe add a list of all type codes,

Thin clients features wiki page

Hello Igniters, I've created a new page in wiki, that summarizes a features availability of thin clients. It should help us to plan development of thin clients while also helping out users to understand a state of clients. Check it out and tell me what you think. And if there are some mistakes,

Re: NodeJS thin client: full API

Alexey, I've checked out the code. Looks good to me. Great job! What about data types support? I can see Timestamp. Are you planning to implement other types, e.g. Decimal, Guid? Best Regards, Igor On Fri, May 11, 2018 at 11:43 AM, Dmitriy Setrakyan wrote: > On Fri,

Re: Apache Ignite 2.4+ Go language client

BSENT > >>> OP_CACHE_GET_ALL > >>> OP_CACHE_PUT_ALL > >>> OP_CACHE_GET_AND_PUT > >>> OP_CACHE_GET_AND_REPLACE > >>> OP_CACHE_GET_AND_REMOVE > >>> OP_CACHE_GET_AND_PUT_IF_ABSENT > >>> OP_CACHE_REPLACE > >>>

Re: Migration guide

Looks like a good idea to me. But I believe, if we decide to adopt this idea, then we need to think how to enforce adding notes to migration guide. The only way I can currently think of is a pretty obvious one - adding corresponding instructions to a wiki [1]. Is there anything else we can do

Re: Apache Ignite 2.5 release

Cool, I've cherry-picked it to ignite-2.5 from master. Best Regards, Igor On Thu, Apr 26, 2018 at 7:48 PM, Andrey Gura <ag...@apache.org> wrote: > Igor, > > Feel free to target ticket to 2.5 release. > > Thanks! > > On Thu, Apr 26, 2018 at 7:45 PM, Igor Sapego <isa

Re: Apache Ignite 2.5 release

Hi guys, I also have fix for a critical bug [1] which I'd like to include in this release. It is OK? [1] - https://issues.apache.org/jira/browse/IGNITE-8394 Best Regards, Igor On Wed, Apr 25, 2018 at 8:19 PM, Andrey Gura wrote: > Pavel, > > looks like painful problem. I've

[jira] [Created] (IGNITE-8394) ODBC: Can not establish SSL connection to remote host.

Igor Sapego created IGNITE-8394: --- Summary: ODBC: Can not establish SSL connection to remote host. Key: IGNITE-8394 URL: https://issues.apache.org/jira/browse/IGNITE-8394 Project: Ignite Issue

Re: Apache Ignite 2.4+ Go language client

Aleksandr, Great job! Do you have any plans on adding new features to your client? Pavel, There are also CacheGet and CachePut [1] operations, as far as I can see. [1] - https://github.com/amsokol/ignite-go-client/blob/master/binary/v1/client.go#L120 Best Regards, Igor On Tue, Apr 24, 2018

Re: Can't run CPP tests locally on linux machine

gt; I removed files you mentioned and got following error messages: > > > > > > > > make[3]: вход в каталог «/home/dragon/src/ignite/ > modules/platforms/cpp/odbc-test» > > > > CXXLDignite-odbc-tests > > > > /usr/lib/gcc/x86_64-linux-gnu/7/../../../

Re: Can't run CPP tests locally on linux machine

gt; boost::unit_test::unit_test_log.set_formatter(new JetBrains:: > TeamcityBoostLogFormatter()); > > Do I need some additional team city library for tets? > Can tests for odbc be executed locally? > > В Ср, 18/04/2018 в 16:29 +0300, Igor Sapego пишет: > > I think it is better to rem

Re: Can't run CPP tests locally on linux machine

OTES? > Should we add some readme to setup development environment for CPP module? > > В Ср, 18/04/2018 в 16:11 +0300, Igor Sapego пишет: > > Hi, Nikolay, > > > > 1. Yes, it's OK; > > 2. Well, it is the old issue that we are working only with the specifi

[jira] [Created] (IGNITE-8310) CPP: Remove strong dependency on Boost 1.58.0

Igor Sapego created IGNITE-8310: --- Summary: CPP: Remove strong dependency on Boost 1.58.0 Key: IGNITE-8310 URL: https://issues.apache.org/jira/browse/IGNITE-8310 Project: Ignite Issue Type

Re: Can't run CPP tests locally on linux machine

Hi, Nikolay, 1. Yes, it's OK; 2. Well, it is the old issue that we are working only with the specific Boost version (1.58.0). You can try commenting out the following line: #include in teamcity_boost.cpp files to make it working with your version. Best Regards, Igor On Wed, Apr 18, 2018 at

Re: affinityRun/Call in C++

the server C++ runtime. > > Hope that all makes sense. I’m happy to contribute to this effort. > > Take care, > Lucas > > -- > Lucas BEELER > Technical Consultant, Professional Services > GridGain Systems > www.gridgain.com > > > On Apr 16, 2018, at 9:02 AM, Igor

Re: affinityRun/Call in C++

t for 2.6 release? It shouldn't be time-consuming to support > it, right? > > -- > Denis > > On Mon, Apr 16, 2018 at 2:48 AM, Igor Sapego <isap...@apache.org> wrote: > > > Guys, > > > > I've created a ticket: [1] > > > > [1] - https://issues

[jira] [Created] (IGNITE-8273) CPP: Implement AffinityRun and AffinityCall Compute methods

Igor Sapego created IGNITE-8273: --- Summary: CPP: Implement AffinityRun and AffinityCall Compute methods Key: IGNITE-8273 URL: https://issues.apache.org/jira/browse/IGNITE-8273 Project: Ignite

Re: affinityRun/Call in C++

Guys, I've created a ticket: [1] [1] - https://issues.apache.org/jira/browse/IGNITE-8273 Best Regards, Igor On Wed, Apr 11, 2018 at 2:44 AM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Is there a ticket? Let's create one if not. > > -Val > > On Tue, Apr 10, 2018 at 6:17 AM,

Re: IGNITE-6879

Hi, Well, Dmitry has said he's going to merge it in 3-4 days 2 days ago, so I guess, the merge is going to happen in 1-2 days or so. Best Regards, Igor On Fri, Apr 6, 2018 at 3:48 PM, Роман Меерсон wrote: > Hi all! > > As i see everything is awesome and there is no

Re: Breaking change in JDBC connection string format

ODBC uses semicolon and this semantics are defined by ODBC specification. Best Regards, Igor On Thu, Apr 5, 2018 at 10:35 PM, Denis Magda wrote: > Vladimir, Igor, > > Shouldn't we do the same for ODBC? > > -- > Denis > > On Thu, Apr 5, 2018 at 5:53 AM, Vladimir Ozerov

[jira] [Created] (IGNITE-8150) Fix suite [Prepare Vote #1] .Net & C++

Igor Sapego created IGNITE-8150: --- Summary: Fix suite [Prepare Vote #1] .Net & C++ Key: IGNITE-8150 URL: https://issues.apache.org/jira/browse/IGNITE-8150 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-8013) CPP: Check pending snapshots in BinaryTypeManager::GetHandler

Igor Sapego created IGNITE-8013: --- Summary: CPP: Check pending snapshots in BinaryTypeManager::GetHandler Key: IGNITE-8013 URL: https://issues.apache.org/jira/browse/IGNITE-8013 Project: Ignite

[jira] [Created] (IGNITE-8012) CPP: BinaryWriter::WriteElement should accept const reference instead of value.

Igor Sapego created IGNITE-8012: --- Summary: CPP: BinaryWriter::WriteElement should accept const reference instead of value. Key: IGNITE-8012 URL: https://issues.apache.org/jira/browse/IGNITE-8012

Re: MTCGA: Tests of the week

Id=73631266 > > > > In 30 clean runs, there was 371 failed tests, 21 suites. During previous > > mass run there were 804 tests including 355 C ++, suites 29. This > indicate > > progress, but still there is a lot of work to be done. > > > > Thanks to Alexey Gonchar

Ignite nightly build job on Apache Jenkins server

Hi Igniters, There is a job on Apache Jenkins for nightly builds of Ignite [1], which was useful for providing fast fixes to our users. However, it seems that noone supports it any more as the last successfull build date is 31.05.2017. Does anyone know what is the issue with the job and why it

Re: .NET Long Running Test execution timeout

In C++ there are no tests that use TcpDiscoveryMulticastIpFinder. There are examples, though, that use it. As far as I know, currently all examples use TcpDiscoveryMulticastIpFinder, and there were some objections against using VmIpFinder instead. Am I right, folks? Best Regards, Igor On Mon,

[jira] [Created] (IGNITE-7825) ODBC: Update specification documentation

Igor Sapego created IGNITE-7825: --- Summary: ODBC: Update specification documentation Key: IGNITE-7825 URL: https://issues.apache.org/jira/browse/IGNITE-7825 Project: Ignite Issue Type: Task

[jira] [Created] (IGNITE-7811) ODBC: Implement connection fail over

Igor Sapego created IGNITE-7811: --- Summary: ODBC: Implement connection fail over Key: IGNITE-7811 URL: https://issues.apache.org/jira/browse/IGNITE-7811 Project: Ignite Issue Type: Bug

Re: Thin client failover mechanism (+ODBC, JDBC)

Well, I agree with Pavel here. To me looks like this feature gives a little to a user, as they need to write all the same amount of code as they would need to if there was no this feature. It also will produce some new issues with the "hanging" of operations, while thin client tries and fails to

Re: SSL for ODBC connection

> Igor, > > Why it might be not enough to have ssl_enabled=[true | false]? Could you > give an example since you’ve already did a research? > > — > Denis > > > On Jan 26, 2018, at 6:08 AM, Igor Sapego <isap...@apache.org> wrote: > > > > Guys, > >

Re: SSL for ODBC connection

org> wrote: > This configuration approach looks clearer to me. +1 for it. > > — > Denis > > > On Nov 20, 2017, at 12:42 AM, Igor Sapego <isap...@apache.org> wrote: > > > > Ok, then how about the following set of options: > > > > ssl

[jira] [Created] (IGNITE-7362) ODBC: Third party libraries truncate any inserted varlen data to ColumnSize

Igor Sapego created IGNITE-7362: --- Summary: ODBC: Third party libraries truncate any inserted varlen data to ColumnSize Key: IGNITE-7362 URL: https://issues.apache.org/jira/browse/IGNITE-7362 Project

Re: Handling slashes in cache names

Also, considering case-insensitivity issue, we need to choose some encoding that only uses upper or lower case letters in encoding result. By the way, such encoding will resolve cache name clashes due to case-insensitivity issue. Best Regards, Igor On Wed, Dec 27, 2017 at 4:18 PM, Igor Sapego

Re: Handling slashes in cache names

I personally like a Pavel's suggestion - base64 encoding seems like a good solution, while string hashes will arise a collision issue. Best Regards, Igor On Wed, Dec 27, 2017 at 3:29 PM, Petr Ivanov wrote: > Special characters banning seems to be exclusive way and cannot

Re: Handling slashes in cache names

There are also some international features that you might want to address. For example, instead of backslash some other characters may be used on Windows - ¥ on the Japanese version, ₩ on the Korean version. See [1] for more info. Here is the citation: Security Considerations for Character Sets

[jira] [Created] (IGNITE-7189) ODBC: ODBC return weird names for tables created with DDL

Igor Sapego created IGNITE-7189: --- Summary: ODBC: ODBC return weird names for tables created with DDL Key: IGNITE-7189 URL: https://issues.apache.org/jira/browse/IGNITE-7189 Project: Ignite

[jira] [Created] (IGNITE-7151) CPP: Get rid of code duplication in JNI library

Igor Sapego created IGNITE-7151: --- Summary: CPP: Get rid of code duplication in JNI library Key: IGNITE-7151 URL: https://issues.apache.org/jira/browse/IGNITE-7151 Project: Ignite Issue Type

[jira] [Created] (IGNITE-7143) CPP: Can not insert zero decimal value with the ODBC driver.

Igor Sapego created IGNITE-7143: --- Summary: CPP: Can not insert zero decimal value with the ODBC driver. Key: IGNITE-7143 URL: https://issues.apache.org/jira/browse/IGNITE-7143 Project: Ignite

Re: Time and scope for Apache Ignite 2.4

Hi Denis, I've been working on SSL support for ODBC [1] for a while now, and I hope to include it in 2.4, as well as some other minor improvements and bug fixes for ODBC. [1] - https://issues.apache.org/jira/browse/IGNITE-6810 Best Regards, Igor On Thu, Dec 7, 2017 at 11:51 AM, vveider

Re: Documentation for GA Grid: GA library to Apache Ignite

It is in a drop-down list that appears when you click on your name, not where you are looking for it. Best Regards, Igor On Sat, Dec 2, 2017 at 1:02 AM, techbysample wrote: > Denis, > > Up on logging in, I do not see the Admin panel that you described. > > I have attached a

Re: SSL for ODBC connection

v 7, 2017 at 10:04 PM, Denis Magda <dma...@apache.org> wrote: > > > Igor, > > > > Thanks for the clarification. Please file a ticket if nobody else shares > a > > feedback soon. > > > > — > > Denis > > > > > On Nov 7, 2017, at 1:23

Re: Problem in Ignite Server When using it with hiredis to Store and retrieve C++ Class Object

Hello, Please, add checks for success of the operations so we can understand what is the problem. Please, check result of serealization, deserialisation, and command sending. Please, also note that this check is not going to work as intended, because size_t is unsigned type:

[jira] [Created] (IGNITE-6841) ODBC: Add new version for multiple result set functionality

Igor Sapego created IGNITE-6841: --- Summary: ODBC: Add new version for multiple result set functionality Key: IGNITE-6841 URL: https://issues.apache.org/jira/browse/IGNITE-6841 Project: Ignite

Re: SSL for ODBC connection

explain the difference between “allow, prefer and require” modes? > > BTW, do we really need to have the “disable” one? Guess that having > ssl_mode set to “disable” will have the same effect as not setting the > ssl_mode at all. > > — > Denis > > > On Nov 3, 2017, a

SSL for ODBC connection

Hi, Igniters, I'm going to start working on the SSL support for the ODBC connection and I need to hear your opinion. For the client side I'm going to use OpenSSL library [1], which is standard de-facto for C/C++ applications. Unfortunately its licence is not fully compatible with Apache Licence,

[jira] [Created] (IGNITE-6810) ODBC: Add secure connection support

Igor Sapego created IGNITE-6810: --- Summary: ODBC: Add secure connection support Key: IGNITE-6810 URL: https://issues.apache.org/jira/browse/IGNITE-6810 Project: Ignite Issue Type: New Feature

Re: [VOTE] Apache Ignite 2.3.0 RC2

+1 1. Building C++ from binary release - OK. 2. Building C++ examples - OK. 3. Building ODBC from binary release - OK. 4. ODBC installers - OK. 5. Building C++ from source release - OK. 6. Building ODBC from source release - OK. Best Regards, Igor On Mon, Oct 30, 2017 at 6:58 AM, Alexey

[jira] [Created] (IGNITE-6765) ODBC: Error when closing executed DML statement.

Igor Sapego created IGNITE-6765: --- Summary: ODBC: Error when closing executed DML statement. Key: IGNITE-6765 URL: https://issues.apache.org/jira/browse/IGNITE-6765 Project: Ignite Issue Type

Re: SQL error codes

Error codes are different for ODBC and JDBC. Best Regards, Igor On Thu, Oct 19, 2017 at 3:23 AM, Denis Magda wrote: > Alex P, Vladimir, > > Please confirm that the error codes documented for JDBC [1] driver are > shared by all SQL APIs we have. If it’s so I would create

Re: Optimized DML execution: how to name it?

Here is the link for the ticket [1] If someone else was wandering about what kind of optimization we are talking. [1] - https://issues.apache.org/jira/browse/IGNITE-6024 Best Regards, Igor On Thu, Oct 12, 2017 at 9:45 AM, Vladimir Ozerov wrote: > Igniters, > > We

OpenSSL licence compatibility

Hi guys, Lately I've been wondering about adding SSL to our ODBC driver. Of course I'm not going to write my own SSL implementation from the scratch, and going to use third-party library for that instead. OpenSSL library is the standard de-facto for implementation of SSL connectivity, but it uses

[jira] [Created] (IGNITE-6594) Add lazy flag to the list of the ODBC connection string attributes.

Igor Sapego created IGNITE-6594: --- Summary: Add lazy flag to the list of the ODBC connection string attributes. Key: IGNITE-6594 URL: https://issues.apache.org/jira/browse/IGNITE-6594 Project: Ignite

[jira] [Created] (IGNITE-6593) Document C and SQL types, supported by ODBC driver.

Igor Sapego created IGNITE-6593: --- Summary: Document C and SQL types, supported by ODBC driver. Key: IGNITE-6593 URL: https://issues.apache.org/jira/browse/IGNITE-6593 Project: Ignite Issue

[jira] [Created] (IGNITE-6592) Describe Ignite C++ pointer reading and writing semantics

Igor Sapego created IGNITE-6592: --- Summary: Describe Ignite C++ pointer reading and writing semantics Key: IGNITE-6592 URL: https://issues.apache.org/jira/browse/IGNITE-6592 Project: Ignite

[jira] [Created] (IGNITE-6468) ODBC: Add tests for SQLGetInfo

Igor Sapego created IGNITE-6468: --- Summary: ODBC: Add tests for SQLGetInfo Key: IGNITE-6468 URL: https://issues.apache.org/jira/browse/IGNITE-6468 Project: Ignite Issue Type: Improvement

Re: Disabling ODBC/thin JDBC/thin .NET connectivity

p 20, 2017 at 5:26 AM, Igor Sapego <isap...@apache.org> wrote: > > > I've filed a ticket for that: [1] > > > > [1] - https://issues.apache.org/jira/browse/IGNITE-6456 > > > > Best Regards, > > Igor > > > > On Wed, Sep 20, 2017 at 2:33 PM, Vladi

[jira] [Created] (IGNITE-6456) Add flags to ClientConnectorConfiguration which enable/disable different clients

Igor Sapego created IGNITE-6456: --- Summary: Add flags to ClientConnectorConfiguration which enable/disable different clients Key: IGNITE-6456 URL: https://issues.apache.org/jira/browse/IGNITE-6456

Re: Disabling ODBC/thin JDBC/thin .NET connectivity

t; > > This way users will also have better understanding of the > > ClientConnectorConfiguration purpose. > > > > Pavel > > > > On Wed, Sep 20, 2017 at 1:12 PM, Igor Sapego <isap...@apache.org> wrote: > > > > > Hi, Igniters, > > > > > > In current approac

[jira] [Created] (IGNITE-6455) Add flags to ClientConnectorConfiguration which enable/disable different clients

Igor Sapego created IGNITE-6455: --- Summary: Add flags to ClientConnectorConfiguration which enable/disable different clients Key: IGNITE-6455 URL: https://issues.apache.org/jira/browse/IGNITE-6455

Disabling ODBC/thin JDBC/thin .NET connectivity

Hi, Igniters, In current approach, ODBC, thin JDBC and thin .NET client all connect to the grid using ClientListenerProcessor, which listen on a single port. The problem is that there is currently no way to disable only one client. For example, currently you can't disallow thin JDBC driver

Re: [VOTE] Apache Ignite 2.2.0 RC1

Wait, there is no platforms\cpp\bin directory with odbc installers in binary release. Can someone double-check? Best Regards, Igor On Tue, Sep 12, 2017 at 7:44 PM, Igor Sapego <isap...@apache.org> wrote: > +1 > > Checked: > - Building of x86 and amd64 versions of C++ bina

Re: [VOTE] Apache Ignite 2.2.0 RC1

+1 Checked: - Building of x86 and amd64 versions of C++ binaries. - Building of x86 and amd64 versions of ODBC. - C++ examples. Best Regards, Igor On Tue, Sep 12, 2017 at 6:16 PM, Andrey Gura wrote: > +1 > > On Tue, Sep 12, 2017 at 6:09 PM, Kozlov Maxim

Re: [DISCUSSION] Urgent Ignite bug fix release

Igniters, There is one more fix I would propose to include into 2.2: [1]. It has been fixed a while ago and it is critical for C++ users that would like to make use of persistence store, as currently they need to have separate Java node just to activate cluster. What do you think? [1] -

[jira] [Created] (IGNITE-6211) ODBC: SQLBindParameter should not unbind parameter if the ParameterValuePtr is NULL

Igor Sapego created IGNITE-6211: --- Summary: ODBC: SQLBindParameter should not unbind parameter if the ParameterValuePtr is NULL Key: IGNITE-6211 URL: https://issues.apache.org/jira/browse/IGNITE-6211

[jira] [Created] (IGNITE-6188) ODBC: SQLSQLFreeStmt failing if called before all the rows from the result set were fetched.

Igor Sapego created IGNITE-6188: --- Summary: ODBC: SQLSQLFreeStmt failing if called before all the rows from the result set were fetched. Key: IGNITE-6188 URL: https://issues.apache.org/jira/browse/IGNITE-6188

[jira] [Created] (IGNITE-6162) ODBC: Implement support for multiple result sets

Igor Sapego created IGNITE-6162: --- Summary: ODBC: Implement support for multiple result sets Key: IGNITE-6162 URL: https://issues.apache.org/jira/browse/IGNITE-6162 Project: Ignite Issue Type

[jira] [Created] (IGNITE-6159) ODBC: Implement SQLStatistics

Igor Sapego created IGNITE-6159: --- Summary: ODBC: Implement SQLStatistics Key: IGNITE-6159 URL: https://issues.apache.org/jira/browse/IGNITE-6159 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-6158) ODBC: Implement proper support of SQLPrimaryKeys

Igor Sapego created IGNITE-6158: --- Summary: ODBC: Implement proper support of SQLPrimaryKeys Key: IGNITE-6158 URL: https://issues.apache.org/jira/browse/IGNITE-6158 Project: Ignite Issue Type

[jira] [Created] (IGNITE-6156) ODBC: Implement SQL_ATTR_QUERY_TIMEOUT statement attribute

Igor Sapego created IGNITE-6156: --- Summary: ODBC: Implement SQL_ATTR_QUERY_TIMEOUT statement attribute Key: IGNITE-6156 URL: https://issues.apache.org/jira/browse/IGNITE-6156 Project: Ignite

[jira] [Created] (IGNITE-6153) ODBC: Implement SQLCancel

Igor Sapego created IGNITE-6153: --- Summary: ODBC: Implement SQLCancel Key: IGNITE-6153 URL: https://issues.apache.org/jira/browse/IGNITE-6153 Project: Ignite Issue Type: Improvement

[jira] [Created] (IGNITE-6151) ODBC: Implement SQL_ATTR_CONNECTION_DEAD connection attribute

Igor Sapego created IGNITE-6151: --- Summary: ODBC: Implement SQL_ATTR_CONNECTION_DEAD connection attribute Key: IGNITE-6151 URL: https://issues.apache.org/jira/browse/IGNITE-6151 Project: Ignite

Re: SQL Getting Started Guide

RN ret = SQLExecDirect(stmt, query, queryLen); > > > On Fri, Aug 18, 2017 at 12:09 PM, Denis Magda <dma...@apache.org> wrote: > > > Igor, thanks a lot. Appreciate this! > > > > — > > Denis > > > > > On Aug 18, 2017, at 8:56 AM, Igor Sapego &l

Re: SQL Getting Started Guide

ironment is set up on your side. > > — > Denis > > > On Aug 17, 2017, at 5:37 AM, Igor Sapego <isap...@apache.org> wrote: > > > > Akmal, > > > > I work on the ODBC driver and would be glad to help. You can send > > mails with your requests to d

Re: ODBC doc needs to be updated

Denis, Ok, I've filed a ticket [1] and will take a look. [1] - https://issues.apache.org/jira/browse/IGNITE-6112 Best Regards, Igor On Fri, Aug 18, 2017 at 3:19 AM, Dmitriy Setrakyan wrote: > Denis, it will be helpful to also file a ticket on this. > > On Thu, Aug 17,

[jira] [Created] (IGNITE-6112) Review and update C++ documentation according to new features.

Igor Sapego created IGNITE-6112: --- Summary: Review and update C++ documentation according to new features. Key: IGNITE-6112 URL: https://issues.apache.org/jira/browse/IGNITE-6112 Project: Ignite

[jira] [Created] (IGNITE-6099) ODBC: Implement SQLGetInfo for all info types

Igor Sapego created IGNITE-6099: --- Summary: ODBC: Implement SQLGetInfo for all info types Key: IGNITE-6099 URL: https://issues.apache.org/jira/browse/IGNITE-6099 Project: Ignite Issue Type

Re: SQL Getting Started Guide

Akmal, I work on the ODBC driver and would be glad to help. You can send mails with your requests to devlist and I will try to help as much as I can. Best Regards, Igor On Thu, Aug 17, 2017 at 3:28 PM, Akmal Chaudhri wrote: > When I have the opportunity to test

[jira] [Created] (IGNITE-6081) .NET: Cannot get from cache values which were stored in cache with PutAll.

Igor Sapego created IGNITE-6081: --- Summary: .NET: Cannot get from cache values which were stored in cache with PutAll. Key: IGNITE-6081 URL: https://issues.apache.org/jira/browse/IGNITE-6081 Project

[jira] [Created] (IGNITE-6032) ODBC: SQLGetData should return SQL_SUCCESS if called on NULL column

Igor Sapego created IGNITE-6032: --- Summary: ODBC: SQLGetData should return SQL_SUCCESS if called on NULL column Key: IGNITE-6032 URL: https://issues.apache.org/jira/browse/IGNITE-6032 Project: Ignite

[jira] [Created] (IGNITE-5995) ODBC: SQLGetData gets data for the next row instead of current

Igor Sapego created IGNITE-5995: --- Summary: ODBC: SQLGetData gets data for the next row instead of current Key: IGNITE-5995 URL: https://issues.apache.org/jira/browse/IGNITE-5995 Project: Ignite

Re: ODBC API conformance page updated

e plans to get closer to 100% compliance? > > D. > > On Fri, Aug 4, 2017 at 1:08 PM, Vladimir Ozerov <voze...@gridgain.com> > wrote: > > > Igor, > > > > Vary cool! > > > > On Fri, Aug 4, 2017 at 1:15 PM, Igor Sapego <isap...@apache.org> wrote: >

ODBC API conformance page updated

Hi Igniters, I've updated an ODBC API conformance page - [1], so take a look if you are interested. Also, make sure you edit this page if you are adding new features, or modifying existing features of the Ignite ODBC driver. [1] - https://apacheignite.readme.io/v2.1/docs/conformance Best

[jira] [Created] (IGNITE-5923) ODBC: SQLGetTypeInfo does not work with SQL_ALL_TYPES

Igor Sapego created IGNITE-5923: --- Summary: ODBC: SQLGetTypeInfo does not work with SQL_ALL_TYPES Key: IGNITE-5923 URL: https://issues.apache.org/jira/browse/IGNITE-5923 Project: Ignite Issue

[jira] [Created] (IGNITE-5900) CPP: Add tests for CREATE/DROP table/index for C++ and ODBC

Igor Sapego created IGNITE-5900: --- Summary: CPP: Add tests for CREATE/DROP table/index for C++ and ODBC Key: IGNITE-5900 URL: https://issues.apache.org/jira/browse/IGNITE-5900 Project: Ignite

Re: Non-UTF-8 string encoding support in BinaryMarshaller (IGNITE-5655)

itriy Setrakyan <dsetrak...@apache.org> wrote: > On Thu, Jul 27, 2017 at 9:04 AM, Igor Sapego <isap...@apache.org> wrote: > > > Just a note from the platforms guy: > > > > Solution with table-level configuration is going to be significantly > > harder

Re: Non-UTF-8 string encoding support in BinaryMarshaller (IGNITE-5655)

Just a note from the platforms guy: Solution with table-level configuration is going to be significantly harder to implement for platforms and ODBC then field-level one. Also, what about binary objects, which are not stored in cache, but being marshalled? Best Regards, Igor On Wed, Jul 26,

<    1   2   3   4   5   6   7   >