Hi,

You can use nightly builds [1] as an option.

[1] -
https://ci.ignite.apache.org/project.html?projectId=Releases_NightlyRelease

Best Regards,
Igor


On Fri, Jul 13, 2018 at 11:58 AM Som Som <[email protected]> wrote:

> hi. yes, that's it.
>
> when is the new release with the fix planned? or how can get a fixed
> version of driver?
>
> 13 июл. 2018 г. 10:20 ДП пользователь "Pavel Vinokurov" <
> [email protected]> написал:
>
> Hi,
>
> Probably this issue relates to
> https://issues.apache.org/jira/browse/IGNITE-8838
>
> Thanks,
> Pavel
>
> 2018-07-12 15:36 GMT+03:00 Som Som <[email protected]>:
>
>> 2.5.0
>>
>> чт, 12 июл. 2018 г., 12:47 Igor Sapego <[email protected]>:
>>
>>> Hello,
>>>
>>> What is the Ignite version you are using?
>>>
>>> Best Regards,
>>> Igor
>>>
>>>
>>> On Wed, Jul 11, 2018 at 7:47 PM Som Som <[email protected]> wrote:
>>>
>>>> There is a system ("DS") which publishes data into MS db via odbc and *it
>>>> works without any problems*.
>>>>
>>>> So i created cache instead of MS db table “T”, then as a test i
>>>> connected via DBeaver and inserted test row and there was no problem. Next
>>>> i installed ignite odbc driver and created dsn, but when i tryed to publish
>>>> data from data "DS" only one row was inserted into the table and  i saw
>>>> errors in "DS" log file: “Error: SQL Error DBTable ‘T’ DB ODBC error: Query
>>>> cursor is in open state already.”
>>>>
>>>>
>>>>
>>>> Cache was created with the following code:
>>>>
>>>>
>>>>
>>>> var cache = ignite.GetOrCreateCache<TKey, T>(
>>>>
>>>>                 new CacheConfiguration
>>>>
>>>>                 {
>>>>
>>>>                     SqlSchema = "PUBLIC",
>>>>
>>>>                     Name = "T",
>>>>
>>>>                     WriteSynchronizationMode =
>>>> CacheWriteSynchronizationMode.FullAsync,
>>>>
>>>>                     QueryEntities = new[] { newQueryEntity(typeof
>>>> (TKey), typeof(T)) }
>>>>
>>>>                 });
>>>>
>>>>
>>>>
>>>> What could be the problem?
>>>>
>>>
>
>
> --
>
> Regards
>
> Pavel Vinokurov
>
>
>

Reply via email to