[jira] [Updated] (IGNITE-1588) CPP: Fix constructor of the IgniteJvmOption class
[
https://issues.apache.org/jira/browse/IGNITE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-1588:
Affects Version/s: 1.1.4
> CPP: Fix constructor of the IgniteJvmOption class
> -
>
> Key: IGNITE-1588
> URL: https://issues.apache.org/jira/browse/IGNITE-1588
> Project: Ignite
> Issue Type: Task
> Components: interop
>Affects Versions: 1.1.4
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>
> Current implementation of the IgniteJvmOption class takes {{char*}} as
> argument, when it should take {{const char*}} and copy it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1588) CPP: Fix constructor of the IgniteJvmOption class
Igor Sapego created IGNITE-1588:
---
Summary: CPP: Fix constructor of the IgniteJvmOption class
Key: IGNITE-1588
URL: https://issues.apache.org/jira/browse/IGNITE-1588
Project: Ignite
Issue Type: Task
Reporter: Igor Sapego
Assignee: Igor Sapego
Current implementation of the IgniteJvmOption class takes {{char*}} as
argument, when it should take {{const char*}} and copy it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1588) CPP: Fix constructor of the IgniteJvmOption class
[
https://issues.apache.org/jira/browse/IGNITE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-1588:
Component/s: interop
> CPP: Fix constructor of the IgniteJvmOption class
> -
>
> Key: IGNITE-1588
> URL: https://issues.apache.org/jira/browse/IGNITE-1588
> Project: Ignite
> Issue Type: Task
> Components: interop
>Affects Versions: 1.1.4
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>
> Current implementation of the IgniteJvmOption class takes {{char*}} as
> argument, when it should take {{const char*}} and copy it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-1588) CPP: Fix constructor of the IgniteJvmOption class
[
https://issues.apache.org/jira/browse/IGNITE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego reassigned IGNITE-1588:
---
Assignee: Igor Sapego (was: Vladimir Ozerov)
> CPP: Fix constructor of the IgniteJvmOption class
> -
>
> Key: IGNITE-1588
> URL: https://issues.apache.org/jira/browse/IGNITE-1588
> Project: Ignite
> Issue Type: Task
> Components: interop
>Affects Versions: 1.1.4
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>
> Current implementation of the IgniteJvmOption class takes {{char*}} as
> argument, when it should take {{const char*}} and copy it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1588) CPP: Fix constructor of the IgniteJvmOption class
[
https://issues.apache.org/jira/browse/IGNITE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939782#comment-14939782
]
Igor Sapego commented on IGNITE-1588:
-
Vladimir,
Fixed.
> CPP: Fix constructor of the IgniteJvmOption class
> -
>
> Key: IGNITE-1588
> URL: https://issues.apache.org/jira/browse/IGNITE-1588
> Project: Ignite
> Issue Type: Task
> Components: interop
>Affects Versions: 1.1.4
>Reporter: Igor Sapego
>Assignee: Vladimir Ozerov
>
> Current implementation of the IgniteJvmOption class takes {{char*}} as
> argument, when it should take {{const char*}} and copy it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-1454) CPP: Review all std:: usages in public API.
[ https://issues.apache.org/jira/browse/IGNITE-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-1454: --- Assignee: Igor Sapego > CPP: Review all std:: usages in public API. > --- > > Key: IGNITE-1454 > URL: https://issues.apache.org/jira/browse/IGNITE-1454 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Igor Sapego >Priority: Critical > Fix For: ignite-1.5 > > > 1) All std:: usages in public API must reside in headers. > 2) Consider getting rid of char* and use std::string instead in public API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1454) CPP: Review all std:: usages in public API.
[ https://issues.apache.org/jira/browse/IGNITE-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941058#comment-14941058 ] Igor Sapego commented on IGNITE-1454: - 1. It seems like a good idea to replace standard library containers with iterators. This way we can make our API more agile and avoid some dependencies on the standard library. 2. Lets move string type issue in separate ticket. > CPP: Review all std:: usages in public API. > --- > > Key: IGNITE-1454 > URL: https://issues.apache.org/jira/browse/IGNITE-1454 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Igor Sapego >Priority: Critical > Fix For: ignite-1.5 > > > 1) All std:: usages in public API must reside in headers. > 2) Consider getting rid of char* and use std::string instead in public API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-1454) CPP: Review all std:: usages in public API.
[ https://issues.apache.org/jira/browse/IGNITE-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego closed IGNITE-1454. --- > CPP: Review all std:: usages in public API. > --- > > Key: IGNITE-1454 > URL: https://issues.apache.org/jira/browse/IGNITE-1454 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Igor Sapego >Priority: Critical > Fix For: ignite-1.5 > > > 1) All std:: usages in public API must reside in headers. > 2) Consider getting rid of char* and use std::string instead in public API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1454) CPP: Review all std:: usages in public API.
[ https://issues.apache.org/jira/browse/IGNITE-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego resolved IGNITE-1454. - Resolution: Fixed > CPP: Review all std:: usages in public API. > --- > > Key: IGNITE-1454 > URL: https://issues.apache.org/jira/browse/IGNITE-1454 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Igor Sapego >Priority: Critical > Fix For: ignite-1.5 > > > 1) All std:: usages in public API must reside in headers. > 2) Consider getting rid of char* and use std::string instead in public API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1610) CPP: Implement reader and writer for iterators
Igor Sapego created IGNITE-1610: --- Summary: CPP: Implement reader and writer for iterators Key: IGNITE-1610 URL: https://issues.apache.org/jira/browse/IGNITE-1610 Project: Ignite Issue Type: Task Components: interop Affects Versions: 1.1.4 Reporter: Igor Sapego Assignee: Igor Sapego Need to try and implement portable writer and portable reader that could work with iterators. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1617) CPP: review string usage in public API
[ https://issues.apache.org/jira/browse/IGNITE-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1617: Affects Version/s: 1.1.4 > CPP: review string usage in public API > --- > > Key: IGNITE-1617 > URL: https://issues.apache.org/jira/browse/IGNITE-1617 > Project: Ignite > Issue Type: Task >Affects Versions: 1.1.4 >Reporter: Igor Sapego >Assignee: Igor Sapego > > Currently there is std::string type used in some parts of public API while > const char* used in some other parts. Need to review API and suggest solution > for the consistent string policy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1617) CPP: review string usage in public API
Igor Sapego created IGNITE-1617: --- Summary: CPP: review string usage in public API Key: IGNITE-1617 URL: https://issues.apache.org/jira/browse/IGNITE-1617 Project: Ignite Issue Type: Task Reporter: Igor Sapego Assignee: Igor Sapego Currently there is std::string type used in some parts of public API while const char* used in some other parts. Need to review API and suggest solution for the consistent string policy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1617) CPP: review string usage in public API
[ https://issues.apache.org/jira/browse/IGNITE-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943428#comment-14943428 ] Igor Sapego commented on IGNITE-1617: - String policy by classes is represented by the table below. ||Class||Current string policy|| |SqlQuery|std::string| |TextQuery|std::string| |Cache|char*| |Portable|char* with std::string overloads| |PortableStringArrayWriter|char* with std::string overloads| |PortableStringArrayReader|char* with std::string overloads| |PortableRawReader|char* with std::string overloads| |PortableRawWriter|char* with std::string overloads| |PortableReader|char* with std::string overloads but some args are only char*| |PortableWriter|char* with std::string overloads but some args are only char*| |PortableType|char*| |Ignite|char*| |IgniteJvmOption|char*| |IgniteConfiguration|very dangerous usage of char*| |IgniteError|char*| |Ignition|char*| > CPP: review string usage in public API > --- > > Key: IGNITE-1617 > URL: https://issues.apache.org/jira/browse/IGNITE-1617 > Project: Ignite > Issue Type: Task >Affects Versions: 1.1.4 >Reporter: Igor Sapego >Assignee: Igor Sapego > > Currently there is std::string type used in some parts of public API while > const char* used in some other parts. Need to review API and suggest solution > for the consistent string policy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1617) CPP: review string usage in public API
[ https://issues.apache.org/jira/browse/IGNITE-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1617: Assignee: Vladimir Ozerov (was: Igor Sapego) > CPP: review string usage in public API > --- > > Key: IGNITE-1617 > URL: https://issues.apache.org/jira/browse/IGNITE-1617 > Project: Ignite > Issue Type: Task >Affects Versions: 1.1.4 >Reporter: Igor Sapego >Assignee: Vladimir Ozerov > > Currently there is std::string type used in some parts of public API while > const char* used in some other parts. Need to review API and suggest solution > for the consistent string policy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1467) CPP: Create application for standalone node.
[ https://issues.apache.org/jira/browse/IGNITE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-1467: --- Assignee: Igor Sapego > CPP: Create application for standalone node. > - > > Key: IGNITE-1467 > URL: https://issues.apache.org/jira/browse/IGNITE-1467 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Igor Sapego >Priority: Critical > Fix For: ignite-1.5 > > > We need to create executable application to start stadalone CPP node. This > can be done in the same way as we did it for .Net. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1467) CPP: Create application for standalone node.
[ https://issues.apache.org/jira/browse/IGNITE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1467: Assignee: Vladimir Ozerov (was: Igor Sapego) > CPP: Create application for standalone node. > - > > Key: IGNITE-1467 > URL: https://issues.apache.org/jira/browse/IGNITE-1467 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: ignite-1.5 > > > We need to create executable application to start stadalone CPP node. This > can be done in the same way as we did it for .Net. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1617) CPP: review string usage in public API
[ https://issues.apache.org/jira/browse/IGNITE-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948505#comment-14948505 ] Igor Sapego commented on IGNITE-1617: - Vladimir, 1. It seems like there are not so many usages of std::string so It seems to me that there is no reason to remove overloads for std::string from the API. We are not going to remove all of them anyway so why remove part of them? 2. Ignite configuration struct has been made safe in IGNITE-1467. > CPP: review string usage in public API > --- > > Key: IGNITE-1617 > URL: https://issues.apache.org/jira/browse/IGNITE-1617 > Project: Ignite > Issue Type: Task >Affects Versions: 1.1.4 >Reporter: Igor Sapego >Assignee: Igor Sapego > > Currently there is std::string type used in some parts of public API while > const char* used in some other parts. Need to review API and suggest solution > for the consistent string policy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1617) CPP: review string usage in public API
[ https://issues.apache.org/jira/browse/IGNITE-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1617: Assignee: Vladimir Ozerov (was: Igor Sapego) > CPP: review string usage in public API > --- > > Key: IGNITE-1617 > URL: https://issues.apache.org/jira/browse/IGNITE-1617 > Project: Ignite > Issue Type: Task >Affects Versions: 1.1.4 >Reporter: Igor Sapego >Assignee: Vladimir Ozerov > > Currently there is std::string type used in some parts of public API while > const char* used in some other parts. Need to review API and suggest solution > for the consistent string policy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1467) CPP: Create application for standalone node.
[ https://issues.apache.org/jira/browse/IGNITE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1467: Assignee: Vladimir Ozerov (was: Igor Sapego) > CPP: Create application for standalone node. > - > > Key: IGNITE-1467 > URL: https://issues.apache.org/jira/browse/IGNITE-1467 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.5 > > > We need to create executable application to start stadalone CPP node. This > can be done in the same way as we did it for .Net. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1647) CPP: Implement SqlFieldQuery
Igor Sapego created IGNITE-1647: --- Summary: CPP: Implement SqlFieldQuery Key: IGNITE-1647 URL: https://issues.apache.org/jira/browse/IGNITE-1647 Project: Ignite Issue Type: Task Components: interop Affects Versions: 1.1.4 Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.5 Need to decide on interface of the SqlFieldQuery class in C++ and implement it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1647) CPP: Implement SqlFieldQuery
[
https://issues.apache.org/jira/browse/IGNITE-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950576#comment-14950576
]
Igor Sapego commented on IGNITE-1647:
-
Following implementation is proposed:
1. New class {{SqlFiledsQuery}}.
2. New method for Cache class: {{QueryFieldsCursor Query(const
SqlFiledsQuery&)}}.
3. New class {{QueryFieldsCursor}} with method {{FieldsRow GetNext()}}.
4. New class {{FieldsRow}} with methods {{T GetNext()}} and {{bool HasNext()}}.
> CPP: Implement SqlFieldQuery
>
>
> Key: IGNITE-1647
> URL: https://issues.apache.org/jira/browse/IGNITE-1647
> Project: Ignite
> Issue Type: Task
> Components: interop
>Affects Versions: 1.1.4
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.5
>
>
> Need to decide on interface of the SqlFieldQuery class in C++ and implement
> it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-1467) CPP: Create application for standalone node.
[ https://issues.apache.org/jira/browse/IGNITE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953043#comment-14953043 ] Igor Sapego commented on IGNITE-1467: - Fixed > CPP: Create application for standalone node. > - > > Key: IGNITE-1467 > URL: https://issues.apache.org/jira/browse/IGNITE-1467 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.5 > > > We need to create executable application to start stadalone CPP node. This > can be done in the same way as we did it for .Net. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1680) CPP: Implement basic API for remote job execution
Igor Sapego created IGNITE-1680: --- Summary: CPP: Implement basic API for remote job execution Key: IGNITE-1680 URL: https://issues.apache.org/jira/browse/IGNITE-1680 Project: Ignite Issue Type: Task Components: interop Affects Versions: 1.1.4 Reporter: Igor Sapego Assignee: Igor Sapego Need to implement IgniteCompute class for C++ with one basic method IgniteCompute::Call(...) which will provide basic remote job execution API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1647) CPP: Implement SqlFieldQuery
[ https://issues.apache.org/jira/browse/IGNITE-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14960620#comment-14960620 ] Igor Sapego commented on IGNITE-1647: - Vladimir, thank you for the review. Here are some comments: 1) You are right. Fixed. 2-3) Maybe it should be done in separate ticket as the same can be said about any other Query - for every QueryCursorImpl::GetNext() operation new InteropMemory is allocated. Also, it means that every existing QueryFieldsRow should be invalidated in some way after new GetNext() call. > CPP: Implement SqlFieldQuery > > > Key: IGNITE-1647 > URL: https://issues.apache.org/jira/browse/IGNITE-1647 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.5 > > > Need to decide on interface of the SqlFieldQuery class in C++ and implement > it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1467) CPP: Create application for standalone node.
[ https://issues.apache.org/jira/browse/IGNITE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966853#comment-14966853 ] Igor Sapego commented on IGNITE-1467: - Fixed that too. Also added warning if some unknown arguments are being used, > CPP: Create application for standalone node. > - > > Key: IGNITE-1467 > URL: https://issues.apache.org/jira/browse/IGNITE-1467 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Igor Sapego >Priority: Critical > Fix For: 1.5 > > > We need to create executable application to start stadalone CPP node. This > can be done in the same way as we did it for .Net. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-1467) CPP: Create application for standalone node.
[ https://issues.apache.org/jira/browse/IGNITE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966853#comment-14966853 ] Igor Sapego edited comment on IGNITE-1467 at 10/21/15 2:03 PM: --- Fixed that too. Also added warning if some unknown arguments are being used. was (Author: isapego): Fixed that too. Also added warning if some unknown arguments are being used, > CPP: Create application for standalone node. > - > > Key: IGNITE-1467 > URL: https://issues.apache.org/jira/browse/IGNITE-1467 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Igor Sapego >Priority: Critical > Fix For: 1.5 > > > We need to create executable application to start stadalone CPP node. This > can be done in the same way as we did it for .Net. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1786) Need to implement ODBC driver for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-1786: --- Assignee: Igor Sapego > Need to implement ODBC driver for Ignite > > > Key: IGNITE-1786 > URL: https://issues.apache.org/jira/browse/IGNITE-1786 > Project: Ignite > Issue Type: New Feature > Components: clients >Reporter: Dmitriy Setrakyan >Assignee: Igor Sapego > Fix For: 1.6 > > > # We have a C++ API for Ignite which starts JVM internally. Probably we can > just add that ODBC API there. > # Another approach is to implement really separate driver and a network > server on java side which will interact with each other. > The first one is simpler and probably more effective, but heavyweight. The > second one is probably slower but but more lightweight. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1786) Need to implement ODBC driver for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14974798#comment-14974798 ] Igor Sapego commented on IGNITE-1786: - I suggest to implement separate lightweight driver and use shared memory to communicate with the JVM. This approach will require a JVM node running on the same computer but it will be more flexible than the first approach and easier to implement than the second one. > Need to implement ODBC driver for Ignite > > > Key: IGNITE-1786 > URL: https://issues.apache.org/jira/browse/IGNITE-1786 > Project: Ignite > Issue Type: New Feature > Components: clients >Reporter: Dmitriy Setrakyan >Assignee: Igor Sapego > Fix For: 1.6 > > > # We have a C++ API for Ignite which starts JVM internally. Probably we can > just add that ODBC API there. > # Another approach is to implement really separate driver and a network > server on java side which will interact with each other. > The first one is simpler and probably more effective, but heavyweight. The > second one is probably slower but but more lightweight. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1786) Need to implement ODBC driver for Ignite
[
https://issues.apache.org/jira/browse/IGNITE-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976177#comment-14976177
]
Igor Sapego commented on IGNITE-1786:
-
ODBC API itself has a lot of functions. I believe it makes sense to implement
the minimum set of functions that will provide us with ability to perform
simple queries for the beginning.
Here is the set that should do:
{code}
SQLAllocHandle
SQLFreeHandle
SQLConnect
SQLDisconnect
SQLExecDirect
SQLFreeStmt
SQLFetch
SQLGetData
{code}
> Need to implement ODBC driver for Ignite
>
>
> Key: IGNITE-1786
> URL: https://issues.apache.org/jira/browse/IGNITE-1786
> Project: Ignite
> Issue Type: New Feature
> Components: clients
>Reporter: Dmitriy Setrakyan
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> # We have a C++ API for Ignite which starts JVM internally. Probably we can
> just add that ODBC API there.
> # Another approach is to implement really separate driver and a network
> server on java side which will interact with each other.
> The first one is simpler and probably more effective, but heavyweight. The
> second one is probably slower but but more lightweight.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1798) CPP: implement constant-time field lookup for portables.
Igor Sapego created IGNITE-1798: --- Summary: CPP: implement constant-time field lookup for portables. Key: IGNITE-1798 URL: https://issues.apache.org/jira/browse/IGNITE-1798 Project: Ignite Issue Type: Sub-task Components: interop Affects Versions: ignite-1.4 Reporter: Igor Sapego Assignee: Igor Sapego Priority: Blocker Fix For: 1.5 Constant-time field lookup for portables should be implemented for C++ implementation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1798) CPP: implement constant-time field lookup for portables.
[ https://issues.apache.org/jira/browse/IGNITE-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981970#comment-14981970 ] Igor Sapego commented on IGNITE-1798: - The point is to make C++ object serialialization/deserialization operations match [this|https://cwiki.apache.org/confluence/display/IGNITE/Portable+object+constant-time+field+lookup] document. > CPP: implement constant-time field lookup for portables. > > > Key: IGNITE-1798 > URL: https://issues.apache.org/jira/browse/IGNITE-1798 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Blocker > Fix For: 1.5 > > > Constant-time field lookup for portables should be implemented for C++ > implementation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1798) CPP: implement constant-time field lookup for portables.
[ https://issues.apache.org/jira/browse/IGNITE-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981973#comment-14981973 ] Igor Sapego commented on IGNITE-1798: - Final portable objects structure and schema ID generation algorithm are described in comments to IGNITE-1770. > CPP: implement constant-time field lookup for portables. > > > Key: IGNITE-1798 > URL: https://issues.apache.org/jira/browse/IGNITE-1798 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Blocker > Fix For: 1.5 > > > Constant-time field lookup for portables should be implemented for C++ > implementation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1821) CPP: compact footer offsets
Igor Sapego created IGNITE-1821: --- Summary: CPP: compact footer offsets Key: IGNITE-1821 URL: https://issues.apache.org/jira/browse/IGNITE-1821 Project: Ignite Issue Type: Sub-task Components: interop Affects Versions: ignite-1.4 Reporter: Igor Sapego Assignee: Igor Sapego Priority: Critical Fix For: 1.5 Impement changes described in IGNITE-1814 for C++. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1821) CPP: compact footer offsets
[ https://issues.apache.org/jira/browse/IGNITE-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1821: Description: Implement changes described in IGNITE-1814 for C++. (was: Imlpement changes described in IGNITE-1814 for C++.) > CPP: compact footer offsets > --- > > Key: IGNITE-1821 > URL: https://issues.apache.org/jira/browse/IGNITE-1821 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Critical > Fix For: 1.5 > > > Implement changes described in IGNITE-1814 for C++. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1821) CPP: compact footer offsets
[ https://issues.apache.org/jira/browse/IGNITE-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1821: Description: Imlpement changes described in IGNITE-1814 for C++. (was: Impement changes described in IGNITE-1814 for C++.) > CPP: compact footer offsets > --- > > Key: IGNITE-1821 > URL: https://issues.apache.org/jira/browse/IGNITE-1821 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Critical > Fix For: 1.5 > > > Imlpement changes described in IGNITE-1814 for C++. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1821) CPP: compact footer offsets
[ https://issues.apache.org/jira/browse/IGNITE-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14982860#comment-14982860 ] Igor Sapego commented on IGNITE-1821: - Affects following algorithms: - Schema writing after field data has been written. - Field lookup. - Raw offset detection. > CPP: compact footer offsets > --- > > Key: IGNITE-1821 > URL: https://issues.apache.org/jira/browse/IGNITE-1821 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Critical > Fix For: 1.5 > > > Implement changes described in IGNITE-1814 for C++. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1821) CPP: compact footer offsets
[ https://issues.apache.org/jira/browse/IGNITE-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1821: Assignee: Vladimir Ozerov (was: Igor Sapego) > CPP: compact footer offsets > --- > > Key: IGNITE-1821 > URL: https://issues.apache.org/jira/browse/IGNITE-1821 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Igor Sapego >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.5 > > > Implement changes described in IGNITE-1814 for C++. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1821) CPP: compact footer offsets
[ https://issues.apache.org/jira/browse/IGNITE-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987010#comment-14987010 ] Igor Sapego commented on IGNITE-1821: - Fixed > CPP: compact footer offsets > --- > > Key: IGNITE-1821 > URL: https://issues.apache.org/jira/browse/IGNITE-1821 > Project: Ignite > Issue Type: Sub-task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Critical > Fix For: 1.5 > > > Implement changes described in IGNITE-1814 for C++. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1786) Need to implement ODBC driver for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14987044#comment-14987044 ] Igor Sapego commented on IGNITE-1786: - Ok, it seems like using a TCP sockets would be a more flexible approach. What I'm going to do now is a walking skeleton of some kind, that will include basic ODBC driver which can be used to connect to Ignite grid and perform some simple queries. Here is what I'm planning to do in the beginning: - Add new GridNioServer to GridQueryProcessor that will communicate with the ODBC driver. - Add configuration for the ODBC server. - Write a simple TCP-client on the C++ side that will work for both Windows and Linux and that will be able to communicate with ODBC server on Java side. - Move C++ implementation of Portable protocol to separate library. - Use Portable protocol to send queries from C++ driver to Java and receive responses. > Need to implement ODBC driver for Ignite > > > Key: IGNITE-1786 > URL: https://issues.apache.org/jira/browse/IGNITE-1786 > Project: Ignite > Issue Type: New Feature > Components: clients >Reporter: Dmitriy Setrakyan >Assignee: Igor Sapego > Fix For: 1.6 > > > # We have a C++ API for Ignite which starts JVM internally. Probably we can > just add that ODBC API there. > # Another approach is to implement really separate driver and a network > server on java side which will interact with each other. > The first one is simpler and probably more effective, but heavyweight. The > second one is probably slower but but more lightweight. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1862) CPP: Fix string handling
[ https://issues.apache.org/jira/browse/IGNITE-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-1862: --- Assignee: Igor Sapego > CPP: Fix string handling > > > Key: IGNITE-1862 > URL: https://issues.apache.org/jira/browse/IGNITE-1862 > Project: Ignite > Issue Type: Task > Components: interop >Affects Versions: ignite-1.4 >Reporter: Vladimir Ozerov >Assignee: Igor Sapego >Priority: Critical > Fix For: 1.5 > > > Currently we write strings using 2 bytes for each simbol. This way we are > trying to mimic UTF16, which is natural for Java. > Instead of doing this weird things, we should: > 1) Tell user that we expect UTF8 string. > 2) Write strings as plain char*. > Once it is done, we will be able to remove "convertStrings" property from > PortableMarshaller. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1901) CPP: Adopt new marshalling flags.
[
https://issues.apache.org/jira/browse/IGNITE-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego reassigned IGNITE-1901:
---
Assignee: Igor Sapego
> CPP: Adopt new marshalling flags.
> -
>
> Key: IGNITE-1901
> URL: https://issues.apache.org/jira/browse/IGNITE-1901
> Project: Ignite
> Issue Type: Sub-task
> Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Igor Sapego
>Priority: Critical
> Fix For: 1.5
>
>
> As a part of IGNITE-1816 I had to revisit our flags. Here are how they look
> now:
> {code}
> /** Flag: user type. */
> public static final short FLAG_USR_TYP = 0x0001;
> /** Flag: schema exists. */
> public static final short FLAG_HAS_SCHEMA = 0x0002;
> /** Flag indicating that object has raw data. */
> public static final short FLAG_HAS_RAW = 0x0004;
> /** Flag: offsets take 1 byte. */
> public static final short FLAG_OFFSET_ONE_BYTE = 0x0008;
> /** Flag: offsets take 2 bytes. */
> public static final short FLAG_OFFSET_TWO_BYTES = 0x0010;
> /** Flag: compact footer, no field IDs. */
> public static final short FLAG_COMPACT_FOOTER = 0x0020;
> {code}
> The following changes must be made to CPP:
> 1) When schema exists (i.e. at least on non-raw fieid was written), HAS_
> SCHEMA flag is set to true. This is the inversed version of what previously
> was "RAW_ONLY".
> 2) When raw data exists, HAS_RAW flag is set to true. This flag should be
> used to determine location of raw data.
> *DO NOT USE % for this anymore!*
> 3) For now COMPACT_FOOTER should always be 0. If you receive an object with
> this flag set to 1, an exception must be thrown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1901) CPP: Adopt new marshalling flags.
[
https://issues.apache.org/jira/browse/IGNITE-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-1901:
Assignee: Vladimir Ozerov (was: Igor Sapego)
> CPP: Adopt new marshalling flags.
> -
>
> Key: IGNITE-1901
> URL: https://issues.apache.org/jira/browse/IGNITE-1901
> Project: Ignite
> Issue Type: Sub-task
> Components: interop
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Critical
> Fix For: 1.5
>
>
> As a part of IGNITE-1816 I had to revisit our flags. Here are how they look
> now:
> {code}
> /** Flag: user type. */
> public static final short FLAG_USR_TYP = 0x0001;
> /** Flag: schema exists. */
> public static final short FLAG_HAS_SCHEMA = 0x0002;
> /** Flag indicating that object has raw data. */
> public static final short FLAG_HAS_RAW = 0x0004;
> /** Flag: offsets take 1 byte. */
> public static final short FLAG_OFFSET_ONE_BYTE = 0x0008;
> /** Flag: offsets take 2 bytes. */
> public static final short FLAG_OFFSET_TWO_BYTES = 0x0010;
> /** Flag: compact footer, no field IDs. */
> public static final short FLAG_COMPACT_FOOTER = 0x0020;
> {code}
> The following changes must be made to CPP:
> 1) When schema exists (i.e. at least on non-raw fieid was written), HAS_
> SCHEMA flag is set to true. This is the inversed version of what previously
> was "RAW_ONLY".
> 2) When raw data exists, HAS_RAW flag is set to true. This flag should be
> used to determine location of raw data.
> *DO NOT USE % for this anymore!*
> 3) For now COMPACT_FOOTER should always be 0. If you receive an object with
> this flag set to 1, an exception must be thrown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-1949) C++ platform library for Linux: make uninstall doesn't delete directories
Igor Sapego created IGNITE-1949: --- Summary: C++ platform library for Linux: make uninstall doesn't delete directories Key: IGNITE-1949 URL: https://issues.apache.org/jira/browse/IGNITE-1949 Project: Ignite Issue Type: Bug Affects Versions: ignite-1.4 Reporter: Igor Sapego Assignee: Igor Sapego Priority: Minor Uninstall doesn't delete directories created for include files -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1949) C++ platform library for Linux: make uninstall doesn't delete directories
[ https://issues.apache.org/jira/browse/IGNITE-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1949: Component/s: interop > C++ platform library for Linux: make uninstall doesn't delete directories > - > > Key: IGNITE-1949 > URL: https://issues.apache.org/jira/browse/IGNITE-1949 > Project: Ignite > Issue Type: Bug > Components: interop >Affects Versions: ignite-1.4 >Reporter: Igor Sapego >Assignee: Vladimir Ozerov >Priority: Minor > > Uninstall doesn't delete directories created for include files -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-1963) CPP: Optimize interop memory
Igor Sapego created IGNITE-1963: --- Summary: CPP: Optimize interop memory Key: IGNITE-1963 URL: https://issues.apache.org/jira/browse/IGNITE-1963 Project: Ignite Issue Type: Task Affects Versions: ignite-1.4 Reporter: Igor Sapego Priority: Minor Current design of the InteropMemory class got some unavoidable overheads and makes it difficult to implement adapter-like subclasses. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1963) CPP: Optimize interop memory
[
https://issues.apache.org/jira/browse/IGNITE-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-1963:
Description:
Current design of the {{InteropMemory}} class got some unavoidable overheads
and makes it difficult to implement adapter-like subclasses.
1. Considering that {{InteropMemory}} is the only class that can be used with
binary streams and binary readers/writers, it should have design that allows
writing adapter subclasses. For example, it could be std::vector class adapter
or stack-allocated array.
2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
allocations during instance creating for all children. It's a big overhead
considering that memory allocations happen often.
3. Consider replacing this class into two classes: read/write memory and read
only memory. It makes sense because Input streams do not modify memory they
operate on and It would allow us to implement reading in a more efficient way
because we wont be needing to implement {{Reallocate()}} method anymore.
was:Current design of the InteropMemory class got some unavoidable overheads
and makes it difficult to implement adapter-like subclasses.
> CPP: Optimize interop memory
>
>
> Key: IGNITE-1963
> URL: https://issues.apache.org/jira/browse/IGNITE-1963
> Project: Ignite
> Issue Type: Task
>Affects Versions: ignite-1.4
>Reporter: Igor Sapego
>Priority: Minor
>
> Current design of the {{InteropMemory}} class got some unavoidable overheads
> and makes it difficult to implement adapter-like subclasses.
> 1. Considering that {{InteropMemory}} is the only class that can be used with
> binary streams and binary readers/writers, it should have design that allows
> writing adapter subclasses. For example, it could be std::vector class
> adapter or stack-allocated array.
> 2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
> allocations during instance creating for all children. It's a big overhead
> considering that memory allocations happen often.
> 3. Consider replacing this class into two classes: read/write memory and read
> only memory. It makes sense because Input streams do not modify memory they
> operate on and It would allow us to implement reading in a more efficient way
> because we wont be needing to implement {{Reallocate()}} method anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1963) CPP: Optimize interop memory
[
https://issues.apache.org/jira/browse/IGNITE-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-1963:
Description:
Current design of the {{InteropMemory}} class got some unavoidable overheads
and makes it difficult to implement adapter-like subclasses.
1. Considering that {{InteropMemory}} is the only class that can be used with
binary streams and binary readers/writers, it should have design that allows
writing adapter subclasses. For example, it could be std::vector class adapter
or stack-allocated array.
2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
allocations during instance construction. It's a big overhead considering that
memory allocations happen often.
3. Consider replacing this class into two classes: read/write memory and read
only memory. It makes sense because Input streams do not modify memory they
operate on and It would allow us to implement reading in a more efficient way
because we wont be needing to implement {{Reallocate()}} method anymore.
was:
Current design of the {{InteropMemory}} class got some unavoidable overheads
and makes it difficult to implement adapter-like subclasses.
1. Considering that {{InteropMemory}} is the only class that can be used with
binary streams and binary readers/writers, it should have design that allows
writing adapter subclasses. For example, it could be std::vector class adapter
or stack-allocated array.
2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
allocations during instance creating for all children. It's a big overhead
considering that memory allocations happen often.
3. Consider replacing this class into two classes: read/write memory and read
only memory. It makes sense because Input streams do not modify memory they
operate on and It would allow us to implement reading in a more efficient way
because we wont be needing to implement {{Reallocate()}} method anymore.
> CPP: Optimize interop memory
>
>
> Key: IGNITE-1963
> URL: https://issues.apache.org/jira/browse/IGNITE-1963
> Project: Ignite
> Issue Type: Task
>Affects Versions: ignite-1.4
>Reporter: Igor Sapego
>Priority: Minor
>
> Current design of the {{InteropMemory}} class got some unavoidable overheads
> and makes it difficult to implement adapter-like subclasses.
> 1. Considering that {{InteropMemory}} is the only class that can be used with
> binary streams and binary readers/writers, it should have design that allows
> writing adapter subclasses. For example, it could be std::vector class
> adapter or stack-allocated array.
> 2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
> allocations during instance construction. It's a big overhead considering
> that memory allocations happen often.
> 3. Consider replacing this class into two classes: read/write memory and read
> only memory. It makes sense because Input streams do not modify memory they
> operate on and It would allow us to implement reading in a more efficient way
> because we wont be needing to implement {{Reallocate()}} method anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1963) CPP: Optimize interop memory
[
https://issues.apache.org/jira/browse/IGNITE-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-1963:
Description:
Current design of the {{InteropMemory}} class got some unavoidable overheads
and makes it difficult to implement adapter-like subclasses.
1. Considering that {{InteropMemory}} is the only class that can be used with
binary streams and binary readers/writers, it should have design that allows
writing adapter subclasses. For example, it could be std::vector class adapter
or stack-allocated array.
2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
allocations during instance construction. It's a big overhead considering that
{{InteropUnpooledMemory}} instances construction happen often.
3. Consider replacing this class into two classes: read/write memory and read
only memory. It makes sense because Input streams do not modify memory they
operate on and It would allow us to implement reading in a more efficient way
because we wont be needing to implement {{Reallocate()}} method anymore.
was:
Current design of the {{InteropMemory}} class got some unavoidable overheads
and makes it difficult to implement adapter-like subclasses.
1. Considering that {{InteropMemory}} is the only class that can be used with
binary streams and binary readers/writers, it should have design that allows
writing adapter subclasses. For example, it could be std::vector class adapter
or stack-allocated array.
2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
allocations during instance construction. It's a big overhead considering that
memory allocations happen often.
3. Consider replacing this class into two classes: read/write memory and read
only memory. It makes sense because Input streams do not modify memory they
operate on and It would allow us to implement reading in a more efficient way
because we wont be needing to implement {{Reallocate()}} method anymore.
> CPP: Optimize interop memory
>
>
> Key: IGNITE-1963
> URL: https://issues.apache.org/jira/browse/IGNITE-1963
> Project: Ignite
> Issue Type: Task
>Affects Versions: ignite-1.4
>Reporter: Igor Sapego
>Priority: Minor
>
> Current design of the {{InteropMemory}} class got some unavoidable overheads
> and makes it difficult to implement adapter-like subclasses.
> 1. Considering that {{InteropMemory}} is the only class that can be used with
> binary streams and binary readers/writers, it should have design that allows
> writing adapter subclasses. For example, it could be std::vector class
> adapter or stack-allocated array.
> 2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
> allocations during instance construction. It's a big overhead considering
> that {{InteropUnpooledMemory}} instances construction happen often.
> 3. Consider replacing this class into two classes: read/write memory and read
> only memory. It makes sense because Input streams do not modify memory they
> operate on and It would allow us to implement reading in a more efficient way
> because we wont be needing to implement {{Reallocate()}} method anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1963) CPP: Optimize interop memory
[
https://issues.apache.org/jira/browse/IGNITE-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-1963:
Fix Version/s: 1.6
> CPP: Optimize interop memory
>
>
> Key: IGNITE-1963
> URL: https://issues.apache.org/jira/browse/IGNITE-1963
> Project: Ignite
> Issue Type: Task
>Affects Versions: ignite-1.4
>Reporter: Igor Sapego
>Priority: Minor
> Fix For: 1.6
>
>
> Current design of the {{InteropMemory}} class got some unavoidable overheads
> and makes it difficult to implement adapter-like subclasses.
> 1. Considering that {{InteropMemory}} is the only class that can be used with
> binary streams and binary readers/writers, it should have design that allows
> writing adapter subclasses. For example, it could be std::vector class
> adapter or stack-allocated array.
> 2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
> allocations during instance construction. It's a big overhead considering
> that {{InteropUnpooledMemory}} instances construction happen often.
> 3. Consider replacing this class into two classes: read/write memory and read
> only memory. It makes sense because Input streams do not modify memory they
> operate on and It would allow us to implement reading in a more efficient way
> because we wont be needing to implement {{Reallocate()}} method anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1963) CPP: Optimize interop memory
[
https://issues.apache.org/jira/browse/IGNITE-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-1963:
Component/s: interop
> CPP: Optimize interop memory
>
>
> Key: IGNITE-1963
> URL: https://issues.apache.org/jira/browse/IGNITE-1963
> Project: Ignite
> Issue Type: Task
> Components: interop
>Affects Versions: ignite-1.4
>Reporter: Igor Sapego
>Priority: Minor
> Fix For: 1.6
>
>
> Current design of the {{InteropMemory}} class got some unavoidable overheads
> and makes it difficult to implement adapter-like subclasses.
> 1. Considering that {{InteropMemory}} is the only class that can be used with
> binary streams and binary readers/writers, it should have design that allows
> writing adapter subclasses. For example, it could be std::vector class
> adapter or stack-allocated array.
> 2. Current {{InteropUnpooledMemory}} implementation makes two heap memory
> allocations during instance construction. It's a big overhead considering
> that {{InteropUnpooledMemory}} instances construction happen often.
> 3. Consider replacing this class into two classes: read/write memory and read
> only memory. It makes sense because Input streams do not modify memory they
> operate on and It would allow us to implement reading in a more efficient way
> because we wont be needing to implement {{Reallocate()}} method anymore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-1986) cpp: couldn't build cpp ignite-examples due to wrong parameters values in the project file
[ https://issues.apache.org/jira/browse/IGNITE-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-1986: --- Assignee: Igor Sapego > cpp: couldn't build cpp ignite-examples due to wrong parameters values in the > project file > -- > > Key: IGNITE-1986 > URL: https://issues.apache.org/jira/browse/IGNITE-1986 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.5 > Environment: Win7 64bit, MS Visual C++ 2010 Professional, Apache > Ignite 1.5.0 build #79 >Reporter: Vasilisa Sidorova >Assignee: Igor Sapego >Priority: Critical > Fix For: 1.5 > > > - > DESCRIPTION > - > Couldn't build cpp ignite-examples due to wrong parameters values in the > %IGNITE_HOME%\platforms\cpp\examples\project\vs\ignite-examples.vcxproj. > PlatformToolset is v120 but should be v100 (local fix for this issue works > good) > - > STEPS FOR REPRODUCE > - > # Open and build %IGNITE_HOME%\platforms\cpp\project\vs\ignite.sln > # Open and build > %IGNITE_HOME%\platforms\cpp\examples\project\vs\ignite-examples.sln > - > ACTUAL RESULT > - > Project doesn't built with error: > Error 1 error MSB8008: Specified platform toolset (v120) is not > installed or invalid. Please make sure that a supported PlatformToolset value > is selected. C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\Microsoft.Cpp.x64.Targets > 507 6 ignite-examples > - > EXPECTED RESULT > - > Solution built without any exceptions > > ADDITIONAL INFO > > Second error is wrong ToolsVersion in the same project file. > It's 12.0 and should be 4.0. Please, fix it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-1986) cpp: couldn't build cpp ignite-examples due to wrong parameters values in the project file
[ https://issues.apache.org/jira/browse/IGNITE-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022564#comment-15022564 ] Igor Sapego commented on IGNITE-1986: - I'll fix this one. > cpp: couldn't build cpp ignite-examples due to wrong parameters values in the > project file > -- > > Key: IGNITE-1986 > URL: https://issues.apache.org/jira/browse/IGNITE-1986 > Project: Ignite > Issue Type: Bug >Affects Versions: 1.5 > Environment: Win7 64bit, MS Visual C++ 2010 Professional, Apache > Ignite 1.5.0 build #79 >Reporter: Vasilisa Sidorova >Priority: Critical > Fix For: 1.5 > > > - > DESCRIPTION > - > Couldn't build cpp ignite-examples due to wrong parameters values in the > %IGNITE_HOME%\platforms\cpp\examples\project\vs\ignite-examples.vcxproj. > PlatformToolset is v120 but should be v100 (local fix for this issue works > good) > - > STEPS FOR REPRODUCE > - > # Open and build %IGNITE_HOME%\platforms\cpp\project\vs\ignite.sln > # Open and build > %IGNITE_HOME%\platforms\cpp\examples\project\vs\ignite-examples.sln > - > ACTUAL RESULT > - > Project doesn't built with error: > Error 1 error MSB8008: Specified platform toolset (v120) is not > installed or invalid. Please make sure that a supported PlatformToolset value > is selected. C:\Program Files > (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\Microsoft.Cpp.x64.Targets > 507 6 ignite-examples > - > EXPECTED RESULT > - > Solution built without any exceptions > > ADDITIONAL INFO > > Second error is wrong ToolsVersion in the same project file. > It's 12.0 and should be 4.0. Please, fix it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2021) CPP: Implement tests for ODBC driver.
Igor Sapego created IGNITE-2021: --- Summary: CPP: Implement tests for ODBC driver. Key: IGNITE-2021 URL: https://issues.apache.org/jira/browse/IGNITE-2021 Project: Ignite Issue Type: Sub-task Components: interop Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.6 Need to implement tests sub-project for ODBC driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2021) CPP: Create test project for ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2021: Summary: CPP: Create test project for ODBC driver. (was: CPP: Implement tests for ODBC driver.) > CPP: Create test project for ODBC driver. > - > > Key: IGNITE-2021 > URL: https://issues.apache.org/jira/browse/IGNITE-2021 > Project: Ignite > Issue Type: Sub-task > Components: interop >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Need to implement tests sub-project for ODBC driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2022) CPP: Add local tests for ODBC driver.
Igor Sapego created IGNITE-2022: --- Summary: CPP: Add local tests for ODBC driver. Key: IGNITE-2022 URL: https://issues.apache.org/jira/browse/IGNITE-2022 Project: Ignite Issue Type: Sub-task Components: interop Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.6 Need to add tests for the components that can be tested locally, without establishing connection to a node. Here is the list of such a components: 1. Configuration. 2. ConnectionInfo. 3. Parser. 5. ApplicationDataBuffer. 4. Row. 6. Cursor. 7. Utility. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2021) CPP: Create test project for ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15031715#comment-15031715 ] Igor Sapego commented on IGNITE-2021: - Task completed and merged to ignite-1786. > CPP: Create test project for ODBC driver. > - > > Key: IGNITE-2021 > URL: https://issues.apache.org/jira/browse/IGNITE-2021 > Project: Ignite > Issue Type: Sub-task > Components: interop >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Need to implement tests sub-project for ODBC driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2021) CPP: Create test project for ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15031720#comment-15031720 ] Igor Sapego commented on IGNITE-2021: - Current implementation of ODBC test project does not link driver as a dynamic library. Instead it links specific files which contain tested functionality. Test project is implemented in that way to be able to test internal driver functions and classes which are not exported. > CPP: Create test project for ODBC driver. > - > > Key: IGNITE-2021 > URL: https://issues.apache.org/jira/browse/IGNITE-2021 > Project: Ignite > Issue Type: Sub-task > Components: interop >Reporter: Igor Sapego >Assignee: Vladimir Ozerov > Fix For: 1.6 > > > Need to implement tests sub-project for ODBC driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2044) CPP: Fix bugs revealed by the ODBC tests.
Igor Sapego created IGNITE-2044: --- Summary: CPP: Fix bugs revealed by the ODBC tests. Key: IGNITE-2044 URL: https://issues.apache.org/jira/browse/IGNITE-2044 Project: Ignite Issue Type: Sub-task Components: interop Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.6 Number of bugs have been found during tests implementation (See IGNITE-2022). Need to fix them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2022) CPP: Add local tests for ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033775#comment-15033775 ] Igor Sapego commented on IGNITE-2022: - Merged to development branch (ignite-1786). > CPP: Add local tests for ODBC driver. > - > > Key: IGNITE-2022 > URL: https://issues.apache.org/jira/browse/IGNITE-2022 > Project: Ignite > Issue Type: Sub-task > Components: interop >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Need to add tests for the components that can be tested locally, without > establishing connection to a node. Here is the list of such a components: > 1. Configuration. > 2. ConnectionInfo. > 3. Parser. > 5. ApplicationDataBuffer. > 4. Row. > 6. Cursor. > 7. Utility. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2022) CPP: Add local tests for ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2022: Assignee: Vladimir Ozerov (was: Igor Sapego) > CPP: Add local tests for ODBC driver. > - > > Key: IGNITE-2022 > URL: https://issues.apache.org/jira/browse/IGNITE-2022 > Project: Ignite > Issue Type: Sub-task > Components: interop >Reporter: Igor Sapego >Assignee: Vladimir Ozerov > Fix For: 1.6 > > > Need to add tests for the components that can be tested locally, without > establishing connection to a node. Here is the list of such a components: > 1. Configuration. > 2. ConnectionInfo. > 3. Parser. > 5. ApplicationDataBuffer. > 4. Row. > 6. Cursor. > 7. Utility. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2022) CPP: Add local tests for ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033766#comment-15033766 ] Igor Sapego commented on IGNITE-2022: - Number of bugs have been found during tests implementation. Corresponding ticket has been submitted: IGNITE-2044. > CPP: Add local tests for ODBC driver. > - > > Key: IGNITE-2022 > URL: https://issues.apache.org/jira/browse/IGNITE-2022 > Project: Ignite > Issue Type: Sub-task > Components: interop >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Need to add tests for the components that can be tested locally, without > establishing connection to a node. Here is the list of such a components: > 1. Configuration. > 2. ConnectionInfo. > 3. Parser. > 5. ApplicationDataBuffer. > 4. Row. > 6. Cursor. > 7. Utility. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2044) CPP: Fix bugs revealed by the ODBC tests.
[ https://issues.apache.org/jira/browse/IGNITE-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15034001#comment-15034001 ] Igor Sapego commented on IGNITE-2044: - Merged into development branch. > CPP: Fix bugs revealed by the ODBC tests. > - > > Key: IGNITE-2044 > URL: https://issues.apache.org/jira/browse/IGNITE-2044 > Project: Ignite > Issue Type: Sub-task > Components: interop >Reporter: Igor Sapego >Assignee: Vladimir Ozerov > Fix For: 1.6 > > > Number of bugs have been found during tests implementation (See IGNITE-2022). > Need to fix them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2045) Make message handling by OdbcProcessor synchronous.
Igor Sapego created IGNITE-2045: --- Summary: Make message handling by OdbcProcessor synchronous. Key: IGNITE-2045 URL: https://issues.apache.org/jira/browse/IGNITE-2045 Project: Ignite Issue Type: Sub-task Components: interop Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.6 Currently OdbcProcessor implementation is asynchronous. It seems like this is an unnecessary overhead and should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2045) Make message handling by OdbcProcessor synchronous.
[ https://issues.apache.org/jira/browse/IGNITE-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2045: Assignee: Vladimir Ozerov (was: Igor Sapego) > Make message handling by OdbcProcessor synchronous. > --- > > Key: IGNITE-2045 > URL: https://issues.apache.org/jira/browse/IGNITE-2045 > Project: Ignite > Issue Type: Sub-task > Components: interop >Reporter: Igor Sapego >Assignee: Vladimir Ozerov > Fix For: 1.6 > > > Currently OdbcProcessor implementation is asynchronous. It seems like this is > an unnecessary overhead and should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2045) Make message handling by OdbcProcessor synchronous.
[ https://issues.apache.org/jira/browse/IGNITE-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15034174#comment-15034174 ] Igor Sapego commented on IGNITE-2045: - Merged into parent development branch. > Make message handling by OdbcProcessor synchronous. > --- > > Key: IGNITE-2045 > URL: https://issues.apache.org/jira/browse/IGNITE-2045 > Project: Ignite > Issue Type: Sub-task > Components: interop >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Currently OdbcProcessor implementation is asynchronous. It seems like this is > an unnecessary overhead and should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2046) CPP: Implement SQLColumns ODBC API function
Igor Sapego created IGNITE-2046:
---
Summary: CPP: Implement SQLColumns ODBC API function
Key: IGNITE-2046
URL: https://issues.apache.org/jira/browse/IGNITE-2046
Project: Ignite
Issue Type: Sub-task
Components: interop
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.6
{{SQLColumns}} API function is often used by the data analyzing software to
retrieve information about columns returned by the SQL query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2046) CPP: Implement catalog ODBC API functions
[
https://issues.apache.org/jira/browse/IGNITE-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2046:
Summary: CPP: Implement catalog ODBC API functions (was: CPP: Implement
SQLColumns ODBC API function)
> CPP: Implement catalog ODBC API functions
> -
>
> Key: IGNITE-2046
> URL: https://issues.apache.org/jira/browse/IGNITE-2046
> Project: Ignite
> Issue Type: Sub-task
> Components: interop
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> {{SQLColumns}} API function is often used by the data analyzing software to
> retrieve information about columns returned by the SQL query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2046) CPP: Implement catalog ODBC API functions
[
https://issues.apache.org/jira/browse/IGNITE-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2046:
Description:
Such API function is often used by the data analyzing software to retrieve
information about columns, tables and supported data types.
Here is the list of functions that need to be supported:
- {{SQLColumns}}
- {{SQLTables}}
- {{SQLGetTypeInfo}}
- {{SQLStatistics}}
was:{{SQLColumns}} API function is often used by the data analyzing software
to retrieve information about columns returned by the SQL query.
> CPP: Implement catalog ODBC API functions
> -
>
> Key: IGNITE-2046
> URL: https://issues.apache.org/jira/browse/IGNITE-2046
> Project: Ignite
> Issue Type: Sub-task
> Components: interop
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> Such API function is often used by the data analyzing software to retrieve
> information about columns, tables and supported data types.
> Here is the list of functions that need to be supported:
> - {{SQLColumns}}
> - {{SQLTables}}
> - {{SQLGetTypeInfo}}
> - {{SQLStatistics}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2059) CPP: Implement basic support of the params for the OSBC driver.
Igor Sapego created IGNITE-2059:
---
Summary: CPP: Implement basic support of the params for the OSBC
driver.
Key: IGNITE-2059
URL: https://issues.apache.org/jira/browse/IGNITE-2059
Project: Ignite
Issue Type: Sub-task
Components: interop
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.6
We need to provide basic API for parameters binding.
Here is the list of functions that need to be supported:
- {{SQLBindParameter}}
- {{SQLNumParams}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2046) CPP: Implement catalog ODBC API functions
[
https://issues.apache.org/jira/browse/IGNITE-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2046:
Description:
Such API functions is often used by the data analyzing software to retrieve
information about columns, tables and supported data types.
Here is the list of functions that need to be supported:
- {{SQLColumns}}
- {{SQLTables}}
- {{SQLGetTypeInfo}}
- {{SQLStatistics}}
was:
Such API function is often used by the data analyzing software to retrieve
information about columns, tables and supported data types.
Here is the list of functions that need to be supported:
- {{SQLColumns}}
- {{SQLTables}}
- {{SQLGetTypeInfo}}
- {{SQLStatistics}}
> CPP: Implement catalog ODBC API functions
> -
>
> Key: IGNITE-2046
> URL: https://issues.apache.org/jira/browse/IGNITE-2046
> Project: Ignite
> Issue Type: Sub-task
> Components: interop
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> Such API functions is often used by the data analyzing software to retrieve
> information about columns, tables and supported data types.
> Here is the list of functions that need to be supported:
> - {{SQLColumns}}
> - {{SQLTables}}
> - {{SQLGetTypeInfo}}
> - {{SQLStatistics}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2060) CPP: Implement access to the metadata for result sets of the ODBC driver.
Igor Sapego created IGNITE-2060:
---
Summary: CPP: Implement access to the metadata for result sets of
the ODBC driver.
Key: IGNITE-2060
URL: https://issues.apache.org/jira/browse/IGNITE-2060
Project: Ignite
Issue Type: Sub-task
Components: interop
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.6
This type of API functions is often used by the data analyzing software to
retrieve information about columns, tables and supported data types.
Here is the list of functions that need to be supported:
- {{SQLColAttribute}}
- {{SQLDescribeCol}}
- {{SQLRowCount}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2061) CPP: Implement obtaining of diagnostic information for ODBC driver.
Igor Sapego created IGNITE-2061:
---
Summary: CPP: Implement obtaining of diagnostic information for
ODBC driver.
Key: IGNITE-2061
URL: https://issues.apache.org/jira/browse/IGNITE-2061
Project: Ignite
Issue Type: Sub-task
Components: interop
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.6
These API functions used by user to retrieve diagnostic information, such as
error or warning messages.
Here is the list of functions that need to be supported:
- {{SQLGetDiagField }}
- {{SQLGetDiagRec}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2062) CPP: Implement support of Linux OS family for the ODBC driver.
Igor Sapego created IGNITE-2062: --- Summary: CPP: Implement support of Linux OS family for the ODBC driver. Key: IGNITE-2062 URL: https://issues.apache.org/jira/browse/IGNITE-2062 Project: Ignite Issue Type: Sub-task Components: interop Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.6 ODBC driver should be buildable and usable on the Linux-based OS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2046) CPP: Implement catalog ODBC API functions
[
https://issues.apache.org/jira/browse/IGNITE-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2046:
Description:
Such API functions is often used by the data analyzing software to retrieve
information about columns, tables and supported data types.
Here is the list of functions that need to be supported:
- {{SQLColumns}}
- {{SQLTables}}
was:
Such API functions is often used by the data analyzing software to retrieve
information about columns, tables and supported data types.
Here is the list of functions that need to be supported:
- {{SQLColumns}}
- {{SQLTables}}
- {{SQLGetTypeInfo}}
- {{SQLStatistics}}
> CPP: Implement catalog ODBC API functions
> -
>
> Key: IGNITE-2046
> URL: https://issues.apache.org/jira/browse/IGNITE-2046
> Project: Ignite
> Issue Type: Sub-task
> Components: interop
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> Such API functions is often used by the data analyzing software to retrieve
> information about columns, tables and supported data types.
> Here is the list of functions that need to be supported:
> - {{SQLColumns}}
> - {{SQLTables}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2046) CPP: Implement catalog ODBC API functions
[
https://issues.apache.org/jira/browse/IGNITE-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045371#comment-15045371
]
Igor Sapego commented on IGNITE-2046:
-
Merged into parent development branch.
> CPP: Implement catalog ODBC API functions
> -
>
> Key: IGNITE-2046
> URL: https://issues.apache.org/jira/browse/IGNITE-2046
> Project: Ignite
> Issue Type: Sub-task
> Components: interop
>Reporter: Igor Sapego
>Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> Such API functions is often used by the data analyzing software to retrieve
> information about columns, tables and supported data types.
> Here is the list of functions that need to be supported:
> - {{SQLColumns}}
> - {{SQLTables}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2059) CPP: Implement basic support of the params for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2059:
Summary: CPP: Implement basic support of the params for the ODBC driver.
(was: CPP: Implement basic support of the params for the OSBC driver.)
> CPP: Implement basic support of the params for the ODBC driver.
> ---
>
> Key: IGNITE-2059
> URL: https://issues.apache.org/jira/browse/IGNITE-2059
> Project: Ignite
> Issue Type: Sub-task
> Components: interop
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> We need to provide basic API for parameters binding.
> Here is the list of functions that need to be supported:
> - {{SQLBindParameter}}
> - {{SQLNumParams}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2061) CPP: Implement obtaining of diagnostic information for ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2061:
Description:
These API functions used by user to retrieve diagnostic information, such as
error or warning messages.
Here is the list of functions that need to be supported:
- {{SQLGetDiagField}}
- {{SQLGetDiagRec}}
was:
These API functions used by user to retrieve diagnostic information, such as
error or warning messages.
Here is the list of functions that need to be supported:
- {{SQLGetDiagField }}
- {{SQLGetDiagRec}}
> CPP: Implement obtaining of diagnostic information for ODBC driver.
> ---
>
> Key: IGNITE-2061
> URL: https://issues.apache.org/jira/browse/IGNITE-2061
> Project: Ignite
> Issue Type: Sub-task
> Components: interop
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> These API functions used by user to retrieve diagnostic information, such as
> error or warning messages.
> Here is the list of functions that need to be supported:
> - {{SQLGetDiagField}}
> - {{SQLGetDiagRec}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2059) CPP: Implement basic support of the params for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048474#comment-15048474
]
Igor Sapego commented on IGNITE-2059:
-
Merged to parent development branch.
> CPP: Implement basic support of the params for the ODBC driver.
> ---
>
> Key: IGNITE-2059
> URL: https://issues.apache.org/jira/browse/IGNITE-2059
> Project: Ignite
> Issue Type: Sub-task
> Components: interop
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> We need to provide basic API for parameters binding.
> Here is the list of functions that need to be supported:
> - {{SQLBindParameter}}
> - {{SQLNumParams}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2022) CPP: Add local tests for ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-2022: --- Assignee: Igor Sapego (was: Vladimir Ozerov) > CPP: Add local tests for ODBC driver. > - > > Key: IGNITE-2022 > URL: https://issues.apache.org/jira/browse/IGNITE-2022 > Project: Ignite > Issue Type: Sub-task > Components: interop >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Need to add tests for the components that can be tested locally, without > establishing connection to a node. Here is the list of such a components: > 1. Configuration. > 2. ConnectionInfo. > 3. Parser. > 5. ApplicationDataBuffer. > 4. Row. > 6. Cursor. > 7. Utility. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-2021) CPP: Create test project for ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-2021: --- Assignee: Igor Sapego (was: Vladimir Ozerov) > CPP: Create test project for ODBC driver. > - > > Key: IGNITE-2021 > URL: https://issues.apache.org/jira/browse/IGNITE-2021 > Project: Ignite > Issue Type: Sub-task > Components: interop >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Need to implement tests sub-project for ODBC driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2021) CPP: Create test project for ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2021: Component/s: (was: interop) odbc > CPP: Create test project for ODBC driver. > - > > Key: IGNITE-2021 > URL: https://issues.apache.org/jira/browse/IGNITE-2021 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Need to implement tests sub-project for ODBC driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2022) CPP: Add local tests for ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2022: Component/s: (was: interop) odbc > CPP: Add local tests for ODBC driver. > - > > Key: IGNITE-2022 > URL: https://issues.apache.org/jira/browse/IGNITE-2022 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Need to add tests for the components that can be tested locally, without > establishing connection to a node. Here is the list of such a components: > 1. Configuration. > 2. ConnectionInfo. > 3. Parser. > 5. ApplicationDataBuffer. > 4. Row. > 6. Cursor. > 7. Utility. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2044) CPP: Fix bugs revealed by the ODBC tests.
[ https://issues.apache.org/jira/browse/IGNITE-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2044: Component/s: (was: interop) odbc > CPP: Fix bugs revealed by the ODBC tests. > - > > Key: IGNITE-2044 > URL: https://issues.apache.org/jira/browse/IGNITE-2044 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Number of bugs have been found during tests implementation (See IGNITE-2022). > Need to fix them. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1786) Need to implement ODBC driver for Ignite
[ https://issues.apache.org/jira/browse/IGNITE-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1786: Component/s: (was: clients) odbc > Need to implement ODBC driver for Ignite > > > Key: IGNITE-1786 > URL: https://issues.apache.org/jira/browse/IGNITE-1786 > Project: Ignite > Issue Type: New Feature > Components: odbc >Reporter: Dmitriy Setrakyan >Assignee: Igor Sapego > Fix For: 1.6 > > > # We have a C++ API for Ignite which starts JVM internally. Probably we can > just add that ODBC API there. > # Another approach is to implement really separate driver and a network > server on java side which will interact with each other. > The first one is simpler and probably more effective, but heavyweight. The > second one is probably slower but but more lightweight. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2045) Make message handling by OdbcProcessor synchronous.
[ https://issues.apache.org/jira/browse/IGNITE-2045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2045: Component/s: (was: interop) odbc > Make message handling by OdbcProcessor synchronous. > --- > > Key: IGNITE-2045 > URL: https://issues.apache.org/jira/browse/IGNITE-2045 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Currently OdbcProcessor implementation is asynchronous. It seems like this is > an unnecessary overhead and should be removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2046) CPP: Implement catalog ODBC API functions
[
https://issues.apache.org/jira/browse/IGNITE-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2046:
Component/s: (was: interop)
odbc
> CPP: Implement catalog ODBC API functions
> -
>
> Key: IGNITE-2046
> URL: https://issues.apache.org/jira/browse/IGNITE-2046
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> Such API functions is often used by the data analyzing software to retrieve
> information about columns, tables and supported data types.
> Here is the list of functions that need to be supported:
> - {{SQLColumns}}
> - {{SQLTables}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2060) CPP: Implement access to the metadata for result sets of the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2060:
Component/s: (was: interop)
odbc
> CPP: Implement access to the metadata for result sets of the ODBC driver.
> --
>
> Key: IGNITE-2060
> URL: https://issues.apache.org/jira/browse/IGNITE-2060
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This type of API functions is often used by the data analyzing software to
> retrieve information about columns, tables and supported data types.
> Here is the list of functions that need to be supported:
> - {{SQLColAttribute}}
> - {{SQLDescribeCol}}
> - {{SQLRowCount}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2059) CPP: Implement basic support of the params for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2059:
Component/s: (was: interop)
odbc
> CPP: Implement basic support of the params for the ODBC driver.
> ---
>
> Key: IGNITE-2059
> URL: https://issues.apache.org/jira/browse/IGNITE-2059
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> We need to provide basic API for parameters binding.
> Here is the list of functions that need to be supported:
> - {{SQLBindParameter}}
> - {{SQLNumParams}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2061) CPP: Implement obtaining of diagnostic information for ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2061:
Component/s: (was: interop)
odbc
> CPP: Implement obtaining of diagnostic information for ODBC driver.
> ---
>
> Key: IGNITE-2061
> URL: https://issues.apache.org/jira/browse/IGNITE-2061
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> These API functions used by user to retrieve diagnostic information, such as
> error or warning messages.
> Here is the list of functions that need to be supported:
> - {{SQLGetDiagField}}
> - {{SQLGetDiagRec}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2062) CPP: Implement support of Linux OS family for the ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2062: Component/s: (was: interop) odbc > CPP: Implement support of Linux OS family for the ODBC driver. > -- > > Key: IGNITE-2062 > URL: https://issues.apache.org/jira/browse/IGNITE-2062 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > ODBC driver should be buildable and usable on the Linux-based OS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2062) CPP: Implement support of Linux OS family for the ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2062: Issue Type: Task (was: Sub-task) Parent: (was: IGNITE-1786) > CPP: Implement support of Linux OS family for the ODBC driver. > -- > > Key: IGNITE-2062 > URL: https://issues.apache.org/jira/browse/IGNITE-2062 > Project: Ignite > Issue Type: Task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > ODBC driver should be buildable and usable on the Linux-based OS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2130) CPP: Implement basic support of SQLForeignKeys API call for ODBC driver.
Igor Sapego created IGNITE-2130:
---
Summary: CPP: Implement basic support of SQLForeignKeys API call
for ODBC driver.
Key: IGNITE-2130
URL: https://issues.apache.org/jira/browse/IGNITE-2130
Project: Ignite
Issue Type: Sub-task
Components: odbc
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.6
It seems like Tableu uses {{SQLForeignKeys}} call when user tries to add new
table in set. It needs to be implemented to provide valid data on call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2130) CPP: Implement basic support of SQLForeignKeys API call for ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051308#comment-15051308
]
Igor Sapego commented on IGNITE-2130:
-
Current approach is to return empty row. This is valid result, and it is easy
to implement. For Tableu it should not be critical that we do not provide real
foreign keys.
> CPP: Implement basic support of SQLForeignKeys API call for ODBC driver.
>
>
> Key: IGNITE-2130
> URL: https://issues.apache.org/jira/browse/IGNITE-2130
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> It seems like Tableu uses {{SQLForeignKeys}} call when user tries to add new
> table in set. It needs to be implemented to provide valid data on call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2130) CPP: Implement basic support of SQLForeignKeys API call for ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051315#comment-15051315
]
Igor Sapego commented on IGNITE-2130:
-
Merged to parent development branch.
> CPP: Implement basic support of SQLForeignKeys API call for ODBC driver.
>
>
> Key: IGNITE-2130
> URL: https://issues.apache.org/jira/browse/IGNITE-2130
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> It seems like Tableu uses {{SQLForeignKeys}} call when user tries to add new
> table in set. It needs to be implemented to provide valid data on call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (IGNITE-2082) Documentationd for C++/.Net missed in fabric binary package
[ https://issues.apache.org/jira/browse/IGNITE-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-2082: --- Assignee: Igor Sapego (was: Sergey Kozlov) > Documentationd for C++/.Net missed in fabric binary package > --- > > Key: IGNITE-2082 > URL: https://issues.apache.org/jira/browse/IGNITE-2082 > Project: Ignite > Issue Type: Bug > Components: interop >Reporter: Sergey Kozlov >Assignee: Igor Sapego >Priority: Critical > Fix For: 1.5 > > > There's no documentation generated by Doxygen for /platforms/cpp and > platforms/dotnet in Apache Ignite fabric binary package -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2082) Documentationd for C++/.Net missed in fabric binary package
[ https://issues.apache.org/jira/browse/IGNITE-2082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052910#comment-15052910 ] Igor Sapego commented on IGNITE-2082: - Sergey, fixed. > Documentationd for C++/.Net missed in fabric binary package > --- > > Key: IGNITE-2082 > URL: https://issues.apache.org/jira/browse/IGNITE-2082 > Project: Ignite > Issue Type: Bug > Components: interop >Reporter: Sergey Kozlov >Assignee: Igor Sapego >Priority: Critical > Fix For: 1.5 > > > There's no documentation generated by Doxygen for /platforms/cpp and > platforms/dotnet in Apache Ignite fabric binary package -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2060) CPP: Implement access to the metadata for result sets of the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15053038#comment-15053038
]
Igor Sapego commented on IGNITE-2060:
-
Merged to parent branch.
> CPP: Implement access to the metadata for result sets of the ODBC driver.
> --
>
> Key: IGNITE-2060
> URL: https://issues.apache.org/jira/browse/IGNITE-2060
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This type of API functions is often used by the data analyzing software to
> retrieve information about columns, tables and supported data types.
> Here is the list of functions that need to be supported:
> - {{SQLColAttribute}}
> - {{SQLDescribeCol}}
> - {{SQLRowCount}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2140) Simplify ODBC command handler.
Igor Sapego created IGNITE-2140:
---
Summary: Simplify ODBC command handler.
Key: IGNITE-2140
URL: https://issues.apache.org/jira/browse/IGNITE-2140
Project: Ignite
Issue Type: Sub-task
Components: odbc
Reporter: Igor Sapego
Assignee: Igor Sapego
Handlers logic in {{GridOdbcProcessor}} is overly complicated right now.
Current design implies that there can be several different command handlers but
there are currently only one - {{GridOdbcQueryCommandHandler}}.
The design should be simplified to use one exact command processor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2141) Cleanup ODBC configuration.
Igor Sapego created IGNITE-2141:
---
Summary: Cleanup ODBC configuration.
Key: IGNITE-2141
URL: https://issues.apache.org/jira/browse/IGNITE-2141
Project: Ignite
Issue Type: Sub-task
Components: odbc
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.6
Currently {{OdbcConfiguration}} contatins a lot of dead code. It should be
removed.
Also, currenty {{OdbcConfiguration#isEnabled}} used to determine if ODBC is
enabled which seems unnecessary - just check for presence of the
{{OdbcConfiguration}} itself to find out whether ODBC is enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2142) CPP: Move ODBC MSVS projects to separate solution.
Igor Sapego created IGNITE-2142: --- Summary: CPP: Move ODBC MSVS projects to separate solution. Key: IGNITE-2142 URL: https://issues.apache.org/jira/browse/IGNITE-2142 Project: Ignite Issue Type: Sub-task Components: odbc Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.6 Currently ODBC project are included in general CPP solution. Move them to separate solution for the ODBC. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
