[jira] [Updated] (CASSANDRA-4242) Name of parameters should be available in CqlPreparedResult
[
https://issues.apache.org/jira/browse/CASSANDRA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Chalamet updated CASSANDRA-4242:
---
Attachment: 4242_3.txt
ensure compatibility with cql 3 client.
Name of parameters should be available in CqlPreparedResult
---
Key: CASSANDRA-4242
URL: https://issues.apache.org/jira/browse/CASSANDRA-4242
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 1.1.0
Reporter: Pierre Chalamet
Priority: Minor
Attachments: 4242.txt, 4242_2.txt, 4242_3.txt
Client side, it could be nice to have the name of parameters in
CqlPreparedResult. This could allow parameters mapping by name instead of by
index.
{code}
struct CqlNameType {
1: required binary key,
2: required string type
}
struct CqlPreparedResult {
1: required i32 itemId,
2: required i32 count,
3: optional liststring variable_types,
4: optional listCqlNameType name_types
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4242) Name of parameters should be available in CqlPreparedResult
[
https://issues.apache.org/jira/browse/CASSANDRA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Chalamet updated CASSANDRA-4242:
---
Attachment: 4242_4.txt
Reverting to 2 lists in CqlPreparedResult
Column names are String now
Name of parameters should be available in CqlPreparedResult
---
Key: CASSANDRA-4242
URL: https://issues.apache.org/jira/browse/CASSANDRA-4242
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 1.1.0
Reporter: Pierre Chalamet
Priority: Minor
Attachments: 4242.txt, 4242_2.txt, 4242_3.txt, 4242_4.txt
Client side, it could be nice to have the name of parameters in
CqlPreparedResult. This could allow parameters mapping by name instead of by
index.
{code}
struct CqlNameType {
1: required binary key,
2: required string type
}
struct CqlPreparedResult {
1: required i32 itemId,
2: required i32 count,
3: optional liststring variable_types,
4: optional listCqlNameType name_types
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4242) Name of parameters should be available in CqlPreparedResult
[
https://issues.apache.org/jira/browse/CASSANDRA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-4242:
--
Reviewer: slebresne
Assignee: Pierre Chalamet
Name of parameters should be available in CqlPreparedResult
---
Key: CASSANDRA-4242
URL: https://issues.apache.org/jira/browse/CASSANDRA-4242
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 1.1.0
Reporter: Pierre Chalamet
Assignee: Pierre Chalamet
Priority: Minor
Fix For: 1.1.1
Attachments: 4242.txt, 4242_2.txt, 4242_3.txt, 4242_4.txt
Client side, it could be nice to have the name of parameters in
CqlPreparedResult. This could allow parameters mapping by name instead of by
index.
{code}
struct CqlNameType {
1: required binary key,
2: required string type
}
struct CqlPreparedResult {
1: required i32 itemId,
2: required i32 count,
3: optional liststring variable_types,
4: optional listCqlNameType name_types
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4242) Name of parameters should be available in CqlPreparedResult
[
https://issues.apache.org/jira/browse/CASSANDRA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-4242:
--
Fix Version/s: 1.1.1
Name of parameters should be available in CqlPreparedResult
---
Key: CASSANDRA-4242
URL: https://issues.apache.org/jira/browse/CASSANDRA-4242
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 1.1.0
Reporter: Pierre Chalamet
Assignee: Pierre Chalamet
Priority: Minor
Fix For: 1.1.1
Attachments: 4242.txt, 4242_2.txt, 4242_3.txt, 4242_4.txt
Client side, it could be nice to have the name of parameters in
CqlPreparedResult. This could allow parameters mapping by name instead of by
index.
{code}
struct CqlNameType {
1: required binary key,
2: required string type
}
struct CqlPreparedResult {
1: required i32 itemId,
2: required i32 count,
3: optional liststring variable_types,
4: optional listCqlNameType name_types
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4242) Name of parameters should be available in CqlPreparedResult
[
https://issues.apache.org/jira/browse/CASSANDRA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Chalamet updated CASSANDRA-4242:
---
Attachment: 4242_2.txt
patch rebase from trunk
Name of parameters should be available in CqlPreparedResult
---
Key: CASSANDRA-4242
URL: https://issues.apache.org/jira/browse/CASSANDRA-4242
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 1.1.0
Reporter: Pierre Chalamet
Priority: Minor
Attachments: 4242.txt, 4242_2.txt
Client side, it could be nice to have the name of parameters in
CqlPreparedResult. This could allow parameters mapping by name instead of by
index.
{code}
struct CqlNameType {
1: required binary key,
2: required string type
}
struct CqlPreparedResult {
1: required i32 itemId,
2: required i32 count,
3: optional liststring variable_types,
4: optional listCqlNameType name_types
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4242) Name of parameters should be available in CqlPreparedResult
[
https://issues.apache.org/jira/browse/CASSANDRA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Chalamet updated CASSANDRA-4242:
---
Attachment: (was: 4242.txt)
Name of parameters should be available in CqlPreparedResult
---
Key: CASSANDRA-4242
URL: https://issues.apache.org/jira/browse/CASSANDRA-4242
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 1.1.0
Reporter: Pierre Chalamet
Priority: Minor
Attachments: 4242.txt
Client side, it could be nice to have the name of parameters in
CqlPreparedResult. This could allow parameters mapping by name instead of by
index.
{code}
struct CqlPreparedResult {
1: required i32 itemId,
2: required i32 count,
3: optional liststring variable_types
4: optional mapbinary,string name_types
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4242) Name of parameters should be available in CqlPreparedResult
[
https://issues.apache.org/jira/browse/CASSANDRA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Chalamet updated CASSANDRA-4242:
---
Attachment: 4242.txt
use list instead of map since the order is important
Name of parameters should be available in CqlPreparedResult
---
Key: CASSANDRA-4242
URL: https://issues.apache.org/jira/browse/CASSANDRA-4242
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 1.1.0
Reporter: Pierre Chalamet
Priority: Minor
Attachments: 4242.txt
Client side, it could be nice to have the name of parameters in
CqlPreparedResult. This could allow parameters mapping by name instead of by
index.
{code}
struct CqlPreparedResult {
1: required i32 itemId,
2: required i32 count,
3: optional liststring variable_types
4: optional mapbinary,string name_types
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4242) Name of parameters should be available in CqlPreparedResult
[
https://issues.apache.org/jira/browse/CASSANDRA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Chalamet updated CASSANDRA-4242:
---
Description:
Client side, it could be nice to have the name of parameters in
CqlPreparedResult. This could allow parameters mapping by name instead of by
index.
{code}
struct CqlNameType {
1: required binary key,
2: required string type
}
struct CqlPreparedResult {
1: required i32 itemId,
2: required i32 count,
3: optional liststring variable_types,
4: optional listCqlNameType name_types
}
{code}
was:
Client side, it could be nice to have the name of parameters in
CqlPreparedResult. This could allow parameters mapping by name instead of by
index.
{code}
struct CqlPreparedResult {
1: required i32 itemId,
2: required i32 count,
3: optional liststring variable_types
4: optional mapbinary,string name_types
}
{code}
Name of parameters should be available in CqlPreparedResult
---
Key: CASSANDRA-4242
URL: https://issues.apache.org/jira/browse/CASSANDRA-4242
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 1.1.0
Reporter: Pierre Chalamet
Priority: Minor
Attachments: 4242.txt
Client side, it could be nice to have the name of parameters in
CqlPreparedResult. This could allow parameters mapping by name instead of by
index.
{code}
struct CqlNameType {
1: required binary key,
2: required string type
}
struct CqlPreparedResult {
1: required i32 itemId,
2: required i32 count,
3: optional liststring variable_types,
4: optional listCqlNameType name_types
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4242) Name of parameters should be available in CqlPreparedResult
[
https://issues.apache.org/jira/browse/CASSANDRA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Chalamet updated CASSANDRA-4242:
---
Attachment: 4242.txt
Name of parameters should be available in CqlPreparedResult
---
Key: CASSANDRA-4242
URL: https://issues.apache.org/jira/browse/CASSANDRA-4242
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 1.1.0
Reporter: Pierre Chalamet
Priority: Minor
Attachments: 4242.txt
Client side, it could be nice to have the name of parameters in
CqlPreparedResult. This could allow parameters mapping by name instead of by
index.
{code}
struct CqlPreparedResult {
1: required i32 itemId,
2: required i32 count,
3: optional liststring variable_types
4: optional listbinary variable_names
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4242) Name of parameters should be available in CqlPreparedResult
[
https://issues.apache.org/jira/browse/CASSANDRA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Chalamet updated CASSANDRA-4242:
---
Attachment: (was: 4242.txt)
Name of parameters should be available in CqlPreparedResult
---
Key: CASSANDRA-4242
URL: https://issues.apache.org/jira/browse/CASSANDRA-4242
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 1.1.0
Reporter: Pierre Chalamet
Priority: Minor
Attachments: 4242.txt
Client side, it could be nice to have the name of parameters in
CqlPreparedResult. This could allow parameters mapping by name instead of by
index.
{code}
struct CqlPreparedResult {
1: required i32 itemId,
2: required i32 count,
3: optional liststring variable_types
4: optional listbinary variable_names
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4242) Name of parameters should be available in CqlPreparedResult
[
https://issues.apache.org/jira/browse/CASSANDRA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Chalamet updated CASSANDRA-4242:
---
Attachment: 4242.txt
using a map instead of 2 lists
Name of parameters should be available in CqlPreparedResult
---
Key: CASSANDRA-4242
URL: https://issues.apache.org/jira/browse/CASSANDRA-4242
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 1.1.0
Reporter: Pierre Chalamet
Priority: Minor
Attachments: 4242.txt
Client side, it could be nice to have the name of parameters in
CqlPreparedResult. This could allow parameters mapping by name instead of by
index.
{code}
struct CqlPreparedResult {
1: required i32 itemId,
2: required i32 count,
3: optional liststring variable_types
4: optional listbinary variable_names
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CASSANDRA-4242) Name of parameters should be available in CqlPreparedResult
[
https://issues.apache.org/jira/browse/CASSANDRA-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Chalamet updated CASSANDRA-4242:
---
Description:
Client side, it could be nice to have the name of parameters in
CqlPreparedResult. This could allow parameters mapping by name instead of by
index.
{code}
struct CqlPreparedResult {
1: required i32 itemId,
2: required i32 count,
3: optional liststring variable_types
4: optional mapbinary,string name_types
}
{code}
was:
Client side, it could be nice to have the name of parameters in
CqlPreparedResult. This could allow parameters mapping by name instead of by
index.
{code}
struct CqlPreparedResult {
1: required i32 itemId,
2: required i32 count,
3: optional liststring variable_types
4: optional listbinary variable_names
}
{code}
moved from two lists to one map.
Name of parameters should be available in CqlPreparedResult
---
Key: CASSANDRA-4242
URL: https://issues.apache.org/jira/browse/CASSANDRA-4242
Project: Cassandra
Issue Type: Improvement
Components: Core
Affects Versions: 1.1.0
Reporter: Pierre Chalamet
Priority: Minor
Attachments: 4242.txt
Client side, it could be nice to have the name of parameters in
CqlPreparedResult. This could allow parameters mapping by name instead of by
index.
{code}
struct CqlPreparedResult {
1: required i32 itemId,
2: required i32 count,
3: optional liststring variable_types
4: optional mapbinary,string name_types
}
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
