[jira] [Created] (IGNITE-2242) CPP: Implement SQLGetData function for the ODBC driver.
Igor Sapego created IGNITE-2242: --- Summary: CPP: Implement SQLGetData function for the ODBC driver. Key: IGNITE-2242 URL: https://issues.apache.org/jira/browse/IGNITE-2242 Project: Ignite Issue Type: Task Components: odbc Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.6 This function listed in the [ODBC Core Interface Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2244) CPP: Implement Connection attributes manipulation for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2244:
Description:
This feature listed in the [ODBC Core Interface
Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
and should be implemented for our driver.
The list of functions that should be implemented:
- {{SQLGetConnectAttr}}
- {{SQLSetConnectAttr}}
The minimum list of attributes that should be supported:
- {{SQL_ATTR_ACCESS_MODE}}
- {{SQL_ATTR_ODBC_CURSORS}}
- {{SQL_ATTR_QUIET_MODE}}
- {{SQL_ATTR_TRACE}}
- {{SQL_ATTR_TRACEFILE}}
- {{SQL_ATTR_TRANSLATE_LIB}}
- {{SQL_ATTR_TRANSLATE_OPTION}}
was:
This feature listed in the [ODBC Core Interface
Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
and should be implemented for our driver.
The list of functions that should be implemented:
- {{SQLGetEnvAttr}}
- {{SQLSetEnvAttr}}
The minimum list of attributes that should be supported:
- {{SQL_ATTR_ACCESS_MODE}}
- {{SQL_ATTR_ACCESS_MODE}}
- {{SQL_ATTR_ACCESS_MODE}}
> CPP: Implement Connection attributes manipulation for the ODBC driver.
> --
>
> Key: IGNITE-2244
> URL: https://issues.apache.org/jira/browse/IGNITE-2244
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
> The list of functions that should be implemented:
> - {{SQLGetConnectAttr}}
> - {{SQLSetConnectAttr}}
> The minimum list of attributes that should be supported:
> - {{SQL_ATTR_ACCESS_MODE}}
> - {{SQL_ATTR_ODBC_CURSORS}}
> - {{SQL_ATTR_QUIET_MODE}}
> - {{SQL_ATTR_TRACE}}
> - {{SQL_ATTR_TRACEFILE}}
> - {{SQL_ATTR_TRANSLATE_LIB}}
> - {{SQL_ATTR_TRANSLATE_OPTION}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2244) CPP: Implement Connection attributes manipulation for the ODBC driver.
Igor Sapego created IGNITE-2244:
---
Summary: CPP: Implement Connection attributes manipulation for the
ODBC driver.
Key: IGNITE-2244
URL: https://issues.apache.org/jira/browse/IGNITE-2244
Project: Ignite
Issue Type: Task
Components: odbc
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.6
This feature listed in the [ODBC Core Interface
Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
and should be implemented for our driver.
The list of functions that should be implemented:
- {{SQLGetEnvAttr}}
- {{SQLSetEnvAttr}}
The minimum list of attributes that should be supported:
- {{SQL_ATTR_ACCESS_MODE}}
- {{SQL_ATTR_ACCESS_MODE}}
- {{SQL_ATTR_ACCESS_MODE}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2241) CPP: Implement SQLGetTypeInfo function for the ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2241: Summary: CPP: Implement SQLGetTypeInfo function for the ODBC driver. (was: CPP: Implement SQLGEtTypeInfo function for the ODBC driver.) > CPP: Implement SQLGetTypeInfo function for the ODBC driver. > --- > > Key: IGNITE-2241 > URL: https://issues.apache.org/jira/browse/IGNITE-2241 > Project: Ignite > Issue Type: Task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > This function is listed in the [ODBC Core Interface > Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] > and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2245) CPP: Implement Statement attributes manipulation for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068801#comment-15068801
]
Igor Sapego commented on IGNITE-2245:
-
Following attributes are already implemented:
- {{SQL_ATTR_APP_PARAM_DESC}}
- {{SQL_ATTR_APP_ROW_DESC}}
- {{SQL_ATTR_IMP_PARAM_DESC}}
- {{SQL_ATTR_IMP_ROW_DESC}}
- {{SQL_ATTR_PARAM_BIND_OFFSET_PTR}}
- {{SQL_ATTR_ROW_ARRAY_SIZE}}
- {{SQL_ATTR_ROW_BIND_OFFSET_PTR}}
- {{SQL_ATTR_ROW_BIND_TYPE}}
- {{SQL_ATTR_ROW_STATUS_PTR}}
- {{SQL_ATTR_ROWS_FETCHED_PTR}}
Need to implement:
- {{SQL_ATTR_METADATA_ID}}
- {{SQL_ATTR_NOSCAN}}
- {{SQL_ATTR_PARAM_BIND_TYPE}}
- {{SQL_ATTR_PARAM_OPERATION_PTR}}
- {{SQL_ATTR_PARAM_STATUS_PTR}}
- {{SQL_ATTR_PARAMS_PROCESSED_PTR}}
- {{SQL_ATTR_PARAMSET_SIZE}}
> CPP: Implement Statement attributes manipulation for the ODBC driver.
> -
>
> Key: IGNITE-2245
> URL: https://issues.apache.org/jira/browse/IGNITE-2245
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
> The list of functions that should be implemented:
> - {{SQLGetStmtAttr}}
> - {{SQLSetStmtAttr}}
> The minimum list of attributes that should be supported:
> - {{SQL_ATTR_APP_PARAM_DESC}}
> - {{SQL_ATTR_APP_ROW_DESC}}
> - {{SQL_ATTR_IMP_PARAM_DESC}}
> - {{SQL_ATTR_IMP_ROW_DESC}}
> - {{SQL_ATTR_METADATA_ID}}
> - {{SQL_ATTR_NOSCAN}}
> - {{SQL_ATTR_PARAM_BIND_OFFSET_PTR}}
> - {{SQL_ATTR_PARAM_BIND_TYPE}}
> - {{SQL_ATTR_PARAM_OPERATION_PTR}}
> - {{SQL_ATTR_PARAM_STATUS_PTR}}
> - {{SQL_ATTR_PARAMS_PROCESSED_PTR}}
> - {{SQL_ATTR_PARAMSET_SIZE}}
> - {{SQL_ATTR_ROW_ARRAY_SIZE}}
> - {{SQL_ATTR_ROW_BIND_OFFSET_PTR}}
> - {{SQL_ATTR_ROW_BIND_TYPE}}
> - {{SQL_ATTR_ROW_STATUS_PTR}}
> - {{SQL_ATTR_ROWS_FETCHED_PTR}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2247) CPP: Implement error handling for the ODBC driver.
Igor Sapego created IGNITE-2247:
---
Summary: CPP: Implement error handling for the ODBC driver.
Key: IGNITE-2247
URL: https://issues.apache.org/jira/browse/IGNITE-2247
Project: Ignite
Issue Type: Task
Components: odbc
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.6
This feature listed in the [ODBC Core Interface
Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
and should be implemented for our driver.
The list of functions that should be implemented:
- {{SQLGetDiagField}}
- {{SQLGetDiagRec}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2239) CPP: Implement SQLConnect function for the ODBC driver.
Igor Sapego created IGNITE-2239: --- Summary: CPP: Implement SQLConnect function for the ODBC driver. Key: IGNITE-2239 URL: https://issues.apache.org/jira/browse/IGNITE-2239 Project: Ignite Issue Type: Task Components: odbc Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.6 This function is listed in the [ODBC Core Interface Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2305) DEVNOTES.txt should contain infornation about platform build.
[ https://issues.apache.org/jira/browse/IGNITE-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2305: Assignee: Anton Vinogradov (was: Igor Sapego) > DEVNOTES.txt should contain infornation about platform build. > - > > Key: IGNITE-2305 > URL: https://issues.apache.org/jira/browse/IGNITE-2305 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Blocker > Fix For: 1.5 > > > DEVNOTES.txt should explain how to build Ignite Dotnet & Cpp clients. > It should be similar to "Ignite Fabric Maven Build Instructions" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-2230) CPP: Implement "Bind offset" feature for the ODBC driver.
Igor Sapego created IGNITE-2230: --- Summary: CPP: Implement "Bind offset" feature for the ODBC driver. Key: IGNITE-2230 URL: https://issues.apache.org/jira/browse/IGNITE-2230 Project: Ignite Issue Type: Task Components: odbc Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.6 This feature listed in the [ODBC Core Interface Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] and should be implemented for our driver. -- 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 happens 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
{{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.
> 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 happens 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 happens often.
3. Consider replacing this class with 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
{{InteropUnpooledMemory}} instances construction happens 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
> 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 happens often.
> 3. Consider replacing this class with 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 happens often.
3. Consider replacing this class with two classes: read/write memory and read
only memory. It makes sense because Input streams do not modify memory they
operate on. That 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
{{InteropUnpooledMemory}} instances construction happens often.
3. Consider replacing this class with 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
> 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 happens often.
> 3. Consider replacing this class with two classes: read/write memory and read
> only memory. It makes sense because Input streams do not modify memory they
> operate on. That 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-2222) CPP: Implement Date data type support for binary protocol.
[ https://issues.apache.org/jira/browse/IGNITE-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-: Description: It is need to implement date data type support because some SQL queries return data of that type and we need to be able to deserialize it on the C++ client side. (was: Date data type support needs to be implemented because some SQL queries return data of that type and we need to be able to deserialize it on the C++ client side.) > CPP: Implement Date data type support for binary protocol. > -- > > Key: IGNITE- > URL: https://issues.apache.org/jira/browse/IGNITE- > Project: Ignite > Issue Type: Bug > Components: interop >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > It is need to implement date data type support because some SQL queries > return data of that type and we need to be able to deserialize it on the C++ > client side. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2230) CPP: Implement "Bind offset" feature for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068099#comment-15068099
]
Igor Sapego commented on IGNITE-2230:
-
This feature implemented by supporting attributes
{{SQL_ATTR_ROW_BIND_OFFSET_PTR}} and {{SQL_ATTR_PARAM_BIND_OFFSET_PTR}} for
functions {{SQLSetStmtAttr}} and {{SQLGetStmtAttr}}. This attributes later
transferred to {{ApplicationDataBuffer}} class during binding to be used to
access underlying data.
> CPP: Implement "Bind offset" feature for the ODBC driver.
> -
>
> Key: IGNITE-2230
> URL: https://issues.apache.org/jira/browse/IGNITE-2230
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2239) CPP: Implement SQLConnect function for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068320#comment-15068320
]
Igor Sapego edited comment on IGNITE-2239 at 12/22/15 4:11 PM:
---
Implemented as follows:
- If the {{ServerName}} argument is equals default DSN name then trying to
establish connection with default parameters.
- If the {{ServerName}} argument is not equals default DSN name then return
error.
- All function parameters except of {{ServerName}}, {{ServerNameLength}} and
{{ConnectionHandle}} are ignored.
was (Author: isapego):
Implemented as follows:
- If the {{ServerName}} argument is equals default DSN name then trying to
establish connection with default parameters.
- If the {{ServerName}} argument is not equals default DSN name then return
error.
- All function parameters except of {{ServerName}} and {{ConnectionHandle}} are
ignored.
> CPP: Implement SQLConnect function for the ODBC driver.
> ---
>
> Key: IGNITE-2239
> URL: https://issues.apache.org/jira/browse/IGNITE-2239
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This function is listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-2240) CPP: Implement SQLEndTran function for the ODBC driver.
Igor Sapego created IGNITE-2240: --- Summary: CPP: Implement SQLEndTran function for the ODBC driver. Key: IGNITE-2240 URL: https://issues.apache.org/jira/browse/IGNITE-2240 Project: Ignite Issue Type: Task Components: odbc Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.6 This function listed in the [ODBC Core Interface Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-2239) CPP: Implement SQLConnect function for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068320#comment-15068320
]
Igor Sapego commented on IGNITE-2239:
-
Implemented as follows:
- If the {{ServerName}} argument is equals default DSN name then trying to
establish connection with default parameters.
- If the {{ServerName}} argument is not equals default DSN name then return
error.
- All function parameters except of {{ServerName}} and {{ConnectionHandle}} are
ignored.
> CPP: Implement SQLConnect function for the ODBC driver.
> ---
>
> Key: IGNITE-2239
> URL: https://issues.apache.org/jira/browse/IGNITE-2239
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This function is listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2240) CPP: Implement SQLEndTran function for the ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15068369#comment-15068369 ] Igor Sapego commented on IGNITE-2240: - It is not necessary to implement true transactions; therefore, the application cannot specify SQL_ROLLBACK nor SQL_AUTOCOMMIT_OFF for the SQL_ATTR_AUTOCOMMIT connection attribute. So we only need to support SQL_COMMIT. > CPP: Implement SQLEndTran function for the ODBC driver. > --- > > Key: IGNITE-2240 > URL: https://issues.apache.org/jira/browse/IGNITE-2240 > Project: Ignite > Issue Type: Task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > This function listed in the [ODBC Core Interface > Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] > and should be implemented for our driver. -- 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=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=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=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] [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=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] [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=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] [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-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] [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] [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=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] [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:
Issue Type: Sub-task (was: Task)
Parent: IGNITE-1786
> 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] [Created] (IGNITE-2371) ODBC driver does not return any data with SQLColumns and SQLTables calls.
Igor Sapego created IGNITE-2371:
---
Summary: ODBC driver does not return any data with SQLColumns and
SQLTables calls.
Key: IGNITE-2371
URL: https://issues.apache.org/jira/browse/IGNITE-2371
Project: Ignite
Issue Type: Sub-task
Components: odbc
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.6
When Tableau calls {{SQLColumns}} or {{SQLTables}} there is no data in result
set even though values which Tableau uses are returned by previous calls to
ODBC functions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2223) CPP: ODBC queries sometimes return wrong types for columns in metadata.
[ https://issues.apache.org/jira/browse/IGNITE-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2223: Issue Type: Sub-task (was: Bug) Parent: IGNITE-1786 > CPP: ODBC queries sometimes return wrong types for columns in metadata. > --- > > Key: IGNITE-2223 > URL: https://issues.apache.org/jira/browse/IGNITE-2223 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Some SQL queries return wrong types in metadata. For example, if query result > set has column of type "Decimal" it will be transferred as "Long" instead. As > a result, value can not be read in the application data buffer during row > fetch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2165) CPP: Tableau displays textual data in wrong locale.
[ https://issues.apache.org/jira/browse/IGNITE-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2165: Issue Type: Sub-task (was: Bug) Parent: IGNITE-1786 > CPP: Tableau displays textual data in wrong locale. > --- > > Key: IGNITE-2165 > URL: https://issues.apache.org/jira/browse/IGNITE-2165 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > Attachments: screenshot-1.png > > > By some reason Tableau displays strings in wrong locale when using our ODBC > driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2163) CPP: ODBC driver supported version should be upgraded to 3.x
[ https://issues.apache.org/jira/browse/IGNITE-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2163: Issue Type: Sub-task (was: Task) Parent: IGNITE-1786 > CPP: ODBC driver supported version should be upgraded to 3.x > > > Key: IGNITE-2163 > URL: https://issues.apache.org/jira/browse/IGNITE-2163 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Currently our implementation of the ODBC driver states that it supports ODBC > standard version 2.0. It seems that many features that Tablue uses are not > supported in this version of the ODBC. So we need to set our version to 3.x > and make sure it works. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2230) CPP: Implement "Bind offset" feature for the ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2230: Issue Type: Sub-task (was: Task) Parent: IGNITE-1786 > CPP: Implement "Bind offset" feature for the ODBC driver. > - > > Key: IGNITE-2230 > URL: https://issues.apache.org/jira/browse/IGNITE-2230 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > This feature listed in the [ODBC Core Interface > Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] > and should be implemented for our driver. -- 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: Sub-task (was: Task) Parent: 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: 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] [Commented] (IGNITE-2371) ODBC driver does not return any data with SQLColumns and SQLTables calls.
[
https://issues.apache.org/jira/browse/IGNITE-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15096105#comment-15096105
]
Igor Sapego commented on IGNITE-2371:
-
An issue caused by quotation marks around the schema that should be removed
before cache lookup. The other issue is two part table names in format
{{"schema".table}} which should also be parsed in an appropriate way to extract
table name and schema.
> ODBC driver does not return any data with SQLColumns and SQLTables calls.
> -
>
> Key: IGNITE-2371
> URL: https://issues.apache.org/jira/browse/IGNITE-2371
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> When Tableau calls {{SQLColumns}} or {{SQLTables}} there is no data in result
> set even though values which Tableau uses are returned by previous calls to
> ODBC functions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-2371) ODBC driver does not return any data with SQLColumns and SQLTables calls.
[
https://issues.apache.org/jira/browse/IGNITE-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego resolved IGNITE-2371.
-
Resolution: Fixed
Merged to parent development branch.
> ODBC driver does not return any data with SQLColumns and SQLTables calls.
> -
>
> Key: IGNITE-2371
> URL: https://issues.apache.org/jira/browse/IGNITE-2371
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> When Tableau calls {{SQLColumns}} or {{SQLTables}} there is no data in result
> set even though values which Tableau uses are returned by previous calls to
> ODBC functions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2223) CPP: ODBC queries sometimes return wrong types for columns in metadata.
[ https://issues.apache.org/jira/browse/IGNITE-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15094660#comment-15094660 ] Igor Sapego commented on IGNITE-2223: - After a closer look I found out that the issue is not in wrong type, returned by the metadata queries. The real issue is that on the C++ side we does not support Decimal type yet so we don't know how to read it which causes an error during row fetch. > CPP: ODBC queries sometimes return wrong types for columns in metadata. > --- > > Key: IGNITE-2223 > URL: https://issues.apache.org/jira/browse/IGNITE-2223 > Project: Ignite > Issue Type: Bug > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Some SQL queries return wrong types in metadata. For example, if query result > set has column of type "Decimal" it will be transferred as "Long" instead. As > a result, value can not be read in the application data buffer during row > fetch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2223) CPP: ODBC queries sometimes return wrong types for columns in metadata.
[ https://issues.apache.org/jira/browse/IGNITE-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15094660#comment-15094660 ] Igor Sapego edited comment on IGNITE-2223 at 1/12/16 7:59 PM: -- After a closer look I found out that the issue is not in wrong type, returned by the metadata queries. The real issue is that on the C++ side we do not support Decimal type yet so we don't know how to read it which causes an error during row fetch. was (Author: isapego): After a closer look I found out that the issue is not in wrong type, returned by the metadata queries. The real issue is that on the C++ side we does not support Decimal type yet so we don't know how to read it which causes an error during row fetch. > CPP: ODBC queries sometimes return wrong types for columns in metadata. > --- > > Key: IGNITE-2223 > URL: https://issues.apache.org/jira/browse/IGNITE-2223 > Project: Ignite > Issue Type: Bug > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Some SQL queries return wrong types in metadata. For example, if query result > set has column of type "Decimal" it will be transferred as "Long" instead. As > a result, value can not be read in the application data buffer during row > fetch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (IGNITE-2223) CPP: ODBC queries sometimes return wrong types for columns in metadata.
[ https://issues.apache.org/jira/browse/IGNITE-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15094660#comment-15094660 ] Igor Sapego edited comment on IGNITE-2223 at 1/12/16 8:00 PM: -- After a closer look I found out that the issue is not in wrong type, returned by the metadata queries. The real issue is that on the C++ side we do not support Decimal type yet so we don't know how to read it, which causes an error during row fetch. was (Author: isapego): After a closer look I found out that the issue is not in wrong type, returned by the metadata queries. The real issue is that on the C++ side we do not support Decimal type yet so we don't know how to read it which causes an error during row fetch. > CPP: ODBC queries sometimes return wrong types for columns in metadata. > --- > > Key: IGNITE-2223 > URL: https://issues.apache.org/jira/browse/IGNITE-2223 > Project: Ignite > Issue Type: Bug > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Some SQL queries return wrong types in metadata. For example, if query result > set has column of type "Decimal" it will be transferred as "Long" instead. As > a result, value can not be read in the application data buffer during row > fetch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2223) CPP: ODBC queries sometimes return wrong types for columns in metadata.
[ https://issues.apache.org/jira/browse/IGNITE-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2223: Description: Some SQL queries return wrong types in metadata. For example, if query result set has column of type "Decimal" it will be transferred as "Long" instead. As a result, value can not be read in the application data buffer during row fetch. (was: Some SQL queries return wrong types in metadata. For example, if query result set has column of type "Decimal" it will be transferred as "Long" instead.) > CPP: ODBC queries sometimes return wrong types for columns in metadata. > --- > > Key: IGNITE-2223 > URL: https://issues.apache.org/jira/browse/IGNITE-2223 > Project: Ignite > Issue Type: Bug > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Some SQL queries return wrong types in metadata. For example, if query result > set has column of type "Decimal" it will be transferred as "Long" instead. As > a result, value can not be read in the application data buffer during row > fetch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2245) ODBC: Implement Statement attributes manipulation for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2245:
Summary: ODBC: Implement Statement attributes manipulation for the ODBC
driver. (was: CPP: Implement Statement attributes manipulation for the ODBC
driver.)
> ODBC: Implement Statement attributes manipulation for the ODBC driver.
> --
>
> Key: IGNITE-2245
> URL: https://issues.apache.org/jira/browse/IGNITE-2245
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.7
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
> The list of functions that should be implemented:
> - {{SQLGetStmtAttr}}
> - {{SQLSetStmtAttr}}
> The minimum list of attributes that should be supported:
> - {{SQL_ATTR_APP_PARAM_DESC}}
> - {{SQL_ATTR_APP_ROW_DESC}}
> - {{SQL_ATTR_IMP_PARAM_DESC}}
> - {{SQL_ATTR_IMP_ROW_DESC}}
> - {{SQL_ATTR_METADATA_ID}}
> - {{SQL_ATTR_NOSCAN}}
> - {{SQL_ATTR_PARAM_BIND_OFFSET_PTR}}
> - {{SQL_ATTR_PARAM_BIND_TYPE}}
> - {{SQL_ATTR_PARAM_OPERATION_PTR}}
> - {{SQL_ATTR_PARAM_STATUS_PTR}}
> - {{SQL_ATTR_PARAMS_PROCESSED_PTR}}
> - {{SQL_ATTR_PARAMSET_SIZE}}
> - {{SQL_ATTR_ROW_ARRAY_SIZE}}
> - {{SQL_ATTR_ROW_BIND_OFFSET_PTR}}
> - {{SQL_ATTR_ROW_BIND_TYPE}}
> - {{SQL_ATTR_ROW_STATUS_PTR}}
> - {{SQL_ATTR_ROWS_FETCHED_PTR}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2244) ODBC: Implement Connection attributes manipulation for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2244:
Summary: ODBC: Implement Connection attributes manipulation for the ODBC
driver. (was: CPP: Implement Connection attributes manipulation for the ODBC
driver.)
> ODBC: Implement Connection attributes manipulation for the ODBC driver.
> ---
>
> Key: IGNITE-2244
> URL: https://issues.apache.org/jira/browse/IGNITE-2244
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.7
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
> The list of functions that should be implemented:
> - {{SQLGetConnectAttr}}
> - {{SQLSetConnectAttr}}
> The minimum list of attributes that should be supported:
> - {{SQL_ATTR_ACCESS_MODE}}
> - {{SQL_ATTR_ODBC_CURSORS}}
> - {{SQL_ATTR_QUIET_MODE}}
> - {{SQL_ATTR_TRACE}}
> - {{SQL_ATTR_TRACEFILE}}
> - {{SQL_ATTR_TRANSLATE_LIB}}
> - {{SQL_ATTR_TRANSLATE_OPTION}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2246) ODBC: Implement Descriptors support for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2246:
Summary: ODBC: Implement Descriptors support for the ODBC driver. (was:
CPP: Implement Descriptors support for the ODBC driver.)
> ODBC: Implement Descriptors support for the ODBC driver.
>
>
> Key: IGNITE-2246
> URL: https://issues.apache.org/jira/browse/IGNITE-2246
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.7
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
> This includes implementation of the following functions:
> - {{SQLCopyDesc}}
> - {{SQLGetDescField}}
> - {{SQLGetDescRec}}
> - {{SQLSetDescField}}
> - {{SQLSetDescRec}}
> Following header fields:
> - {{SQL_DESC_ALLOC_TYPE}}
> - {{SQL_DESC_ARRAY_SIZE}}
> - {{SQL_DESC_ARRAY_STATUS_PTR}}
> - {{SQL_DESC_BIND_OFFSET_PTR}}
> - {{SQL_DESC_BIND_TYPE}}
> - {{SQL_DESC_COUNT}}
> - {{SQL_DESC_ROWS_PROCESSED_PTR}}
> Following record fields:
> - {{SQL_DESC_BASE_COLUMN_NAME}}
> - {{SQL_DESC_CASE_SENSITIVE}}
> - {{SQL_DESC_CONCISE_TYPE}}
> - {{SQL_DESC_DATA_PTR}}
> - {{SQL_DESC_DATETIME_INTERVAL_ CODE}}
> - {{SQL_DESC_DATETIME_INTERVAL_ PRECISION}}
> - {{SQL_DESC_DISPLAY_SIZE}}
> - {{SQL_DESC_FIXED_PREC_SCALE}}
> - {{SQL_DESC_INDICATOR_PTR}}
> - {{SQL_DESC_LENGTH}}
> - {{SQL_DESC_LITERAL_PREFIX}}
> - {{SQL_DESC_LITERAL_SUFFIX}}
> - {{SQL_DESC_LOCAL_TYPE_NAME}}
> - {{SQL_DESC_NAME}}
> - {{SQL_DESC_NULLABLE}}
> - {{SQL_DESC_OCTET_LENGTH}}
> - {{SQL_DESC_OCTET_LENGTH_PTR}}
> - {{SQL_DESC_PARAMETER_TYPE}}
> - {{SQL_DESC_PRECISION}}
> - {{SQL_DESC_SCALE}}
> - {{SQL_DESC_SEARCHABLE}}
> - {{SQL_DESC_TYPE}}
> - {{SQL_DESC_TYPE_NAME}}
> - {{SQL_DESC_UNNAMED}}
> - {{SQL_DESC_UNSIGNED}}
> - {{SQL_DESC_UPDATABLE}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-1468) CPP: Support date-time in marshaller.
[ https://issues.apache.org/jira/browse/IGNITE-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego resolved IGNITE-1468. - Resolution: Duplicate Assignee: Vladimir Ozerov Fix Version/s: 1.6 Resolved by IGNITE-. > CPP: Support date-time in marshaller. > - > > Key: IGNITE-1468 > URL: https://issues.apache.org/jira/browse/IGNITE-1468 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.6 > > > We need to support date-time written on Java/.Net sides. Probably we will > have to introduce our own thin wrapper for this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1458) CPP: Implement transactions API.
[ https://issues.apache.org/jira/browse/IGNITE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego resolved IGNITE-1458. - Resolution: Duplicate Assignee: Igor Sapego Fix Version/s: 1.6 Resolved by IGNITE-2805. > CPP: Implement transactions API. > > > Key: IGNITE-1458 > URL: https://issues.apache.org/jira/browse/IGNITE-1458 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Igor Sapego >Priority: Critical > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (IGNITE-1443) CPP: Implement cache continuous queries.
[ https://issues.apache.org/jira/browse/IGNITE-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego reassigned IGNITE-1443: --- Assignee: Igor Sapego > CPP: Implement cache continuous queries. > > > Key: IGNITE-1443 > URL: https://issues.apache.org/jira/browse/IGNITE-1443 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Igor Sapego >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2238) ODBC: Implement basic cursor operations for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2238:
Summary: ODBC: Implement basic cursor operations for the ODBC driver.
(was: CPP: Implement basic cursor operations for the ODBC driver.)
> ODBC: Implement basic cursor operations for the ODBC driver.
>
>
> Key: IGNITE-2238
> URL: https://issues.apache.org/jira/browse/IGNITE-2238
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
> Fix For: 1.7
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver. It includes implementation of the
> following functions:
> - {{SQLCloseCursor}};
> - {{SQLGetCursorName}};
> - {{SQLSetCursorName}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-1458) CPP: Implement transactions API.
[ https://issues.apache.org/jira/browse/IGNITE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1458: Assignee: Vladimir Ozerov (was: Igor Sapego) > CPP: Implement transactions API. > > > Key: IGNITE-1458 > URL: https://issues.apache.org/jira/browse/IGNITE-1458 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.6 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1437) CPP: Implement SQL fields query.
[ https://issues.apache.org/jira/browse/IGNITE-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1437: Fix Version/s: (was: 1.7) 1.6 > CPP: Implement SQL fields query. > > > Key: IGNITE-1437 > URL: https://issues.apache.org/jira/browse/IGNITE-1437 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.5.0.final > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1437) CPP: Implement SQL fields query.
[ https://issues.apache.org/jira/browse/IGNITE-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego resolved IGNITE-1437. - Resolution: Duplicate Assignee: Vladimir Ozerov Fix Version/s: 1.7 Resolved by IGNITE-1647. > CPP: Implement SQL fields query. > > > Key: IGNITE-1437 > URL: https://issues.apache.org/jira/browse/IGNITE-1437 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.7 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1437) CPP: Implement SQL fields query.
[ https://issues.apache.org/jira/browse/IGNITE-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1437: Fix Version/s: (was: 1.6) 1.5.0.final > CPP: Implement SQL fields query. > > > Key: IGNITE-1437 > URL: https://issues.apache.org/jira/browse/IGNITE-1437 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.5.0.final > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (IGNITE-1438) CPP: Implement transactions API.
[ https://issues.apache.org/jira/browse/IGNITE-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego resolved IGNITE-1438. - Resolution: Duplicate Assignee: Vladimir Ozerov Fix Version/s: 1.7 Resolved by IGNITE-2805. > CPP: Implement transactions API. > > > Key: IGNITE-1438 > URL: https://issues.apache.org/jira/browse/IGNITE-1438 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.7 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1443) CPP: Implement cache continuous queries.
[ https://issues.apache.org/jira/browse/IGNITE-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1443: Fix Version/s: 1.7 > CPP: Implement cache continuous queries. > > > Key: IGNITE-1443 > URL: https://issues.apache.org/jira/browse/IGNITE-1443 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Igor Sapego >Priority: Critical > Fix For: 1.7 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-1443) CPP: Implement cache continuous queries.
[ https://issues.apache.org/jira/browse/IGNITE-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-1443: Assignee: Vladimir Ozerov (was: Igor Sapego) > CPP: Implement cache continuous queries. > > > Key: IGNITE-1443 > URL: https://issues.apache.org/jira/browse/IGNITE-1443 > Project: Ignite > Issue Type: Task > Components: platforms >Affects Versions: 1.1.4 >Reporter: Vladimir Ozerov >Assignee: Vladimir Ozerov >Priority: Critical > Fix For: 1.7 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3315) CPP: Add documentation for ContinuousQuery API
Igor Sapego created IGNITE-3315: --- Summary: CPP: Add documentation for ContinuousQuery API Key: IGNITE-3315 URL: https://issues.apache.org/jira/browse/IGNITE-3315 Project: Ignite Issue Type: Task Components: documentation, platforms Affects Versions: 1.6 Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.7 We are going to add CountinuousQuery API to Ignite C++ with IGNITE-1443 so we also need to add documentation section to readme.io on this topic. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3205) CPP: Ignite C++ can not be compiled with g++ 4.4.7
Igor Sapego created IGNITE-3205: --- Summary: CPP: Ignite C++ can not be compiled with g++ 4.4.7 Key: IGNITE-3205 URL: https://issues.apache.org/jira/browse/IGNITE-3205 Project: Ignite Issue Type: Bug Components: platforms Affects Versions: 1.6 Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 1.7 Ignite C++ can not be compiled with particular compiler version. Version details: ``` g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16) Copyright (C) 2010 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ``` -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-3205) CPP: Ignite C++ can not be compiled with g++ 4.4.7
[
https://issues.apache.org/jira/browse/IGNITE-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-3205:
Description:
Ignite C++ can not be compiled with particular compiler version. Version
details:
{noformat}
g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
{noformat}
was:
Ignite C++ can not be compiled with particular compiler version. Version
details:
```
g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```
> CPP: Ignite C++ can not be compiled with g++ 4.4.7
> --
>
> Key: IGNITE-3205
> URL: https://issues.apache.org/jira/browse/IGNITE-3205
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.7
>
>
> Ignite C++ can not be compiled with particular compiler version. Version
> details:
> {noformat}
> g++ (GCC) 4.4.7 20120313 (Red Hat 4.4.7-16)
> Copyright (C) 2010 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-2879) ODBC: Add support for Decimal type (SQL_NUMERIC_STRUCT).
[
https://issues.apache.org/jira/browse/IGNITE-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15311133#comment-15311133
]
Igor Sapego commented on IGNITE-2879:
-
In the end, I decided to implement my own solution which is not based on Java
classes but is compatible with them. It conststs of two classes -
{{BigInteger}} and {{Decimal}}. {{BigInteger}} class implements most of the
functionality, including multiplication, division, pow and so on, while the
{{Decimal}} class implemented as an {{BigInteger}} with a scale and only deals
with operations that could affect the scale of the decimal number. Only minimal
set of methods have been implemented which is needed to be able to deal with
adjustment of the scale of the Decimals as required by the ODBC. This set
contains of {{SetScale()}}, {{GetScale()}}, {{GetPrecision()}} and input/output
operators for the {{Decimal}} class. All other methods have been implemented in
order to achieve this functionality.
> ODBC: Add support for Decimal type (SQL_NUMERIC_STRUCT).
>
>
> Key: IGNITE-2879
> URL: https://issues.apache.org/jira/browse/IGNITE-2879
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Affects Versions: 1.5.0.final
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.7
>
>
> We need reasonable Decimal type support at least for the ODBC.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3355) CPP: Implement Compute::Call() for C++ client.
Igor Sapego created IGNITE-3355:
---
Summary: CPP: Implement Compute::Call() for C++ client.
Key: IGNITE-3355
URL: https://issues.apache.org/jira/browse/IGNITE-3355
Project: Ignite
Issue Type: Sub-task
Components: platforms
Affects Versions: 1.6
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.7
Need to implement {{Compute}} class with {{Compute::Call}} method.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (IGNITE-3330) CPP: Implement Cache::Invoke method.
Igor Sapego created IGNITE-3330:
---
Summary: CPP: Implement Cache::Invoke method.
Key: IGNITE-3330
URL: https://issues.apache.org/jira/browse/IGNITE-3330
Project: Ignite
Issue Type: Sub-task
Components: platforms
Affects Versions: 1.6
Reporter: Igor Sapego
Assignee: Igor Sapego
Fix For: 1.7
Implement {{Cache::Invoke}} method for the Ignite C++.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (IGNITE-3330) CPP: Implement Cache::Invoke method.
[
https://issues.apache.org/jira/browse/IGNITE-3330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15334430#comment-15334430
]
Igor Sapego commented on IGNITE-3330:
-
Current plan is to introduce module manager that can dynamically look up
functions in loaded modules and to ask user to register all invoke-jobs using
provided set of macros which are going to compile into a function with a
specific name that could be later accessed by the module manager. After that we
only need to somehow pass the identifier of the job to remote node together
with the serialized job instance and the argument. On the receiving node we are
going to read job identifier, perform job lookup using module manager and call
the job or throw an exception if there are no such job on the remote node.
Note that we don't know how to deserialize the invoke-job until we found it, so
actually we should not only register job when user registers it but also
register job deserializer.
> CPP: Implement Cache::Invoke method.
>
>
> Key: IGNITE-3330
> URL: https://issues.apache.org/jira/browse/IGNITE-3330
> Project: Ignite
> Issue Type: Sub-task
> Components: platforms
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.7
>
>
> Implement {{Cache::Invoke}} method for the Ignite C++.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (IGNITE-2247) CPP: Implement error handling for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego resolved IGNITE-2247.
-
Resolution: Duplicate
> CPP: Implement error handling for the ODBC driver.
> --
>
> Key: IGNITE-2247
> URL: https://issues.apache.org/jira/browse/IGNITE-2247
> Project: Ignite
> Issue Type: Task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
> The list of functions that should be implemented:
> - {{SQLGetDiagField}}
> - {{SQLGetDiagRec}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2242) CPP: Implement SQLGetData function for the ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2242: Issue Type: Sub-task (was: Task) Parent: IGNITE-1786 > CPP: Implement SQLGetData function for the ODBC driver. > --- > > Key: IGNITE-2242 > URL: https://issues.apache.org/jira/browse/IGNITE-2242 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > This function listed in the [ODBC Core Interface > Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] > and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2243) CPP: Implement Environment attributes manipulation for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2243:
Issue Type: Sub-task (was: Task)
Parent: IGNITE-1786
> CPP: Implement Environment attributes manipulation for the ODBC driver.
> ---
>
> Key: IGNITE-2243
> URL: https://issues.apache.org/jira/browse/IGNITE-2243
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
> The list of functions that should be implemented:
> - {{SQLGetEnvAttr}}
> - {{SQLSetEnvAttr}}
> The minimum list of attributes that should be supported:
> - {{SQL_ATTR_ODBC_VER}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2245) CPP: Implement Statement attributes manipulation for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2245:
Issue Type: Sub-task (was: Task)
Parent: IGNITE-1786
> CPP: Implement Statement attributes manipulation for the ODBC driver.
> -
>
> Key: IGNITE-2245
> URL: https://issues.apache.org/jira/browse/IGNITE-2245
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
> The list of functions that should be implemented:
> - {{SQLGetStmtAttr}}
> - {{SQLSetStmtAttr}}
> The minimum list of attributes that should be supported:
> - {{SQL_ATTR_APP_PARAM_DESC}}
> - {{SQL_ATTR_APP_ROW_DESC}}
> - {{SQL_ATTR_IMP_PARAM_DESC}}
> - {{SQL_ATTR_IMP_ROW_DESC}}
> - {{SQL_ATTR_METADATA_ID}}
> - {{SQL_ATTR_NOSCAN}}
> - {{SQL_ATTR_PARAM_BIND_OFFSET_PTR}}
> - {{SQL_ATTR_PARAM_BIND_TYPE}}
> - {{SQL_ATTR_PARAM_OPERATION_PTR}}
> - {{SQL_ATTR_PARAM_STATUS_PTR}}
> - {{SQL_ATTR_PARAMS_PROCESSED_PTR}}
> - {{SQL_ATTR_PARAMSET_SIZE}}
> - {{SQL_ATTR_ROW_ARRAY_SIZE}}
> - {{SQL_ATTR_ROW_BIND_OFFSET_PTR}}
> - {{SQL_ATTR_ROW_BIND_TYPE}}
> - {{SQL_ATTR_ROW_STATUS_PTR}}
> - {{SQL_ATTR_ROWS_FETCHED_PTR}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2244) CPP: Implement Connection attributes manipulation for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2244:
Issue Type: Sub-task (was: Task)
Parent: IGNITE-1786
> CPP: Implement Connection attributes manipulation for the ODBC driver.
> --
>
> Key: IGNITE-2244
> URL: https://issues.apache.org/jira/browse/IGNITE-2244
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
> The list of functions that should be implemented:
> - {{SQLGetConnectAttr}}
> - {{SQLSetConnectAttr}}
> The minimum list of attributes that should be supported:
> - {{SQL_ATTR_ACCESS_MODE}}
> - {{SQL_ATTR_ODBC_CURSORS}}
> - {{SQL_ATTR_QUIET_MODE}}
> - {{SQL_ATTR_TRACE}}
> - {{SQL_ATTR_TRACEFILE}}
> - {{SQL_ATTR_TRANSLATE_LIB}}
> - {{SQL_ATTR_TRANSLATE_OPTION}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2248) CPP: Implement obtaining the row-identifying column of tables for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2248:
Issue Type: Sub-task (was: Task)
Parent: IGNITE-1786
> CPP: Implement obtaining the row-identifying column of tables for the ODBC
> driver.
> --
>
> Key: IGNITE-2248
> URL: https://issues.apache.org/jira/browse/IGNITE-2248
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
> This means implementing obtaining the {{SQL_BEST_ROWID}} row-identifying
> column of tables, by calling {{SQLSpecialColumns}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (IGNITE-2241) CPP: Implement SQLGetTypeInfo function for the ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-2241: Issue Type: Sub-task (was: Task) Parent: IGNITE-1786 > CPP: Implement SQLGetTypeInfo function for the ODBC driver. > --- > > Key: IGNITE-2241 > URL: https://issues.apache.org/jira/browse/IGNITE-2241 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > This function is listed in the [ODBC Core Interface > Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] > and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (IGNITE-2246) CPP: Implement Descriptors support for the ODBC driver.
[
https://issues.apache.org/jira/browse/IGNITE-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-2246:
Issue Type: Sub-task (was: Task)
Parent: IGNITE-1786
> CPP: Implement Descriptors support for the ODBC driver.
> ---
>
> Key: IGNITE-2246
> URL: https://issues.apache.org/jira/browse/IGNITE-2246
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> This feature listed in the [ODBC Core Interface
> Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx]
> and should be implemented for our driver.
> This includes implementation of the following functions:
> - {{SQLCopyDesc}}
> - {{SQLGetDescField}}
> - {{SQLGetDescRec}}
> - {{SQLSetDescField}}
> - {{SQLSetDescRec}}
> Following header fields:
> - {{SQL_DESC_ALLOC_TYPE}}
> - {{SQL_DESC_ARRAY_SIZE}}
> - {{SQL_DESC_ARRAY_STATUS_PTR}}
> - {{SQL_DESC_BIND_OFFSET_PTR}}
> - {{SQL_DESC_BIND_TYPE}}
> - {{SQL_DESC_COUNT}}
> - {{SQL_DESC_ROWS_PROCESSED_PTR}}
> Following record fields:
> - {{SQL_DESC_BASE_COLUMN_NAME}}
> - {{SQL_DESC_CASE_SENSITIVE}}
> - {{SQL_DESC_CONCISE_TYPE}}
> - {{SQL_DESC_DATA_PTR}}
> - {{SQL_DESC_DATETIME_INTERVAL_ CODE}}
> - {{SQL_DESC_DATETIME_INTERVAL_ PRECISION}}
> - {{SQL_DESC_DISPLAY_SIZE}}
> - {{SQL_DESC_FIXED_PREC_SCALE}}
> - {{SQL_DESC_INDICATOR_PTR}}
> - {{SQL_DESC_LENGTH}}
> - {{SQL_DESC_LITERAL_PREFIX}}
> - {{SQL_DESC_LITERAL_SUFFIX}}
> - {{SQL_DESC_LOCAL_TYPE_NAME}}
> - {{SQL_DESC_NAME}}
> - {{SQL_DESC_NULLABLE}}
> - {{SQL_DESC_OCTET_LENGTH}}
> - {{SQL_DESC_OCTET_LENGTH_PTR}}
> - {{SQL_DESC_PARAMETER_TYPE}}
> - {{SQL_DESC_PRECISION}}
> - {{SQL_DESC_SCALE}}
> - {{SQL_DESC_SEARCHABLE}}
> - {{SQL_DESC_TYPE}}
> - {{SQL_DESC_TYPE_NAME}}
> - {{SQL_DESC_UNNAMED}}
> - {{SQL_DESC_UNSIGNED}}
> - {{SQL_DESC_UPDATABLE}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-2241) CPP: Implement SQLGetTypeInfo function for the ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego closed IGNITE-2241. --- > CPP: Implement SQLGetTypeInfo function for the ODBC driver. > --- > > Key: IGNITE-2241 > URL: https://issues.apache.org/jira/browse/IGNITE-2241 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > This function is listed in the [ODBC Core Interface > Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] > and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2142) CPP: Move ODBC MSVS projects to separate solution.
[ https://issues.apache.org/jira/browse/IGNITE-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego closed IGNITE-2142. --- > 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)
[jira] [Closed] (IGNITE-2140) Simplify ODBC command handler.
[
https://issues.apache.org/jira/browse/IGNITE-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego closed IGNITE-2140.
---
> 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
> Fix For: 1.6
>
>
> 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] [Closed] (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 closed IGNITE-2062. --- > 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] [Closed] (IGNITE-2371) ODBC driver does not return any data with SQLColumns and SQLTables calls.
[
https://issues.apache.org/jira/browse/IGNITE-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego closed IGNITE-2371.
---
> ODBC driver does not return any data with SQLColumns and SQLTables calls.
> -
>
> Key: IGNITE-2371
> URL: https://issues.apache.org/jira/browse/IGNITE-2371
> Project: Ignite
> Issue Type: Sub-task
> Components: odbc
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 1.6
>
>
> When Tableau calls {{SQLColumns}} or {{SQLTables}} there is no data in result
> set even though values which Tableau uses are returned by previous calls to
> ODBC functions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (IGNITE-2165) CPP: Tableau displays textual data in wrong locale.
[ https://issues.apache.org/jira/browse/IGNITE-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego closed IGNITE-2165. --- > CPP: Tableau displays textual data in wrong locale. > --- > > Key: IGNITE-2165 > URL: https://issues.apache.org/jira/browse/IGNITE-2165 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > Attachments: screenshot-1.png > > > By some reason Tableau displays strings in wrong locale when using our ODBC > driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2239) CPP: Implement SQLConnect function for the ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego closed IGNITE-2239. --- > CPP: Implement SQLConnect function for the ODBC driver. > --- > > Key: IGNITE-2239 > URL: https://issues.apache.org/jira/browse/IGNITE-2239 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > This function is listed in the [ODBC Core Interface > Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] > and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2163) CPP: ODBC driver supported version should be upgraded to 3.x
[ https://issues.apache.org/jira/browse/IGNITE-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego closed IGNITE-2163. --- > CPP: ODBC driver supported version should be upgraded to 3.x > > > Key: IGNITE-2163 > URL: https://issues.apache.org/jira/browse/IGNITE-2163 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Currently our implementation of the ODBC driver states that it supports ODBC > standard version 2.0. It seems that many features that Tablue uses are not > supported in this version of the ODBC. So we need to set our version to 3.x > and make sure it works. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2223) CPP: ODBC queries sometimes return wrong types for columns in metadata.
[ https://issues.apache.org/jira/browse/IGNITE-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego closed IGNITE-2223. --- > CPP: ODBC queries sometimes return wrong types for columns in metadata. > --- > > Key: IGNITE-2223 > URL: https://issues.apache.org/jira/browse/IGNITE-2223 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Some SQL queries return wrong types in metadata. For example, if query result > set has column of type "Decimal" it will be transferred as "Long" instead. As > a result, value can not be read in the application data buffer during row > fetch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2240) CPP: Implement SQLEndTran function for the ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego closed IGNITE-2240. --- > CPP: Implement SQLEndTran function for the ODBC driver. > --- > > Key: IGNITE-2240 > URL: https://issues.apache.org/jira/browse/IGNITE-2240 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > This function listed in the [ODBC Core Interface > Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] > and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (IGNITE-2230) CPP: Implement "Bind offset" feature for the ODBC driver.
[ https://issues.apache.org/jira/browse/IGNITE-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego closed IGNITE-2230. --- > CPP: Implement "Bind offset" feature for the ODBC driver. > - > > Key: IGNITE-2230 > URL: https://issues.apache.org/jira/browse/IGNITE-2230 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > This feature listed in the [ODBC Core Interface > Conformance|https://msdn.microsoft.com/en-us/library/ms714086(v=vs.85).aspx] > and should be implemented for our driver. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (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 closed IGNITE-2059.
---
> 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] [Closed] (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 closed IGNITE-2060.
---
> 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] [Closed] (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:all-tabpanel
]
Igor Sapego closed IGNITE-2130.
---
> 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] [Closed] (IGNITE-2141) Cleanup ODBC configuration.
[
https://issues.apache.org/jira/browse/IGNITE-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego closed IGNITE-2141.
---
> 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] [Resolved] (IGNITE-2223) CPP: ODBC queries sometimes return wrong types for columns in metadata.
[ https://issues.apache.org/jira/browse/IGNITE-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego resolved IGNITE-2223. - > CPP: ODBC queries sometimes return wrong types for columns in metadata. > --- > > Key: IGNITE-2223 > URL: https://issues.apache.org/jira/browse/IGNITE-2223 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Some SQL queries return wrong types in metadata. For example, if query result > set has column of type "Decimal" it will be transferred as "Long" instead. As > a result, value can not be read in the application data buffer during row > fetch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (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 closed IGNITE-2022. --- > 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] [Closed] (IGNITE-2223) CPP: ODBC queries sometimes return wrong types for columns in metadata.
[ https://issues.apache.org/jira/browse/IGNITE-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego closed IGNITE-2223. --- > CPP: ODBC queries sometimes return wrong types for columns in metadata. > --- > > Key: IGNITE-2223 > URL: https://issues.apache.org/jira/browse/IGNITE-2223 > Project: Ignite > Issue Type: Sub-task > Components: odbc >Reporter: Igor Sapego >Assignee: Igor Sapego > Fix For: 1.6 > > > Some SQL queries return wrong types in metadata. For example, if query result > set has column of type "Decimal" it will be transferred as "Long" instead. As > a result, value can not be read in the application data buffer during row > fetch. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (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 closed IGNITE-2044. --- > 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] [Closed] (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 closed IGNITE-2021. --- > 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)
