[jira] [Commented] (CASSANDRA-4871) get_paged_slice does not obey SlicePredicate

2013-07-31 Thread Jonathan Ellis (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725382#comment-13725382
 ] 

Jonathan Ellis commented on CASSANDRA-4871:
---

Right.  Basically, wide-row mode and get_paged_slice are hacks that are 
obsolete now that we have CQL and CqlPagingRecordReader.  See 
http://www.datastax.com/dev/blog/does-cql-support-dynamic-columns-wide-rows for 
background.

> get_paged_slice does not obey SlicePredicate
> 
>
> Key: CASSANDRA-4871
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4871
> Project: Cassandra
>  Issue Type: New Feature
>  Components: API, Hadoop
>Affects Versions: 1.1.0
>Reporter: Scott Fines
>Priority: Minor
> Attachments: CASSANDRA-4816.patch
>
>
> When experimenting with WideRow support, I noticed that it is not possible to 
> specify a bounding SlicePredicate. This means that, no matter what you may 
> wish, the entire Column Family will be used during a get_paged_slice call. 
> This is unfortunate, if (for example) you are attempting to do MapReduce over 
> a subset of your column range.
> get_paged_slice should support a SlicePredicate, which will bound the column 
> range over which data is returned. It seems like this SlicePredicate should 
> be optional, so that existing code is not broken--when the SlicePredicate is 
> not specified, have it default to going over the entire column range.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-4871) get_paged_slice does not obey SlicePredicate

2013-07-31 Thread Adam Masters (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725335#comment-13725335
 ] 

Adam Masters commented on CASSANDRA-4871:
-

Looking at the word_count example in github, its interesting to note the 
comment which has been added against the wide-row functionality: "this will 
cause the predicate to be ignored in favor of scanning everything as a wide 
row". This suggests that ignoring the SlicePredicate for wide rows is by 
design. In which case, how does one limit the columns when using wide rows?

> get_paged_slice does not obey SlicePredicate
> 
>
> Key: CASSANDRA-4871
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4871
> Project: Cassandra
>  Issue Type: New Feature
>  Components: API, Hadoop
>Affects Versions: 1.1.0
>Reporter: Scott Fines
>Priority: Minor
> Attachments: CASSANDRA-4816.patch
>
>
> When experimenting with WideRow support, I noticed that it is not possible to 
> specify a bounding SlicePredicate. This means that, no matter what you may 
> wish, the entire Column Family will be used during a get_paged_slice call. 
> This is unfortunate, if (for example) you are attempting to do MapReduce over 
> a subset of your column range.
> get_paged_slice should support a SlicePredicate, which will bound the column 
> range over which data is returned. It seems like this SlicePredicate should 
> be optional, so that existing code is not broken--when the SlicePredicate is 
> not specified, have it default to going over the entire column range.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-4871) get_paged_slice does not obey SlicePredicate

2013-07-31 Thread Adam Masters (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725241#comment-13725241
 ] 

Adam Masters commented on CASSANDRA-4871:
-

I'm finding this issue is still prevalent in 1.2.6, and the attached patch 
(still) doesnt apply to trunk. 

> get_paged_slice does not obey SlicePredicate
> 
>
> Key: CASSANDRA-4871
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4871
> Project: Cassandra
>  Issue Type: New Feature
>  Components: API, Hadoop
>Affects Versions: 1.1.0
>Reporter: Scott Fines
>Priority: Minor
> Attachments: CASSANDRA-4816.patch
>
>
> When experimenting with WideRow support, I noticed that it is not possible to 
> specify a bounding SlicePredicate. This means that, no matter what you may 
> wish, the entire Column Family will be used during a get_paged_slice call. 
> This is unfortunate, if (for example) you are attempting to do MapReduce over 
> a subset of your column range.
> get_paged_slice should support a SlicePredicate, which will bound the column 
> range over which data is returned. It seems like this SlicePredicate should 
> be optional, so that existing code is not broken--when the SlicePredicate is 
> not specified, have it default to going over the entire column range.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-4871) get_paged_slice does not obey SlicePredicate

