You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Chris Goffinet (JIRA)" <ji...@apache.org> on 2010/10/20 22:24:25 UTC

[jira] Created: (CASSANDRA-1638) initMetadata does not load partitioner from disk

initMetadata does not load partitioner from disk
------------------------------------------------

                 Key: CASSANDRA-1638
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1638
             Project: Cassandra
          Issue Type: Bug
          Components: Core
    Affects Versions: 0.6.6
            Reporter: Chris Goffinet
            Assignee: Chris Goffinet
            Priority: Minor
             Fix For: 0.6.7


The function initMetadata() in org/apache/cassandra/db/SystemTable.java does not add the PARTITIONER constant to columns. So when the NamesQueryFilter runs, it will never pull the value from disk. This makes this portion of the code always null:

        if (partitionerColumn == null)
        {
            Column c = new Column(PARTITIONER, partitioner.getBytes("UTF-8"), TimestampClock.ZERO);
            cf.addColumn(c);
            logger.info("Saved partitioner not found. Using " + partitioner);
        }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (CASSANDRA-1638) initMetadata does not load partitioner from disk

Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Dusbabek resolved CASSANDRA-1638.
--------------------------------------

    Resolution: Fixed

0.7 and trunk didn't need changes.

> initMetadata does not load partitioner from disk
> ------------------------------------------------
>
>                 Key: CASSANDRA-1638
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1638
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.6.6
>            Reporter: Chris Goffinet
>            Assignee: Chris Goffinet
>            Priority: Minor
>             Fix For: 0.6.7
>
>         Attachments: 0001-Fixed-initMetadata-to-load-on-disk-PARTITIONER-confi.patch
>
>
> The function initMetadata() in org/apache/cassandra/db/SystemTable.java does not add the PARTITIONER constant to columns. So when the NamesQueryFilter runs, it will never pull the value from disk. This makes this portion of the code always null:
>         if (partitionerColumn == null)
>         {
>             Column c = new Column(PARTITIONER, partitioner.getBytes("UTF-8"), TimestampClock.ZERO);
>             cf.addColumn(c);
>             logger.info("Saved partitioner not found. Using " + partitioner);
>         }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (CASSANDRA-1638) initMetadata does not load partitioner from disk

Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924025#action_12924025 ] 

Gary Dusbabek commented on CASSANDRA-1638:
------------------------------------------

+1

> initMetadata does not load partitioner from disk
> ------------------------------------------------
>
>                 Key: CASSANDRA-1638
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1638
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.6.6
>            Reporter: Chris Goffinet
>            Assignee: Chris Goffinet
>            Priority: Minor
>             Fix For: 0.6.7
>
>         Attachments: 0001-Fixed-initMetadata-to-load-on-disk-PARTITIONER-confi.patch
>
>
> The function initMetadata() in org/apache/cassandra/db/SystemTable.java does not add the PARTITIONER constant to columns. So when the NamesQueryFilter runs, it will never pull the value from disk. This makes this portion of the code always null:
>         if (partitionerColumn == null)
>         {
>             Column c = new Column(PARTITIONER, partitioner.getBytes("UTF-8"), TimestampClock.ZERO);
>             cf.addColumn(c);
>             logger.info("Saved partitioner not found. Using " + partitioner);
>         }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Issue Comment Edited: (CASSANDRA-1638) initMetadata does not load partitioner from disk

Posted by "Gary Dusbabek (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926281#action_12926281 ] 

Gary Dusbabek edited comment on CASSANDRA-1638 at 10/29/10 9:46 AM:
--------------------------------------------------------------------

Committed. 

0.7 and trunk didn't need changes.

      was (Author: gdusbabek):
    0.7 and trunk didn't need changes.
  
> initMetadata does not load partitioner from disk
> ------------------------------------------------
>
>                 Key: CASSANDRA-1638
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1638
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.6.6
>            Reporter: Chris Goffinet
>            Assignee: Chris Goffinet
>            Priority: Minor
>             Fix For: 0.6.7
>
>         Attachments: 0001-Fixed-initMetadata-to-load-on-disk-PARTITIONER-confi.patch
>
>
> The function initMetadata() in org/apache/cassandra/db/SystemTable.java does not add the PARTITIONER constant to columns. So when the NamesQueryFilter runs, it will never pull the value from disk. This makes this portion of the code always null:
>         if (partitionerColumn == null)
>         {
>             Column c = new Column(PARTITIONER, partitioner.getBytes("UTF-8"), TimestampClock.ZERO);
>             cf.addColumn(c);
>             logger.info("Saved partitioner not found. Using " + partitioner);
>         }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (CASSANDRA-1638) initMetadata does not load partitioner from disk

Posted by "Chris Goffinet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CASSANDRA-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Goffinet updated CASSANDRA-1638:
--------------------------------------

    Attachment: 0001-Fixed-initMetadata-to-load-on-disk-PARTITIONER-confi.patch

> initMetadata does not load partitioner from disk
> ------------------------------------------------
>
>                 Key: CASSANDRA-1638
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1638
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.6.6
>            Reporter: Chris Goffinet
>            Assignee: Chris Goffinet
>            Priority: Minor
>             Fix For: 0.6.7
>
>         Attachments: 0001-Fixed-initMetadata-to-load-on-disk-PARTITIONER-confi.patch
>
>
> The function initMetadata() in org/apache/cassandra/db/SystemTable.java does not add the PARTITIONER constant to columns. So when the NamesQueryFilter runs, it will never pull the value from disk. This makes this portion of the code always null:
>         if (partitionerColumn == null)
>         {
>             Column c = new Column(PARTITIONER, partitioner.getBytes("UTF-8"), TimestampClock.ZERO);
>             cf.addColumn(c);
>             logger.info("Saved partitioner not found. Using " + partitioner);
>         }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.