[jira] [Updated] (CASSANDRA-4872) Move manifest into sstable metadata
[ https://issues.apache.org/jira/browse/CASSANDRA-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-4872: --- Attachment: 0001-CASSANDRA-4872-wip-v7.patch As far as i can see, reseting levels was not done when moving from STCS to LCS before this, the json file was left behind, meaning, for example that a change to max sstable size might leave data with a too high level etc. anyway, v7 resets levels when changing to LCS (or when updating compaction strategy options). Move manifest into sstable metadata --- Key: CASSANDRA-4872 URL: https://issues.apache.org/jira/browse/CASSANDRA-4872 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Jonathan Ellis Assignee: Marcus Eriksson Priority: Minor Fix For: 2.0 Attachments: 0001-CASSANDRA-4872-move-sstable-level-into-sstable-metad-v1.patch, 0001-CASSANDRA-4872-move-sstable-level-into-sstable-metad-v2.patch, 0001-CASSANDRA-4872-move-sstable-level-into-sstable-metad-v3.patch, 0001-CASSANDRA-4872-move-sstable-level-into-sstable-metad-v4.patch, 0001-CASSANDRA-4872-wip-v6.patch, 0001-CASSANDRA-4872-wip-v7.patch, 4872-v5.txt Now that we have a metadata component it would be better to keep sstable level there, than in a separate manifest. With information per-sstable we don't need to do a full re-level if there is corruption. -- 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] [Comment Edited] (CASSANDRA-4872) Move manifest into sstable metadata
[ https://issues.apache.org/jira/browse/CASSANDRA-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580481#comment-13580481 ] Marcus Eriksson edited comment on CASSANDRA-4872 at 2/18/13 8:07 AM: - As far as i can see, reseting levels was not done when moving from STCS to LCS or when changing compaction options before this, the json file was left behind, meaning, for example that a change to max sstable size might leave data with a too high level etc. anyway, v7 resets levels when changing to LCS (or when updating compaction strategy options). was (Author: krummas): As far as i can see, reseting levels was not done when moving from STCS to LCS before this, the json file was left behind, meaning, for example that a change to max sstable size might leave data with a too high level etc. anyway, v7 resets levels when changing to LCS (or when updating compaction strategy options). Move manifest into sstable metadata --- Key: CASSANDRA-4872 URL: https://issues.apache.org/jira/browse/CASSANDRA-4872 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Jonathan Ellis Assignee: Marcus Eriksson Priority: Minor Fix For: 2.0 Attachments: 0001-CASSANDRA-4872-move-sstable-level-into-sstable-metad-v1.patch, 0001-CASSANDRA-4872-move-sstable-level-into-sstable-metad-v2.patch, 0001-CASSANDRA-4872-move-sstable-level-into-sstable-metad-v3.patch, 0001-CASSANDRA-4872-move-sstable-level-into-sstable-metad-v4.patch, 0001-CASSANDRA-4872-wip-v6.patch, 0001-CASSANDRA-4872-wip-v7.patch, 4872-v5.txt Now that we have a metadata component it would be better to keep sstable level there, than in a separate manifest. With information per-sstable we don't need to do a full re-level if there is corruption. -- 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-5074) Add an official way to disable compaction
[
https://issues.apache.org/jira/browse/CASSANDRA-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580494#comment-13580494
]
Andrea Gazzarini commented on CASSANDRA-5074:
-
Right, I agree...the simplest thing that could possibly work; but in my opinion
there's still something that needs to be changed: setting the min and / or max
threshold, strictly speaking doesn't disable the compaction, because is up to
the concrete strategy implementor to check that doing
if (cfs.isCompactionDisabled()) {
...
}
I think it should be better to move this responsibility to the superlayer.
So my suggestion is to change a little bit the AbstractCompactionStrategy in
order to use a template method. Something like this:
(AbstractCompactionStrategy)
{noformat}
final synchronized AbstractCompactionTask getNextBackgroundTask(final int
gcBefore)
{
if (cfs.isCompactionDisabled()) {
doGetNextBackgroundTask(gcBefore);
}
}
...
abstract AbstractCompactionTask doGetNextBackgroundTask(final int gcBefore);
{noformat}
Add an official way to disable compaction
-
Key: CASSANDRA-5074
URL: https://issues.apache.org/jira/browse/CASSANDRA-5074
Project: Cassandra
Issue Type: Bug
Reporter: Jonathan Ellis
Priority: Minor
Fix For: 1.2.2
We've traditionally used min or max compaction threshold = 0 to disable
compaction, but this isn't exactly intuitive and it's inconsistently
implemented -- allowed from jmx, not allowed from cli.
--
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
[Cassandra Wiki] Trivial Update of JannieKel by JannieKel
Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The JannieKel page has been changed by JannieKel: http://wiki.apache.org/cassandra/JannieKel New page: Hey !! I am RANA MANNING. Soon i will turn 52.BR I go to night school at The Gleeful Institute situated in St. Petersburg. My dad name is Matt and he is a Undertaker. My mother is a Referee.BR BR Here is my page [[http://h2o-xpo.org/beatsbydrecheap.aspx|beats headphones review]]
[jira] [Updated] (CASSANDRA-5251) Hadoop support should be able to work with multiple column families
[ https://issues.apache.org/jira/browse/CASSANDRA-5251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Illarion Kovalchuk updated CASSANDRA-5251: -- Affects Version/s: 2.0 1.1.11 1.2.0 Hadoop support should be able to work with multiple column families --- Key: CASSANDRA-5251 URL: https://issues.apache.org/jira/browse/CASSANDRA-5251 Project: Cassandra Issue Type: Improvement Components: Hadoop Affects Versions: 1.1.0, 1.1.11, 1.2.0, 2.0 Reporter: Illarion Kovalchuk Priority: Minor Attachments: trunk-5251.txt This patch affects api, so I changed hadoop example in it. The main difference is that now ColumnFamilyInput format generates splits for all input column families, and ColumnFamilyOutputFormat works not with ListMutation, but with ListPairString,Mutation, where Pair.left is for column family name. Thank you -- 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-5264) Nodetool ring is reporting incorrect Effective ownership after upgrading from 1.1.2 - 1.1.9
[ https://issues.apache.org/jira/browse/CASSANDRA-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580616#comment-13580616 ] Michael Theroux commented on CASSANDRA-5264: FYI, I setup a test environment and was able to reproduce the behavior. I then reverted the change to StorageService.getSplits(), and my effective ownership information returned to their previous values. I have not yet dug in to understand the difference in the implementation. Nodetool ring is reporting incorrect Effective ownership after upgrading from 1.1.2 - 1.1.9 Key: CASSANDRA-5264 URL: https://issues.apache.org/jira/browse/CASSANDRA-5264 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.1.9 Environment: Amazon AWS Linux, Large instance (8gig of RAM, ephemeral storage). 12 Node cluster. Replication Factor 3, all queries performed with LOCAL_QUORUM Reporter: Michael Theroux Priority: Minor We upgraded from Cassandra 1.1.2 to 1.1.9 yesterday. All indications are the upgrade went well. Repair works as expected, and all our data is available. Performance is as good, if not better, than it was previously. However, nodetool ring is reporting inconsistent and incorrect results. This was my ring information before the upgrade: Address DC RackStatus State Load Effective-Ownership Token Token(bytes[eaa8]) 10.0.4.22 us-east 1a Up Normal 77.75 GB25.00% Token(bytes[0001]) 10.0.10.23 us-east 1d Up Normal 82.68 GB25.00% Token(bytes[1555]) 10.0.8.20 us-east 1c Up Normal 81.72 GB25.00% Token(bytes[2aaa]) 10.0.4.23 us-east 1a Up Normal 82.65 GB25.00% Token(bytes[4000]) 10.0.10.20 us-east 1d Up Normal 80.2 GB 25.00% Token(bytes[5554]) 10.0.8.23 us-east 1c Up Normal 77.06 GB25.00% Token(bytes[6aac]) 10.0.4.21 us-east 1a Up Normal 81.37 GB25.00% Token(bytes[8000]) 10.0.10.24 us-east 1d Up Normal 83.37 GB25.00% Token(bytes[9558]) 10.0.8.21 us-east 1c Up Normal 84.33 GB25.00% Token(bytes[aaa8]) 10.0.4.25 us-east 1a Up Normal 79.91 GB25.00% Token(bytes[c000]) 10.0.10.21 us-east 1d Up Normal 83.46 GB25.00% Token(bytes[d558]) 10.0.8.24 us-east 1c Up Normal 90.66 GB25.00% Token(bytes[eaa8]) This is my ring information after the upgrade: 10.0.4.22 us-east 1a Up Normal 77.74 GB99.89% Token(bytes[0001]) 10.0.10.23 us-east 1d Up Normal 82.82 GB64.14% Token(bytes[1555]) 10.0.8.20 us-east 1c Up Normal 81.89 GB30.55% Token(bytes[2aaa]) 10.0.4.23 us-east 1a Up Normal 82.77 GB0.04% Token(bytes[4000]) 10.0.10.20 us-east 1d Up Normal 80.32 GB0.04% Token(bytes[5554]) 10.0.8.23 us-east 1c Up Normal 77.07 GB0.04% Token(bytes[6aac]) 10.0.4.21 us-east 1a Up Normal 81.35 GB0.04% Token(bytes[8000]) 10.0.10.24 us-east 1d Up Normal 83.49 GB0.04% Token(bytes[9558]) 10.0.8.21 us-east 1c Up Normal 84.47 GB0.04% Token(bytes[aaa8]) 10.0.4.25 us-east 1a Up Normal 80.11 GB0.04%
[jira] [Commented] (CASSANDRA-5264) Nodetool ring is reporting incorrect Effective ownership after upgrading from 1.1.2 - 1.1.9
[ https://issues.apache.org/jira/browse/CASSANDRA-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580620#comment-13580620 ] Jonathan Ellis commented on CASSANDRA-5264: --- bq. We use ByteOrderedPartitioning That would explain getSplits affecting it. Nodetool ring is reporting incorrect Effective ownership after upgrading from 1.1.2 - 1.1.9 Key: CASSANDRA-5264 URL: https://issues.apache.org/jira/browse/CASSANDRA-5264 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.1.9 Environment: Amazon AWS Linux, Large instance (8gig of RAM, ephemeral storage). 12 Node cluster. Replication Factor 3, all queries performed with LOCAL_QUORUM Reporter: Michael Theroux Priority: Minor We upgraded from Cassandra 1.1.2 to 1.1.9 yesterday. All indications are the upgrade went well. Repair works as expected, and all our data is available. Performance is as good, if not better, than it was previously. However, nodetool ring is reporting inconsistent and incorrect results. This was my ring information before the upgrade: Address DC RackStatus State Load Effective-Ownership Token Token(bytes[eaa8]) 10.0.4.22 us-east 1a Up Normal 77.75 GB25.00% Token(bytes[0001]) 10.0.10.23 us-east 1d Up Normal 82.68 GB25.00% Token(bytes[1555]) 10.0.8.20 us-east 1c Up Normal 81.72 GB25.00% Token(bytes[2aaa]) 10.0.4.23 us-east 1a Up Normal 82.65 GB25.00% Token(bytes[4000]) 10.0.10.20 us-east 1d Up Normal 80.2 GB 25.00% Token(bytes[5554]) 10.0.8.23 us-east 1c Up Normal 77.06 GB25.00% Token(bytes[6aac]) 10.0.4.21 us-east 1a Up Normal 81.37 GB25.00% Token(bytes[8000]) 10.0.10.24 us-east 1d Up Normal 83.37 GB25.00% Token(bytes[9558]) 10.0.8.21 us-east 1c Up Normal 84.33 GB25.00% Token(bytes[aaa8]) 10.0.4.25 us-east 1a Up Normal 79.91 GB25.00% Token(bytes[c000]) 10.0.10.21 us-east 1d Up Normal 83.46 GB25.00% Token(bytes[d558]) 10.0.8.24 us-east 1c Up Normal 90.66 GB25.00% Token(bytes[eaa8]) This is my ring information after the upgrade: 10.0.4.22 us-east 1a Up Normal 77.74 GB99.89% Token(bytes[0001]) 10.0.10.23 us-east 1d Up Normal 82.82 GB64.14% Token(bytes[1555]) 10.0.8.20 us-east 1c Up Normal 81.89 GB30.55% Token(bytes[2aaa]) 10.0.4.23 us-east 1a Up Normal 82.77 GB0.04% Token(bytes[4000]) 10.0.10.20 us-east 1d Up Normal 80.32 GB0.04% Token(bytes[5554]) 10.0.8.23 us-east 1c Up Normal 77.07 GB0.04% Token(bytes[6aac]) 10.0.4.21 us-east 1a Up Normal 81.35 GB0.04% Token(bytes[8000]) 10.0.10.24 us-east 1d Up Normal 83.49 GB0.04% Token(bytes[9558]) 10.0.8.21 us-east 1c Up Normal 84.47 GB0.04% Token(bytes[aaa8]) 10.0.4.25 us-east 1a Up Normal 80.11 GB0.04% Token(bytes[c000]) 10.0.10.21 us-east 1d Up Normal 83.5 GB 35.79% Token(bytes[d558]) 10.0.8.24 us-east 1c Up Normal
buildbot failure in ASF Buildbot on cassandra-trunk
The Buildbot has detected a new failure on builder cassandra-trunk while building cassandra. Full details are available at: http://ci.apache.org/builders/cassandra-trunk/builds/2362 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: portunus_ubuntu Build Reason: scheduler Build Source Stamp: [branch trunk] 0e284787294221982d21c17b27c0a4e1ae0971e7 Blamelist: Jonathan Ellis jbel...@apache.org BUILD FAILED: failed shell sincerely, -The Buildbot
[jira] [Commented] (CASSANDRA-5255) dsnitch severity is not correctly set for compaction info
[ https://issues.apache.org/jira/browse/CASSANDRA-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580652#comment-13580652 ] Jonathan Ellis commented on CASSANDRA-5255: --- bq. Another possible option: Create a way to get IOStat data into the JVM and measure the IOWait time but the problem is how do we support MS Windows? not sure if there is a generic way to do so. I like that idea a lot better than trying to special-case streaming and compaction. No idea how to get that info on Windows though. Guess we could fall back to MBPs compaction/streaming there. (Yes, this is not perfect if you mix SSDs + HDDs, but it's a LOT better than total MB of compaction.) dsnitch severity is not correctly set for compaction info - Key: CASSANDRA-5255 URL: https://issues.apache.org/jira/browse/CASSANDRA-5255 Project: Cassandra Issue Type: Bug Affects Versions: 1.2.0 beta 1 Reporter: Brandon Williams Assignee: Vijay Priority: Minor Fix For: 1.2.2 Attachments: 0001-CASSANDRA-5255.patch We're doing two things wrong in CI. First, load can change between calls, which can cause a negative severity even though it meant to subtract whatever it added before. Second, we should report based on how much IO we're using, since a 1T throttled to 5MB/s is less impactful than a 100MB running at full speed. -- 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
buildbot success in ASF Buildbot on cassandra-trunk
The Buildbot has detected a restored build on builder cassandra-trunk while building cassandra. Full details are available at: http://ci.apache.org/builders/cassandra-trunk/builds/2363 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: portunus_ubuntu Build Reason: scheduler Build Source Stamp: [branch trunk] 278a5e86001b1fd094da2e0d05ea48e8f7eb9e1f Blamelist: Jonathan Ellis jbel...@apache.org Build succeeded! sincerely, -The Buildbot
[jira] [Updated] (CASSANDRA-5051) Allow automatic cleanup after gc_grace
[ https://issues.apache.org/jira/browse/CASSANDRA-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis updated CASSANDRA-5051: -- Reviewer: jbellis Allow automatic cleanup after gc_grace -- Key: CASSANDRA-5051 URL: https://issues.apache.org/jira/browse/CASSANDRA-5051 Project: Cassandra Issue Type: New Feature Components: Core Reporter: Brandon Williams Assignee: Vijay Labels: vnodes Fix For: 2.0 Attachments: 0001-CASSANDRA-5051.patch When using vnodes, after adding a new node you have to run cleanup on all the machines, because you don't know which are affected and chances are it was most if not all of them. As an alternative to this intensive process, we could allow cleanup during compaction if the data is older than gc_grace (or perhaps some other time period since people tend to use gc_grace hacks to get rid of tombstones.) -- 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] [Comment Edited] (CASSANDRA-5074) Add an official way to disable compaction
[
https://issues.apache.org/jira/browse/CASSANDRA-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580494#comment-13580494
]
Andrea Gazzarini edited comment on CASSANDRA-5074 at 2/18/13 4:15 PM:
--
Right, I agree...the simplest thing that could possibly work; but in my opinion
there's still something that needs to be changed: setting the min and / or max
threshold, strictly speaking doesn't disable the compaction, because is up to
the concrete strategy implementor to check that doing
if (cfs.isCompactionDisabled()) {
...
}
I think it should be better to move this responsibility to the superlayer.
So my suggestion is to change a little bit the AbstractCompactionStrategy in
order to use a template method. Something like this:
(AbstractCompactionStrategy)
{noformat}
final synchronized AbstractCompactionTask getNextBackgroundTask(final int
gcBefore)
{
if (!cfs.isCompactionDisabled()) {
doGetNextBackgroundTask(gcBefore);
}
}
...
abstract AbstractCompactionTask doGetNextBackgroundTask(final int gcBefore);
{noformat}
was (Author: a.gazzarini):
Right, I agree...the simplest thing that could possibly work; but in my
opinion there's still something that needs to be changed: setting the min and /
or max threshold, strictly speaking doesn't disable the compaction, because is
up to the concrete strategy implementor to check that doing
if (cfs.isCompactionDisabled()) {
...
}
I think it should be better to move this responsibility to the superlayer.
So my suggestion is to change a little bit the AbstractCompactionStrategy in
order to use a template method. Something like this:
(AbstractCompactionStrategy)
{noformat}
final synchronized AbstractCompactionTask getNextBackgroundTask(final int
gcBefore)
{
if (cfs.isCompactionDisabled()) {
doGetNextBackgroundTask(gcBefore);
}
}
...
abstract AbstractCompactionTask doGetNextBackgroundTask(final int gcBefore);
{noformat}
Add an official way to disable compaction
-
Key: CASSANDRA-5074
URL: https://issues.apache.org/jira/browse/CASSANDRA-5074
Project: Cassandra
Issue Type: Bug
Reporter: Jonathan Ellis
Priority: Minor
Fix For: 1.2.2
We've traditionally used min or max compaction threshold = 0 to disable
compaction, but this isn't exactly intuitive and it's inconsistently
implemented -- allowed from jmx, not allowed from cli.
--
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
[Cassandra Wiki] Trivial Update of Lasonya92 by Lasonya92
Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The Lasonya92 page has been changed by Lasonya92: http://wiki.apache.org/cassandra/Lasonya92 New page: This jan i will be 54. I am taking admission in The Short Prep School situated in Tulsa.BR I am self employed as a Architect. My hobby is Martial Arts. My father name is Randy and he is a Computer programmer. My mummy is a Automotive mechanic.BR BR Here is my web site; [[http://www.dressesonit.com|discount wedding dresses]]
[Cassandra Wiki] Update of Committers by BrandonWilliams
Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The Committers page has been changed by BrandonWilliams: http://wiki.apache.org/cassandra/Committers?action=diffrev1=31rev2=32 ||Dave Brosius||May 2012||Independent||Also a [[http://commons.apache.org|Commons]] committer|| ||Yuki Morishita||May 2012||Datastax ||Aleksey Yeschenko||Nov 2012||Datastax|| || - ||Jason Brown||Feb 2012||Netflix|| || + ||Jason Brown||Feb 2013||Netflix|| ||
[jira] [Commented] (CASSANDRA-5074) Add an official way to disable compaction
[ https://issues.apache.org/jira/browse/CASSANDRA-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580725#comment-13580725 ] Sylvain Lebresne commented on CASSANDRA-5074: - In case that wasn't clear, I didn't said there is nothing to change. On the contrary, we should *stop* relying on setting the min/max compaction threshold to disable compaction (I'd be in favor of always considering that setting them to 0 is disallowed, but we'd have to leave that to 2.0 to not break it in a minor release). So instead I would add a per-cfs 'isAutoCompactionEnable' boolean. As for the call to isCompactionDisabled, it should indeed be moved, but I would move it to CompactionManager directly (where I would put 2 checks, one prior to submitting to the compaction executor, to avoid submitting useless task in the first place, and then again before the call to getNextBackgroundTask, just in case the runnable has been sitting for too long on the executor and has missed the first check). Add an official way to disable compaction - Key: CASSANDRA-5074 URL: https://issues.apache.org/jira/browse/CASSANDRA-5074 Project: Cassandra Issue Type: Bug Reporter: Jonathan Ellis Priority: Minor Fix For: 1.2.2 We've traditionally used min or max compaction threshold = 0 to disable compaction, but this isn't exactly intuitive and it's inconsistently implemented -- allowed from jmx, not allowed from cli. -- 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
[Cassandra Wiki] Trivial Update of KatiaSett by KatiaSett
Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The KatiaSett page has been changed by KatiaSett: http://wiki.apache.org/cassandra/KatiaSett New page: Yo guys !! I am MACIE CLARKE. Soon i will turn 26. I and my sister go to The Successful Prep School situated in Harlingen.BR I have a job as Driver.BR BR Also visit my web page ... [[http://www.majorreplicahandbags.com|designer handbags]]
[jira] [Updated] (CASSANDRA-5081) Support null values in PreparedStatements parameters
[ https://issues.apache.org/jira/browse/CASSANDRA-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-5081: Attachment: 5081.patch Attaching patch to support nulls as values for bound variables. I note that there is no change to do to the binary protocol since it has always allowed nulls, they were just not correctly handled server side. Support null values in PreparedStatements parameters Key: CASSANDRA-5081 URL: https://issues.apache.org/jira/browse/CASSANDRA-5081 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Michaël Figuière Assignee: Sylvain Lebresne Fix For: 1.2.2 Attachments: 5081.patch Currently whenever developers want to use PreparedStatements, they need to ensure that all their parameters are non null or they need to have several PreparedStatements for each possible set of non null columns they want to store. This is obviously not a satisfying solution considering that 'null' values are a commonplace in applications. 'null' values should be allowed as parameters of PreparedStatements in Binary Protocol to solve this issue. This issue is obviously tightly coupled with CASSANDRA-3783 but they might be fixed separately. -- 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] [Updated] (CASSANDRA-5231) Add username autocompletion to cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-5231: - Attachment: 5231.txt Add username autocompletion to cqlsh Key: CASSANDRA-5231 URL: https://issues.apache.org/jira/browse/CASSANDRA-5231 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Aleksey Yeschenko Assignee: Aleksey Yeschenko Priority: Trivial Fix For: 1.2.2 Attachments: 5231.txt Add cqlsh username autocompletion to grant/revoke/list/drop/alter queries. -- 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-3783) Add 'null' support to CQL 3.0
[
https://issues.apache.org/jira/browse/CASSANDRA-3783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580764#comment-13580764
]
Sylvain Lebresne commented on CASSANDRA-3783:
-
bq. Will this be supported for prepared statement as well ?
Yes, there is even CASSANDRA-5081 opened for that specific part.
Add 'null' support to CQL 3.0
-
Key: CASSANDRA-3783
URL: https://issues.apache.org/jira/browse/CASSANDRA-3783
Project: Cassandra
Issue Type: Sub-task
Components: API
Reporter: Sylvain Lebresne
Priority: Minor
Labels: cql3
Fix For: 1.2.2
Attachments: 3783-wip-v1.patch
Dense composite supports adding records where only a prefix of all the
component specifying the key is defined. In other words, with:
{noformat}
CREATE TABLE connections (
userid int,
ip text,
port int,
protocol text,
time timestamp,
PRIMARY KEY (userid, ip, port, protocol)
) WITH COMPACT STORAGE
{noformat}
you can insert
{noformat}
INSERT INTO connections (userid, ip, port, time) VALUES (2, '192.168.0.1',
80, 123456789);
{noformat}
You cannot however select that column specifically (i.e, without selecting
column (2, '192.168.0.1', 80, 'http') for instance).
This ticket proposes to allow that though 'null', i.e. to allow
{noformat}
SELECT * FROM connections WHERE userid = 2 AND ip = '192.168.0.1' AND port =
80 AND protocol = null;
{noformat}
It would then also make sense to support:
{noformat}
INSERT INTO connections (userid, ip, port, protocol, time) VALUES (2,
'192.168.0.1', 80, null, 123456789);
{noformat}
as an equivalent to the insert query above.
--
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] [Updated] (CASSANDRA-5081) Support null values in PreparedStatements parameters
[ https://issues.apache.org/jira/browse/CASSANDRA-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-5081: Attachment: (was: 5081.patch) Support null values in PreparedStatements parameters Key: CASSANDRA-5081 URL: https://issues.apache.org/jira/browse/CASSANDRA-5081 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Michaël Figuière Assignee: Sylvain Lebresne Fix For: 1.2.2 Attachments: 5081.patch Currently whenever developers want to use PreparedStatements, they need to ensure that all their parameters are non null or they need to have several PreparedStatements for each possible set of non null columns they want to store. This is obviously not a satisfying solution considering that 'null' values are a commonplace in applications. 'null' values should be allowed as parameters of PreparedStatements in Binary Protocol to solve this issue. This issue is obviously tightly coupled with CASSANDRA-3783 but they might be fixed separately. -- 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] [Updated] (CASSANDRA-5081) Support null values in PreparedStatements parameters
[ https://issues.apache.org/jira/browse/CASSANDRA-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-5081: Attachment: 5081.patch Support null values in PreparedStatements parameters Key: CASSANDRA-5081 URL: https://issues.apache.org/jira/browse/CASSANDRA-5081 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Michaël Figuière Assignee: Sylvain Lebresne Fix For: 1.2.2 Attachments: 5081.patch Currently whenever developers want to use PreparedStatements, they need to ensure that all their parameters are non null or they need to have several PreparedStatements for each possible set of non null columns they want to store. This is obviously not a satisfying solution considering that 'null' values are a commonplace in applications. 'null' values should be allowed as parameters of PreparedStatements in Binary Protocol to solve this issue. This issue is obviously tightly coupled with CASSANDRA-3783 but they might be fixed separately. -- 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-5081) Support null values in PreparedStatements parameters
[ https://issues.apache.org/jira/browse/CASSANDRA-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580793#comment-13580793 ] Sylvain Lebresne commented on CASSANDRA-5081: - I note that the patch attached only support nulls for non primary key parts (which make sense) and not at all in select statements. The reasoning for the latter is just that support null in select statements is not really doable efficiently currently as 2ndary indexexes do not index null values (and it wouldn't be trivial to do). Support null values in PreparedStatements parameters Key: CASSANDRA-5081 URL: https://issues.apache.org/jira/browse/CASSANDRA-5081 Project: Cassandra Issue Type: Improvement Components: Core Reporter: Michaël Figuière Assignee: Sylvain Lebresne Fix For: 1.2.2 Attachments: 5081.patch Currently whenever developers want to use PreparedStatements, they need to ensure that all their parameters are non null or they need to have several PreparedStatements for each possible set of non null columns they want to store. This is obviously not a satisfying solution considering that 'null' values are a commonplace in applications. 'null' values should be allowed as parameters of PreparedStatements in Binary Protocol to solve this issue. This issue is obviously tightly coupled with CASSANDRA-3783 but they might be fixed separately. -- 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] [Updated] (CASSANDRA-5240) CQL3 has error with Compund row keys when secondray index involved
[
https://issues.apache.org/jira/browse/CASSANDRA-5240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shahryar Sedghi updated CASSANDRA-5240:
---
Summary: CQL3 has error with Compund row keys when secondray index involved
(was: CQL3 has error with Compund row keys when sceondray index involved)
CQL3 has error with Compund row keys when secondray index involved
--
Key: CASSANDRA-5240
URL: https://issues.apache.org/jira/browse/CASSANDRA-5240
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 1.2.1
Environment: Linux centos 6.3
Reporter: Shahryar Sedghi
Priority: Blocker
CREATE TABLE test(
interval text,
seq int,
id int,
severity int,
PRIMARY KEY ((interval, seq), id))
WITH CLUSTERING ORDER BY (id DESC);
--
CREATE INDEX ON test(severity);
insert into test(interval, seq, id , severity) values('t',1, 1, 1);
insert into test(interval, seq, id , severity) values('t',1, 2, 1);
insert into test(interval, seq, id , severity) values('t',1, 3, 2);
insert into test(interval, seq, id , severity) values('t',1, 4, 3);
insert into test(interval, seq, id , severity) values('t',2, 1, 3);
insert into test(interval, seq, id , severity) values('t',2, 2, 3);
insert into test(interval, seq, id , severity) values('t',2, 3, 1);
insert into test(interval, seq, id , severity) values('t',2, 4, 2);
select * from test where severity = 3 and interval = 't' and seq =1;
Bad Request: Start key sorts after end key. This is not allowed; you probably
should not specify end key at all under random partitioner
The following works fine
CREATE TABLE test(
interval text,
id int,
severity int,
PRIMARY KEY (interval, id))
WITH CLUSTERING ORDER BY (id DESC);
--
CREATE INDEX ON test(severity);
insert into test(interval, id , severity) values('t1', 4, 1);
insert into test(interval, id , severity) values('t1', 1, 3);
insert into test(interval, id , severity) values('t1', 2, 2);
insert into test(interval, id , severity) values('t1', 3, 3);
insert into test(interval, id , severity) values('t2', 3, 3);
insert into test(interval, id , severity) values('t2', 1, 3);
insert into test(interval, id , severity) values('t2', 2, 1);
select * from test where severity = 3 and interval = 't1';
interval | id | severity
--++--
t1 | 3 |3
t1 | 1 |3
--
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] [Updated] (CASSANDRA-5231) Add username autocompletion to cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-5231: - Attachment: (was: 5231.txt) Add username autocompletion to cqlsh Key: CASSANDRA-5231 URL: https://issues.apache.org/jira/browse/CASSANDRA-5231 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Aleksey Yeschenko Assignee: Aleksey Yeschenko Priority: Trivial Labels: cqlsh Fix For: 1.2.2 Add cqlsh username autocompletion to grant/revoke/list/drop/alter queries. -- 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] [Updated] (CASSANDRA-5231) Add username autocompletion to cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Yeschenko updated CASSANDRA-5231: - Attachment: 5231.txt Here is the right one. Add username autocompletion to cqlsh Key: CASSANDRA-5231 URL: https://issues.apache.org/jira/browse/CASSANDRA-5231 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Aleksey Yeschenko Assignee: Aleksey Yeschenko Priority: Trivial Labels: cqlsh Fix For: 1.2.2 Attachments: 5231.txt Add cqlsh username autocompletion to grant/revoke/list/drop/alter queries. -- 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
[Cassandra Wiki] Update of ClientOptions by Max Penet
Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The ClientOptions page has been changed by Max Penet: http://wiki.apache.org/cassandra/ClientOptions?action=diffrev1=165rev2=166 * clj-hector: https://github.com/pingles/clj-hector * casyn: https://github.com/mpenet/casyn * alia: https://github.com/mpenet/alia (datastax/java-driver wrapper) + * hayt (CQL3 query generation): https://github.com/mpenet/hayt * .NET * Aquiles: http://aquiles.codeplex.com/ * Cassandraemon: http://cassandraemon.codeplex.com/
[jira] [Created] (CASSANDRA-5267) Index organized table
Srdjan Mitrovic created CASSANDRA-5267:
--
Summary: Index organized table
Key: CASSANDRA-5267
URL: https://issues.apache.org/jira/browse/CASSANDRA-5267
Project: Cassandra
Issue Type: Improvement
Reporter: Srdjan Mitrovic
Priority: Minor
The purpose is to enable very fast scans for queries which use WHERE
indexed_column_value='foo';
We could borrow syntax from Oracle (with a small difference).
{noformat}CREATE TABLE blog_entries (
posted_at timestamp,
blog_id int
author text,
content text,
PRIMARY KEY (posted_at)
)
ORGANIZATION INDEX ON (blog_id);
{noformat}
In the background we could have a CF having only (key, indexed_value), in this
case (posted_at, blog_id) so that we can maintain our index when we delete a
row or change blog_id, and we would store other values within the index.
--
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
[Cassandra Wiki] Trivial Update of JannieKel by JannieKel
Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The JannieKel page has been changed by JannieKel: http://wiki.apache.org/cassandra/JannieKel?action=diffrev1=1rev2=2 - Hey !! I am RANA MANNING. Soon i will turn 52.BR - I go to night school at The Gleeful Institute situated in St. Petersburg. My dad name is Matt and he is a Undertaker. My mother is a Referee.BR + Yo guys !! The name is MAYBELLE LYNN. I am turning 26.BR + I am taking admission in The Skeptical Preparatory located in Mesquite. My father name is Peter and he is a Floor Manager. My mummy is a Servant.BR BR - Here is my page [[http://h2o-xpo.org/beatsbydrecheap.aspx|beats headphones review]] + My web-site - [[http://www.blindchildrenscenter.org/cheapbeatsheadphones.html|cheap beats by]]
[Cassandra Wiki] Trivial Update of KatiaSett by KatiaSett
Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The KatiaSett page has been changed by KatiaSett: http://wiki.apache.org/cassandra/KatiaSett?action=diffrev1=1rev2=2 - Yo guys !! I am MACIE CLARKE. Soon i will turn 26. I and my sister go to The Successful Prep School situated in Harlingen.BR - I have a job as Driver.BR + Hello !! The name is ELSIE BUCKNER. I am 38. I and my sister go to The Rare Military School situated in Wolverhampton.BR + I am planning to become a Pilot.BR BR - Also visit my web page ... [[http://www.majorreplicahandbags.com|designer handbags]] + My blog post :: [[http://www.majorreplicahandbags.com|replica handbags]]
git commit: Fix stress with CQL3
Updated Branches:
refs/heads/cassandra-1.2 aef01d162 - 4cd813632
Fix stress with CQL3
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/4cd81363
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/4cd81363
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/4cd81363
Branch: refs/heads/cassandra-1.2
Commit: 4cd813632d7e03adae1f8b519be65e0d65b7eaad
Parents: aef01d1
Author: Sylvain Lebresne sylv...@datastax.com
Authored: Tue Feb 19 00:01:41 2013 +0100
Committer: Sylvain Lebresne sylv...@datastax.com
Committed: Tue Feb 19 00:01:41 2013 +0100
--
.../stress/operations/CqlCounterAdder.java |6 ++--
.../stress/operations/CqlCounterGetter.java|6 ++--
.../stress/operations/CqlIndexedRangeSlicer.java |4 +-
.../cassandra/stress/operations/CqlInserter.java |4 +-
.../stress/operations/CqlRangeSlicer.java |6 ++--
.../cassandra/stress/operations/CqlReader.java |4 +-
.../apache/cassandra/stress/util/Operation.java| 16 +-
7 files changed, 25 insertions(+), 21 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/4cd81363/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterAdder.java
--
diff --git
a/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterAdder.java
b/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterAdder.java
index e1e4e9a..b0633ea 100644
---
a/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterAdder.java
+++
b/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterAdder.java
@@ -88,14 +88,14 @@ public class CqlCounterAdder extends Operation
{
Integer stmntId = getPreparedStatement(client, cqlQuery);
if (session.cqlVersion.startsWith(3))
-client.execute_prepared_cql3_query(stmntId,
Collections.singletonList(ByteBufferUtil.bytes(getUnQuotedCqlBlob(key))),
session.getConsistencyLevel());
+client.execute_prepared_cql3_query(stmntId,
Collections.singletonList(ByteBuffer.wrap(key.getBytes())),
session.getConsistencyLevel());
else
-client.execute_prepared_cql_query(stmntId,
Collections.singletonList(ByteBufferUtil.bytes(getUnQuotedCqlBlob(key;
+client.execute_prepared_cql_query(stmntId,
Collections.singletonList(ByteBuffer.wrap(key.getBytes(;
}
else
{
if (formattedQuery == null)
-formattedQuery = formatCqlQuery(cqlQuery,
Collections.singletonList(getUnQuotedCqlBlob(key)));
+formattedQuery = formatCqlQuery(cqlQuery,
Collections.singletonList(getUnQuotedCqlBlob(key,
session.cqlVersion.startsWith(3;
if (session.cqlVersion.startsWith(3))
client.execute_cql3_query(ByteBuffer.wrap(formattedQuery.getBytes()),
Compression.NONE, session.getConsistencyLevel());
else
http://git-wip-us.apache.org/repos/asf/cassandra/blob/4cd81363/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterGetter.java
--
diff --git
a/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterGetter.java
b/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterGetter.java
index db99d0d..7feee5b 100644
---
a/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterGetter.java
+++
b/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterGetter.java
@@ -89,14 +89,14 @@ public class CqlCounterGetter extends Operation
{
Integer stmntId = getPreparedStatement(client, cqlQuery);
if (session.cqlVersion.startsWith(3))
-result = client.execute_prepared_cql3_query(stmntId,
Collections.singletonList(ByteBufferUtil.bytes(getUnQuotedCqlBlob(key))),
session.getConsistencyLevel());
+result = client.execute_prepared_cql3_query(stmntId,
Collections.singletonList(ByteBuffer.wrap(key)), session.getConsistencyLevel());
else
-result = client.execute_prepared_cql_query(stmntId,
Collections.singletonList(ByteBufferUtil.bytes(getUnQuotedCqlBlob(key;
+result = client.execute_prepared_cql_query(stmntId,
Collections.singletonList(ByteBuffer.wrap(key)));
}
else
{
if (formattedQuery == null)
-formattedQuery = formatCqlQuery(cqlQuery,
[2/2] git commit: Merge branch 'cassandra-1.2' into trunk
Updated Branches: refs/heads/trunk 278a5e860 - 6190a711c Merge branch 'cassandra-1.2' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/6190a711 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/6190a711 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/6190a711 Branch: refs/heads/trunk Commit: 6190a711c6c1b27828349973eab9b06e946ad8c1 Parents: 278a5e8 4cd8136 Author: Sylvain Lebresne sylv...@datastax.com Authored: Tue Feb 19 00:02:19 2013 +0100 Committer: Sylvain Lebresne sylv...@datastax.com Committed: Tue Feb 19 00:02:19 2013 +0100 -- .../stress/operations/CqlCounterAdder.java |6 ++-- .../stress/operations/CqlCounterGetter.java|6 ++-- .../stress/operations/CqlIndexedRangeSlicer.java |4 +- .../cassandra/stress/operations/CqlInserter.java |4 +- .../stress/operations/CqlRangeSlicer.java |6 ++-- .../cassandra/stress/operations/CqlReader.java |4 +- .../apache/cassandra/stress/util/Operation.java| 16 +- 7 files changed, 25 insertions(+), 21 deletions(-) --
[1/2] git commit: Fix stress with CQL3
Fix stress with CQL3
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/4cd81363
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/4cd81363
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/4cd81363
Branch: refs/heads/trunk
Commit: 4cd813632d7e03adae1f8b519be65e0d65b7eaad
Parents: aef01d1
Author: Sylvain Lebresne sylv...@datastax.com
Authored: Tue Feb 19 00:01:41 2013 +0100
Committer: Sylvain Lebresne sylv...@datastax.com
Committed: Tue Feb 19 00:01:41 2013 +0100
--
.../stress/operations/CqlCounterAdder.java |6 ++--
.../stress/operations/CqlCounterGetter.java|6 ++--
.../stress/operations/CqlIndexedRangeSlicer.java |4 +-
.../cassandra/stress/operations/CqlInserter.java |4 +-
.../stress/operations/CqlRangeSlicer.java |6 ++--
.../cassandra/stress/operations/CqlReader.java |4 +-
.../apache/cassandra/stress/util/Operation.java| 16 +-
7 files changed, 25 insertions(+), 21 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/4cd81363/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterAdder.java
--
diff --git
a/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterAdder.java
b/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterAdder.java
index e1e4e9a..b0633ea 100644
---
a/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterAdder.java
+++
b/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterAdder.java
@@ -88,14 +88,14 @@ public class CqlCounterAdder extends Operation
{
Integer stmntId = getPreparedStatement(client, cqlQuery);
if (session.cqlVersion.startsWith(3))
-client.execute_prepared_cql3_query(stmntId,
Collections.singletonList(ByteBufferUtil.bytes(getUnQuotedCqlBlob(key))),
session.getConsistencyLevel());
+client.execute_prepared_cql3_query(stmntId,
Collections.singletonList(ByteBuffer.wrap(key.getBytes())),
session.getConsistencyLevel());
else
-client.execute_prepared_cql_query(stmntId,
Collections.singletonList(ByteBufferUtil.bytes(getUnQuotedCqlBlob(key;
+client.execute_prepared_cql_query(stmntId,
Collections.singletonList(ByteBuffer.wrap(key.getBytes(;
}
else
{
if (formattedQuery == null)
-formattedQuery = formatCqlQuery(cqlQuery,
Collections.singletonList(getUnQuotedCqlBlob(key)));
+formattedQuery = formatCqlQuery(cqlQuery,
Collections.singletonList(getUnQuotedCqlBlob(key,
session.cqlVersion.startsWith(3;
if (session.cqlVersion.startsWith(3))
client.execute_cql3_query(ByteBuffer.wrap(formattedQuery.getBytes()),
Compression.NONE, session.getConsistencyLevel());
else
http://git-wip-us.apache.org/repos/asf/cassandra/blob/4cd81363/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterGetter.java
--
diff --git
a/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterGetter.java
b/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterGetter.java
index db99d0d..7feee5b 100644
---
a/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterGetter.java
+++
b/tools/stress/src/org/apache/cassandra/stress/operations/CqlCounterGetter.java
@@ -89,14 +89,14 @@ public class CqlCounterGetter extends Operation
{
Integer stmntId = getPreparedStatement(client, cqlQuery);
if (session.cqlVersion.startsWith(3))
-result = client.execute_prepared_cql3_query(stmntId,
Collections.singletonList(ByteBufferUtil.bytes(getUnQuotedCqlBlob(key))),
session.getConsistencyLevel());
+result = client.execute_prepared_cql3_query(stmntId,
Collections.singletonList(ByteBuffer.wrap(key)), session.getConsistencyLevel());
else
-result = client.execute_prepared_cql_query(stmntId,
Collections.singletonList(ByteBufferUtil.bytes(getUnQuotedCqlBlob(key;
+result = client.execute_prepared_cql_query(stmntId,
Collections.singletonList(ByteBuffer.wrap(key)));
}
else
{
if (formattedQuery == null)
-formattedQuery = formatCqlQuery(cqlQuery,
Collections.singletonList(getUnQuotedCqlBlob(key)));
+
[jira] [Created] (CASSANDRA-5268) nodetool setcompactionthroughput has no effect
Pas created CASSANDRA-5268: -- Summary: nodetool setcompactionthroughput has no effect Key: CASSANDRA-5268 URL: https://issues.apache.org/jira/browse/CASSANDRA-5268 Project: Cassandra Issue Type: Bug Affects Versions: 1.1.10 Environment: Linux gravity-jasmapp-1 3.2.0-0.bpo.4-amd64 #1 SMP Debian 3.2.32-1~bpo60+1 x86_64 GNU/Linux, java version 1.7.0_07 Reporter: Pas issuing a nodetool setcompactionthroughput 64 has no effect (not even a line in the log), and compactions go merrily about ~20MB/s on an SSD with fairly low utilization (iostat -xm 1 shows ~30-60% util, probably due to reads and other processes on the host) Token: Token(bytes[3030]) Gossip active: true Thrift active: true Load : 106 GB Generation No: 1361216406 Uptime (seconds) : 13825 Heap Memory (MB) : 2829.19 / 9158.88 Data Center : datacenter1 Rack : rack1 Exceptions : 0 Key Cache: size 104857584 (bytes), capacity 104857584 (bytes), 20638124 hits, 20948679 requests, 0.985 recent hit rate, 14400 save period in seconds Row Cache: size 0 (bytes), capacity 0 (bytes), 0 hits, 0 requests, NaN recent hit rate, 0 save period in seconds -- 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
[Cassandra Wiki] Trivial Update of NoeeehuqO by NoeeehuqO
Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The NoeeehuqO page has been changed by NoeeehuqO: http://wiki.apache.org/cassandra/NoeeehuqO New page: I am 37 years old and my name is Mittie Keegan. I life in Scalasaig (Great Britain).BR BR BR BR Feel free to surf to my blog post; [[http://fmp3d.com|free mp3 download]]
[jira] [Commented] (CASSANDRA-5231) Add username autocompletion to cqlsh
[ https://issues.apache.org/jira/browse/CASSANDRA-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580907#comment-13580907 ] Brandon Williams commented on CASSANDRA-5231: - lgtm, +1 Add username autocompletion to cqlsh Key: CASSANDRA-5231 URL: https://issues.apache.org/jira/browse/CASSANDRA-5231 Project: Cassandra Issue Type: Improvement Components: Tools Reporter: Aleksey Yeschenko Assignee: Aleksey Yeschenko Priority: Trivial Labels: cqlsh Fix For: 1.2.2 Attachments: 5231.txt Add cqlsh username autocompletion to grant/revoke/list/drop/alter queries. -- 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
[Cassandra Wiki] Trivial Update of ZacheryCo by ZacheryCo
Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The ZacheryCo page has been changed by ZacheryCo: http://wiki.apache.org/cassandra/ZacheryCo New page: Hey fellas !! My name is DEANA BOYD. I am from Cambridge.BR BR Soon i will turn 55. I might take night schooling in The Practical Academy located in St Davids. I also like to Aquarium. My dad name is Ian and he is a Surgeon. My mom is a Ethologist.BR BR Feel free to visit my website; [[http://www.reachreplicahandbags.com|cheap designer handbags]]
[Cassandra Wiki] Trivial Update of MatildaKY by MatildaKY
Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The MatildaKY page has been changed by MatildaKY: http://wiki.apache.org/cassandra/MatildaKY New page: There is nothing to tell about myself at all.BR I enjoy of finally being a member of apache.org.BR I really hope I'm useful in some way .BR BR Visit my page [[http://www.crownmarble.ca|click through the up coming internet page]]
[jira] [Resolved] (CASSANDRA-5267) Index organized table
[
https://issues.apache.org/jira/browse/CASSANDRA-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-5267.
---
Resolution: Won't Fix
This doesn't work with Cassandra's storage engine. Partitions are ordered by
the partitioner, and data within a partition is ordered by the comparator...
Index organized table
-
Key: CASSANDRA-5267
URL: https://issues.apache.org/jira/browse/CASSANDRA-5267
Project: Cassandra
Issue Type: Improvement
Reporter: Srdjan Mitrovic
Priority: Minor
The purpose is to enable very fast scans for queries which use WHERE
indexed_column_value='foo';
We could borrow syntax from Oracle (with a small difference).
{noformat}CREATE TABLE blog_entries (
posted_at timestamp,
blog_id int
author text,
content text,
PRIMARY KEY (posted_at)
)
ORGANIZATION INDEX ON (blog_id);
{noformat}
In the background we could have a CF having only (key, indexed_value), in
this case (posted_at, blog_id) so that we can maintain our index when we
delete a row or change blog_id, and we would store other values within the
index.
--
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
[Cassandra Wiki] Trivial Update of RosettaRo by RosettaRo
Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The RosettaRo page has been changed by RosettaRo: http://wiki.apache.org/cassandra/RosettaRo New page: Howdy !! The name is CHERRI WALLACE. This autumun iam going to be 44.BR BR I might take night schooling in The Brave Military School in Lowell. I want to become a Surgeon.BR BR My homepage: [[http://www.approachchanelbags.com|chanel replica]]
[jira] [Commented] (CASSANDRA-5267) Index organized table
[
https://issues.apache.org/jira/browse/CASSANDRA-5267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580981#comment-13580981
]
Srdjan Mitrovic commented on CASSANDRA-5267:
I was probably misunderstood, this is just a secondary index with some extra
info stored (beside keys) so partitions are still ordered by partitioner and
data by comparator.
Benefit is that we don't need to read original CF for other data when we query
by index. If this is not possible can you tell me if there is a wiki explaining
internal architecture so that I can read that before creating issues.
Thanks.
Index organized table
-
Key: CASSANDRA-5267
URL: https://issues.apache.org/jira/browse/CASSANDRA-5267
Project: Cassandra
Issue Type: Improvement
Reporter: Srdjan Mitrovic
Priority: Minor
The purpose is to enable very fast scans for queries which use WHERE
indexed_column_value='foo';
We could borrow syntax from Oracle (with a small difference).
{noformat}CREATE TABLE blog_entries (
posted_at timestamp,
blog_id int
author text,
content text,
PRIMARY KEY (posted_at)
)
ORGANIZATION INDEX ON (blog_id);
{noformat}
In the background we could have a CF having only (key, indexed_value), in
this case (posted_at, blog_id) so that we can maintain our index when we
delete a row or change blog_id, and we would store other values within the
index.
--
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
[Cassandra Wiki] Trivial Update of GabrielaG by GabrielaG
Dear Wiki user, You have subscribed to a wiki page or wiki category on Cassandra Wiki for change notification. The GabrielaG page has been changed by GabrielaG: http://wiki.apache.org/cassandra/GabrielaG New page: Nothing to tell about myself at all.BR Finally a part of this site.BR I just hope I'm useful in some way here.BR BR Look at my webpage :: [[http://athomekeratintreatment.blogspot.com|best at home keratin treatment]]
git commit: cqlsh: Add username autocompletion
Updated Branches:
refs/heads/cassandra-1.2 4cd813632 - df6983bba
cqlsh: Add username autocompletion
patch by Aleksey Yeschenko; reviewed by Brandon Williams for
CASSANDRA-5231
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/df6983bb
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/df6983bb
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/df6983bb
Branch: refs/heads/cassandra-1.2
Commit: df6983bbad7f004aac52cfe78c5fb41e8a3871bc
Parents: 4cd8136
Author: Aleksey Yeschenko alek...@apache.org
Authored: Tue Feb 19 07:21:08 2013 +0300
Committer: Aleksey Yeschenko alek...@apache.org
Committed: Tue Feb 19 07:21:08 2013 +0300
--
CHANGES.txt|1 +
pylib/cqlshlib/cql3handling.py | 21 ++---
2 files changed, 15 insertions(+), 7 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/df6983bb/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index ad8c3f2..a543ac1 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -25,6 +25,7 @@
* Fix timestamp-based tomstone removal logic (CASSANDRA-5248)
* cli: Add JMX authentication support (CASSANDRA-5080)
* Fix forceFlush behavior (CASSANDRA-5241)
+ * cqlsh: Add username autocompletion (CASSANDRA-5231)
1.2.1
http://git-wip-us.apache.org/repos/asf/cassandra/blob/df6983bb/pylib/cqlshlib/cql3handling.py
--
diff --git a/pylib/cqlshlib/cql3handling.py b/pylib/cqlshlib/cql3handling.py
index def573e..00e2d0f 100644
--- a/pylib/cqlshlib/cql3handling.py
+++ b/pylib/cqlshlib/cql3handling.py
@@ -1256,7 +1256,7 @@ syntax_rules += r'''
'''
syntax_rules += r'''
-username ::= user=( identifier | stringLiteral )
+username ::= name=( identifier | stringLiteral )
;
createUserStatement ::= CREATE USER username
@@ -1308,13 +1308,20 @@ syntax_rules += r'''
;
'''
+@completer_for('username', 'name')
+def username_name_completer(ctxt, cass):
+def maybe_quote(name):
+if CqlRuleSet.is_valid_cql3_name(name):
+return name
+return '%s' % name
+
+# disable completion for CREATE USER.
+if ctxt.matched[0][0] == 'K_CREATE':
+return [Hint('username')]
-@completer_for('username', 'user')
-def username_user_completer(ctxt, cass):
-# TODO: implement user autocompletion for grant/revoke/list/drop
user/alter user
-# with I could see a way to do this usefully, but I don't. I don't know
-# how any Authorities other than AllowAllAuthorizer work :/
-return [Hint('username')]
+cursor = cass.conn.cursor()
+cursor.execute(LIST USERS)
+return [maybe_quote(row[0].replace(', '')) for row in
cursor.fetchall()]
# END SYNTAX/COMPLETION RULE DEFINITIONS
[1/2] git commit: cqlsh: Add username autocompletion
cqlsh: Add username autocompletion
patch by Aleksey Yeschenko; reviewed by Brandon Williams for
CASSANDRA-5231
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo
Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/df6983bb
Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/df6983bb
Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/df6983bb
Branch: refs/heads/trunk
Commit: df6983bbad7f004aac52cfe78c5fb41e8a3871bc
Parents: 4cd8136
Author: Aleksey Yeschenko alek...@apache.org
Authored: Tue Feb 19 07:21:08 2013 +0300
Committer: Aleksey Yeschenko alek...@apache.org
Committed: Tue Feb 19 07:21:08 2013 +0300
--
CHANGES.txt|1 +
pylib/cqlshlib/cql3handling.py | 21 ++---
2 files changed, 15 insertions(+), 7 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/cassandra/blob/df6983bb/CHANGES.txt
--
diff --git a/CHANGES.txt b/CHANGES.txt
index ad8c3f2..a543ac1 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -25,6 +25,7 @@
* Fix timestamp-based tomstone removal logic (CASSANDRA-5248)
* cli: Add JMX authentication support (CASSANDRA-5080)
* Fix forceFlush behavior (CASSANDRA-5241)
+ * cqlsh: Add username autocompletion (CASSANDRA-5231)
1.2.1
http://git-wip-us.apache.org/repos/asf/cassandra/blob/df6983bb/pylib/cqlshlib/cql3handling.py
--
diff --git a/pylib/cqlshlib/cql3handling.py b/pylib/cqlshlib/cql3handling.py
index def573e..00e2d0f 100644
--- a/pylib/cqlshlib/cql3handling.py
+++ b/pylib/cqlshlib/cql3handling.py
@@ -1256,7 +1256,7 @@ syntax_rules += r'''
'''
syntax_rules += r'''
-username ::= user=( identifier | stringLiteral )
+username ::= name=( identifier | stringLiteral )
;
createUserStatement ::= CREATE USER username
@@ -1308,13 +1308,20 @@ syntax_rules += r'''
;
'''
+@completer_for('username', 'name')
+def username_name_completer(ctxt, cass):
+def maybe_quote(name):
+if CqlRuleSet.is_valid_cql3_name(name):
+return name
+return '%s' % name
+
+# disable completion for CREATE USER.
+if ctxt.matched[0][0] == 'K_CREATE':
+return [Hint('username')]
-@completer_for('username', 'user')
-def username_user_completer(ctxt, cass):
-# TODO: implement user autocompletion for grant/revoke/list/drop
user/alter user
-# with I could see a way to do this usefully, but I don't. I don't know
-# how any Authorities other than AllowAllAuthorizer work :/
-return [Hint('username')]
+cursor = cass.conn.cursor()
+cursor.execute(LIST USERS)
+return [maybe_quote(row[0].replace(', '')) for row in
cursor.fetchall()]
# END SYNTAX/COMPLETION RULE DEFINITIONS
[2/2] git commit: Merge branch 'cassandra-1.2' into trunk
Updated Branches: refs/heads/trunk 6190a711c - 624d82308 Merge branch 'cassandra-1.2' into trunk Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/624d8230 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/624d8230 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/624d8230 Branch: refs/heads/trunk Commit: 624d82308747b2ab44767214ff2bee5dfc623dad Parents: 6190a71 df6983b Author: Aleksey Yeschenko alek...@apache.org Authored: Tue Feb 19 07:26:50 2013 +0300 Committer: Aleksey Yeschenko alek...@apache.org Committed: Tue Feb 19 07:26:50 2013 +0300 -- CHANGES.txt|1 + pylib/cqlshlib/cql3handling.py | 21 ++--- 2 files changed, 15 insertions(+), 7 deletions(-) -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/624d8230/CHANGES.txt -- http://git-wip-us.apache.org/repos/asf/cassandra/blob/624d8230/pylib/cqlshlib/cql3handling.py --