2013-01-02 Thread JIRA

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542090#comment-13542090
 ] 

Piotr Kołaczkowski commented on CASSANDRA-4871:
---

And why the patch file has a different number than the ticket? Is it right 
patch file?

> get_paged_slice does not obey SlicePredicate
> 
>
> Key: CASSANDRA-4871
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4871
> Project: Cassandra
>  Issue Type: New Feature
>  Components: API, Hadoop
>Affects Versions: 1.1.0
>Reporter: Scott Fines
>Priority: Minor
> Fix For: 2.0
>
> Attachments: CASSANDRA-4816.patch
>
>
> When experimenting with WideRow support, I noticed that it is not possible to 
> specify a bounding SlicePredicate. This means that, no matter what you may 
> wish, the entire Column Family will be used during a get_paged_slice call. 
> This is unfortunate, if (for example) you are attempting to do MapReduce over 
> a subset of your column range.
> get_paged_slice should support a SlicePredicate, which will bound the column 
> range over which data is returned. It seems like this SlicePredicate should 
> be optional, so that existing code is not broken--when the SlicePredicate is 
> not specified, have it default to going over the entire column range.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-4871) get_paged_slice does not obey SlicePredicate

2013-01-02 Thread JIRA

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542087#comment-13542087
 ] 

Piotr Kołaczkowski commented on CASSANDRA-4871:
---

error: patch failed: 
src/java/org/apache/cassandra/hadoop/ColumnFamilyRecordReader.java:160
error: src/java/org/apache/cassandra/hadoop/ColumnFamilyRecordReader.java: 
patch does not apply

Can you rebase the patch, please?

> get_paged_slice does not obey SlicePredicate
> 
>
> Key: CASSANDRA-4871
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4871
> Project: Cassandra
>  Issue Type: New Feature
>  Components: API, Hadoop
>Affects Versions: 1.1.0
>Reporter: Scott Fines
>Priority: Minor
> Fix For: 2.0
>
> Attachments: CASSANDRA-4816.patch
>
>
> When experimenting with WideRow support, I noticed that it is not possible to 
> specify a bounding SlicePredicate. This means that, no matter what you may 
> wish, the entire Column Family will be used during a get_paged_slice call. 
> This is unfortunate, if (for example) you are attempting to do MapReduce over 
> a subset of your column range.
> get_paged_slice should support a SlicePredicate, which will bound the column 
> range over which data is returned. It seems like this SlicePredicate should 
> be optional, so that existing code is not broken--when the SlicePredicate is 
> not specified, have it default to going over the entire column range.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Commented] (CASSANDRA-4871) get_paged_slice does not obey SlicePredicate

2013-01-02 Thread JIRA

[ 
https://issues.apache.org/jira/browse/CASSANDRA-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542086#comment-13542086
 ] 

Piotr Kołaczkowski commented on CASSANDRA-4871:
---

Which branch is this patch for? I can't apply it to neither to 1.1 nor 1.2 nor 
trunk.

> get_paged_slice does not obey SlicePredicate
> 
>
> Key: CASSANDRA-4871
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4871
> Project: Cassandra
>  Issue Type: New Feature
>  Components: API, Hadoop
>Affects Versions: 1.1.0
>Reporter: Scott Fines
>Priority: Minor
> Fix For: 2.0
>
> Attachments: CASSANDRA-4816.patch
>
>
> When experimenting with WideRow support, I noticed that it is not possible to 
> specify a bounding SlicePredicate. This means that, no matter what you may 
> wish, the entire Column Family will be used during a get_paged_slice call. 
> This is unfortunate, if (for example) you are attempting to do MapReduce over 
> a subset of your column range.
> get_paged_slice should support a SlicePredicate, which will bound the column 
> range over which data is returned. It seems like this SlicePredicate should 
> be optional, so that existing code is not broken--when the SlicePredicate is 
> not specified, have it default to going over the entire column range.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira