You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Roger Mbiama (JIRA)" <ji...@apache.org> on 2011/07/10 14:11:59 UTC

[jira] [Created] (CASSANDRA-2877) git-cassandra-angosso-angosso.html

git-cassandra-angosso-angosso.html
----------------------------------

                 Key: CASSANDRA-2877
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2877
             Project: Cassandra
          Issue Type: Improvement
          Components: API
    Affects Versions: 0.8.0
         Environment: https://angosso@github.com/angosso/git-cassandra-angosso-angosso.html.git
http://angosso.git.sourceforge.net/git/gitweb-index.cgi configure include/config.h dlls/Makefile.in programs/Makefile.in */Makefile
            Reporter: Roger Mbiama
            Priority: Critical
             Fix For: 0.8.0


Requirements
------------
  * Java >= 1.6 (OpenJDK and Sun have been tested)

Getting started
---------------

This short guide will walk you through getting a basic one node cluster up
and running, and demonstrate some simple reads and writes.

  * tar -zxvf apache-cassandra-$VERSION.tar.gz
  * cd apache-cassandra-$VERSION
  * sudo mkdir -p /var/log/cassandra
  * sudo chown -R `angosso` /var/log/cassandra
  * sudo mkdir -p /var/lib/cassandra
  * sudo chown -R `angosso` /var/lib/cassandra

Note: The sample configuration files in conf/ determine the file-system 
locations Cassandra uses for logging and data storage. You are free to
change these to suit your own environment and adjust the path names
used here accordingly.

Now that we're ready, let's start it up!

  * bin/cassandra -f

Running the startup script with the -f argument will cause Cassandra to
remain in the foreground and log to standard out.

Now let's try to read and write some data using the command line client.

  * bin/cassandra-cli --host http://angosso1.w02.winhost.com --port 9160

The command line client is interactive so if everything worked you should
be sitting in front of a prompt...  
  Connected to http://angosso1.w02.winhost.com/9160
  Welcome to cassandra CLI.
  
  Type 'help' or '?' for help. Type 'quit' or 'exit' to quit.
  cassandra>

As the banner says, you can use 'help' or '?' to see what the CLI has to
offer, and 'quit' or 'exit' when you've had enough fun. But lets try
something slightly more interesting...

  cassandra> set Keyspace1.Standard2['rmbiama']['first'] = 'Roger'
  Value inserted.
  cassandra> set Keyspace1.Standard2['rmbiama']['last'] = 'mbiama'
  Value inserted.
  cassandra> set Keyspace1.Standard2['rmbiama']['age'] = '54'
  Value inserted.
  cassandra> get Keyspace1.Standard2['rmbiama']
    (column=age, value=42; timestamp=1249930062801)
    (column=first, value=Roger; timestamp=1249930053103)
    (column=last, value=Mbiama; timestamp=1249930058345)
  Returned 3 rows.
  cassandra>

If your session looks similar to what's above, congrats, your single node
cluster is operational! But what exactly was all of that? Let's break it
down into pieces and see.

  set Keyspace1.Standard2['rmbiama']['angosso / git-cassandra-angosso-angosso.html'] = 'Roger'
       \            \         \        \          \
        \            \         \_ key   \          \_ value
         \            \                  \_ column
          \_ keyspace  \_ column family

Data stored in Cassandra is associated with a column family (Standard2),
which in turn is associated with a keyspace (Keyspace1). In the example
above, we set the value 'Roger' in the 'first' column for key 'rmbiama'.

Mirror of Apache Cassandra (incubating); install schematool in debian package A commit object contains a (possibly empty) list of the logical predecessor(s) in the line of development, i.e. GIT-cassandra/angosso/angosso.html its parents.[rogerM] 


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CASSANDRA-2877) git-cassandra-angosso-angosso.html

Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195557#comment-13195557 ] 

Jonathan Ellis commented on CASSANDRA-2877:
-------------------------------------------

... what?
                
> git-cassandra-angosso-angosso.html
> ----------------------------------
>
>                 Key: CASSANDRA-2877
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2877
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 0.8.0
>         Environment: https://angosso@github.com/angosso/git-cassandra-angosso-angosso.html.git
> http://angosso.git.sourceforge.net/git/gitweb-index.cgi configure include/config.h dlls/Makefile.in programs/Makefile.in */Makefile
>            Reporter: Roger Mbiama
>            Priority: Critical
>              Labels: features
>             Fix For: 0.8.0
>
>         Attachments: CFMetaData.java, Config.java, ConfigurationException.java, ConfigurationException.java, Converter.java, DatabaseDescriptor.java, ReplicationStrategy.java, RequestSchedulerOptions.java, cassandra.bat, config-converter, json2sstable.bat, netbeans, netbeans.exe, sstable2json.bat
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> Requirements
> ------------
>   * Java >= 1.6 (OpenJDK and Sun have been tested)
> Getting started
> ---------------
> This short guide will walk you through getting a basic one node cluster up
> and running, and demonstrate some simple reads and writes.
>   * tar -zxvf apache-cassandra-$VERSION.tar.gz
>   * cd apache-cassandra-$VERSION
>   * sudo mkdir -p /var/log/cassandra
>   * sudo chown -R `angosso` /var/log/cassandra
>   * sudo mkdir -p /var/lib/cassandra
>   * sudo chown -R `angosso` /var/lib/cassandra
> Note: The sample configuration files in conf/ determine the file-system 
> locations Cassandra uses for logging and data storage. You are free to
> change these to suit your own environment and adjust the path names
> used here accordingly.
> Now that we're ready, let's start it up!
>   * bin/cassandra -f
> Running the startup script with the -f argument will cause Cassandra to
> remain in the foreground and log to standard out.
> Now let's try to read and write some data using the command line client.
>   * bin/cassandra-cli --host http://angosso1.w02.winhost.com --port 9160
> The command line client is interactive so if everything worked you should
> be sitting in front of a prompt...  
>   Connected to http://angosso1.w02.winhost.com/9160
>   Welcome to cassandra CLI.
>   
>   Type 'help' or '?' for help. Type 'quit' or 'exit' to quit.
>   cassandra>
> As the banner says, you can use 'help' or '?' to see what the CLI has to
> offer, and 'quit' or 'exit' when you've had enough fun. But lets try
> something slightly more interesting...
>   cassandra> set Keyspace1.Standard2['rmbiama']['first'] = 'Roger'
>   Value inserted.
>   cassandra> set Keyspace1.Standard2['rmbiama']['last'] = 'mbiama'
>   Value inserted.
>   cassandra> set Keyspace1.Standard2['rmbiama']['age'] = '54'
>   Value inserted.
>   cassandra> get Keyspace1.Standard2['rmbiama']
>     (column=age, value=54; timestamp=1249930062801)
>     (column=first, value=Roger; timestamp=1249930053103)
>     (column=last, value=Mbiama; timestamp=1249930058345)
>   Returned 3 rows.
>   cassandra>
> If your session looks similar to what's above, congrats, your single node
> cluster is operational! But what exactly was all of that? Let's break it
> down into pieces and see.
>   set Keyspace1.Standard2['rmbiama']['angosso / git-cassandra-angosso-angosso.html'] = 'Roger'
>        \            \         \        \          \
>         \            \         \_ key   \          \_ value
>          \            \                  \_ column
>           \_ keyspace  \_ column family
> Data stored in Cassandra is associated with a column family (Standard2),
> which in turn is associated with a keyspace (Keyspace1). In the example
> above, we set the value 'Roger' in the 'first' column for key 'rmbiama'.
> Mirror of Apache Cassandra (incubating); install schematool in debian package A commit object contains a (possibly empty) list of the logical predecessor(s) in the line of development, i.e. GIT-cassandra/angosso/angosso.html its parents.[rogerM] 

--
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-2877) git-cassandra-angosso-angosso.html

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

Roger Mbiama updated CASSANDRA-2877:
------------------------------------

    Attachment: CFMetaData.java
                ReplicationStrategy.java
                RequestSchedulerOptions.java
                Converter.java
                DatabaseDescriptor.java
                Config.java
                ConfigurationException.java
                netbeans
    
> git-cassandra-angosso-angosso.html
> ----------------------------------
>
>                 Key: CASSANDRA-2877
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2877
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 0.8.0
>         Environment: https://angosso@github.com/angosso/git-cassandra-angosso-angosso.html.git
> http://angosso.git.sourceforge.net/git/gitweb-index.cgi configure include/config.h dlls/Makefile.in programs/Makefile.in */Makefile
>            Reporter: Roger Mbiama
>            Priority: Critical
>              Labels: features
>             Fix For: 0.8.0
>
>         Attachments: CFMetaData.java, Config.java, ConfigurationException.java, Converter.java, DatabaseDescriptor.java, ReplicationStrategy.java, RequestSchedulerOptions.java, netbeans, netbeans.exe
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> Requirements
> ------------
>   * Java >= 1.6 (OpenJDK and Sun have been tested)
> Getting started
> ---------------
> This short guide will walk you through getting a basic one node cluster up
> and running, and demonstrate some simple reads and writes.
>   * tar -zxvf apache-cassandra-$VERSION.tar.gz
>   * cd apache-cassandra-$VERSION
>   * sudo mkdir -p /var/log/cassandra
>   * sudo chown -R `angosso` /var/log/cassandra
>   * sudo mkdir -p /var/lib/cassandra
>   * sudo chown -R `angosso` /var/lib/cassandra
> Note: The sample configuration files in conf/ determine the file-system 
> locations Cassandra uses for logging and data storage. You are free to
> change these to suit your own environment and adjust the path names
> used here accordingly.
> Now that we're ready, let's start it up!
>   * bin/cassandra -f
> Running the startup script with the -f argument will cause Cassandra to
> remain in the foreground and log to standard out.
> Now let's try to read and write some data using the command line client.
>   * bin/cassandra-cli --host http://angosso1.w02.winhost.com --port 9160
> The command line client is interactive so if everything worked you should
> be sitting in front of a prompt...  
>   Connected to http://angosso1.w02.winhost.com/9160
>   Welcome to cassandra CLI.
>   
>   Type 'help' or '?' for help. Type 'quit' or 'exit' to quit.
>   cassandra>
> As the banner says, you can use 'help' or '?' to see what the CLI has to
> offer, and 'quit' or 'exit' when you've had enough fun. But lets try
> something slightly more interesting...
>   cassandra> set Keyspace1.Standard2['rmbiama']['first'] = 'Roger'
>   Value inserted.
>   cassandra> set Keyspace1.Standard2['rmbiama']['last'] = 'mbiama'
>   Value inserted.
>   cassandra> set Keyspace1.Standard2['rmbiama']['age'] = '54'
>   Value inserted.
>   cassandra> get Keyspace1.Standard2['rmbiama']
>     (column=age, value=54; timestamp=1249930062801)
>     (column=first, value=Roger; timestamp=1249930053103)
>     (column=last, value=Mbiama; timestamp=1249930058345)
>   Returned 3 rows.
>   cassandra>
> If your session looks similar to what's above, congrats, your single node
> cluster is operational! But what exactly was all of that? Let's break it
> down into pieces and see.
>   set Keyspace1.Standard2['rmbiama']['angosso / git-cassandra-angosso-angosso.html'] = 'Roger'
>        \            \         \        \          \
>         \            \         \_ key   \          \_ value
>          \            \                  \_ column
>           \_ keyspace  \_ column family
> Data stored in Cassandra is associated with a column family (Standard2),
> which in turn is associated with a keyspace (Keyspace1). In the example
> above, we set the value 'Roger' in the 'first' column for key 'rmbiama'.
> Mirror of Apache Cassandra (incubating); install schematool in debian package A commit object contains a (possibly empty) list of the logical predecessor(s) in the line of development, i.e. GIT-cassandra/angosso/angosso.html its parents.[rogerM] 

--
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-2877) git-cassandra-angosso-angosso.html

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

Roger Mbiama updated CASSANDRA-2877:
------------------------------------

    Attachment: config-converter
                sstable2json.bat
                cassandra.bat
                json2sstable.bat
                ConfigurationException.java
    
> git-cassandra-angosso-angosso.html
> ----------------------------------
>
>                 Key: CASSANDRA-2877
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2877
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 0.8.0
>         Environment: https://angosso@github.com/angosso/git-cassandra-angosso-angosso.html.git
> http://angosso.git.sourceforge.net/git/gitweb-index.cgi configure include/config.h dlls/Makefile.in programs/Makefile.in */Makefile
>            Reporter: Roger Mbiama
>            Priority: Critical
>              Labels: features
>             Fix For: 0.8.0
>
>         Attachments: CFMetaData.java, Config.java, ConfigurationException.java, ConfigurationException.java, Converter.java, DatabaseDescriptor.java, ReplicationStrategy.java, RequestSchedulerOptions.java, cassandra.bat, config-converter, json2sstable.bat, netbeans, netbeans.exe, sstable2json.bat
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> Requirements
> ------------
>   * Java >= 1.6 (OpenJDK and Sun have been tested)
> Getting started
> ---------------
> This short guide will walk you through getting a basic one node cluster up
> and running, and demonstrate some simple reads and writes.
>   * tar -zxvf apache-cassandra-$VERSION.tar.gz
>   * cd apache-cassandra-$VERSION
>   * sudo mkdir -p /var/log/cassandra
>   * sudo chown -R `angosso` /var/log/cassandra
>   * sudo mkdir -p /var/lib/cassandra
>   * sudo chown -R `angosso` /var/lib/cassandra
> Note: The sample configuration files in conf/ determine the file-system 
> locations Cassandra uses for logging and data storage. You are free to
> change these to suit your own environment and adjust the path names
> used here accordingly.
> Now that we're ready, let's start it up!
>   * bin/cassandra -f
> Running the startup script with the -f argument will cause Cassandra to
> remain in the foreground and log to standard out.
> Now let's try to read and write some data using the command line client.
>   * bin/cassandra-cli --host http://angosso1.w02.winhost.com --port 9160
> The command line client is interactive so if everything worked you should
> be sitting in front of a prompt...  
>   Connected to http://angosso1.w02.winhost.com/9160
>   Welcome to cassandra CLI.
>   
>   Type 'help' or '?' for help. Type 'quit' or 'exit' to quit.
>   cassandra>
> As the banner says, you can use 'help' or '?' to see what the CLI has to
> offer, and 'quit' or 'exit' when you've had enough fun. But lets try
> something slightly more interesting...
>   cassandra> set Keyspace1.Standard2['rmbiama']['first'] = 'Roger'
>   Value inserted.
>   cassandra> set Keyspace1.Standard2['rmbiama']['last'] = 'mbiama'
>   Value inserted.
>   cassandra> set Keyspace1.Standard2['rmbiama']['age'] = '54'
>   Value inserted.
>   cassandra> get Keyspace1.Standard2['rmbiama']
>     (column=age, value=54; timestamp=1249930062801)
>     (column=first, value=Roger; timestamp=1249930053103)
>     (column=last, value=Mbiama; timestamp=1249930058345)
>   Returned 3 rows.
>   cassandra>
> If your session looks similar to what's above, congrats, your single node
> cluster is operational! But what exactly was all of that? Let's break it
> down into pieces and see.
>   set Keyspace1.Standard2['rmbiama']['angosso / git-cassandra-angosso-angosso.html'] = 'Roger'
>        \            \         \        \          \
>         \            \         \_ key   \          \_ value
>          \            \                  \_ column
>           \_ keyspace  \_ column family
> Data stored in Cassandra is associated with a column family (Standard2),
> which in turn is associated with a keyspace (Keyspace1). In the example
> above, we set the value 'Roger' in the 'first' column for key 'rmbiama'.
> Mirror of Apache Cassandra (incubating); install schematool in debian package A commit object contains a (possibly empty) list of the logical predecessor(s) in the line of development, i.e. GIT-cassandra/angosso/angosso.html its parents.[rogerM] 

--
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-2877) git-cassandra-angosso-angosso.html

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

Roger Mbiama updated CASSANDRA-2877:
------------------------------------

    Description: 
Requirements
------------
  * Java >= 1.6 (OpenJDK and Sun have been tested)

Getting started
---------------

This short guide will walk you through getting a basic one node cluster up
and running, and demonstrate some simple reads and writes.

  * tar -zxvf apache-cassandra-$VERSION.tar.gz
  * cd apache-cassandra-$VERSION
  * sudo mkdir -p /var/log/cassandra
  * sudo chown -R `angosso` /var/log/cassandra
  * sudo mkdir -p /var/lib/cassandra
  * sudo chown -R `angosso` /var/lib/cassandra

Note: The sample configuration files in conf/ determine the file-system 
locations Cassandra uses for logging and data storage. You are free to
change these to suit your own environment and adjust the path names
used here accordingly.

Now that we're ready, let's start it up!

  * bin/cassandra -f

Running the startup script with the -f argument will cause Cassandra to
remain in the foreground and log to standard out.

Now let's try to read and write some data using the command line client.

  * bin/cassandra-cli --host http://angosso1.w02.winhost.com --port 9160

The command line client is interactive so if everything worked you should
be sitting in front of a prompt...  
  Connected to http://angosso1.w02.winhost.com/9160
  Welcome to cassandra CLI.
  
  Type 'help' or '?' for help. Type 'quit' or 'exit' to quit.
  cassandra>

As the banner says, you can use 'help' or '?' to see what the CLI has to
offer, and 'quit' or 'exit' when you've had enough fun. But lets try
something slightly more interesting...

  cassandra> set Keyspace1.Standard2['rmbiama']['first'] = 'Roger'
  Value inserted.
  cassandra> set Keyspace1.Standard2['rmbiama']['last'] = 'mbiama'
  Value inserted.
  cassandra> set Keyspace1.Standard2['rmbiama']['age'] = '54'
  Value inserted.
  cassandra> get Keyspace1.Standard2['rmbiama']
    (column=age, value=54; timestamp=1249930062801)
    (column=first, value=Roger; timestamp=1249930053103)
    (column=last, value=Mbiama; timestamp=1249930058345)
  Returned 3 rows.
  cassandra>

If your session looks similar to what's above, congrats, your single node
cluster is operational! But what exactly was all of that? Let's break it
down into pieces and see.

  set Keyspace1.Standard2['rmbiama']['angosso / git-cassandra-angosso-angosso.html'] = 'Roger'
       \            \         \        \          \
        \            \         \_ key   \          \_ value
         \            \                  \_ column
          \_ keyspace  \_ column family

Data stored in Cassandra is associated with a column family (Standard2),
which in turn is associated with a keyspace (Keyspace1). In the example
above, we set the value 'Roger' in the 'first' column for key 'rmbiama'.

Mirror of Apache Cassandra (incubating); install schematool in debian package A commit object contains a (possibly empty) list of the logical predecessor(s) in the line of development, i.e. GIT-cassandra/angosso/angosso.html its parents.[rogerM] 


  was:
Requirements
------------
  * Java >= 1.6 (OpenJDK and Sun have been tested)

Getting started
---------------

This short guide will walk you through getting a basic one node cluster up
and running, and demonstrate some simple reads and writes.

  * tar -zxvf apache-cassandra-$VERSION.tar.gz
  * cd apache-cassandra-$VERSION
  * sudo mkdir -p /var/log/cassandra
  * sudo chown -R `angosso` /var/log/cassandra
  * sudo mkdir -p /var/lib/cassandra
  * sudo chown -R `angosso` /var/lib/cassandra

Note: The sample configuration files in conf/ determine the file-system 
locations Cassandra uses for logging and data storage. You are free to
change these to suit your own environment and adjust the path names
used here accordingly.

Now that we're ready, let's start it up!

  * bin/cassandra -f

Running the startup script with the -f argument will cause Cassandra to
remain in the foreground and log to standard out.

Now let's try to read and write some data using the command line client.

  * bin/cassandra-cli --host http://angosso1.w02.winhost.com --port 9160

The command line client is interactive so if everything worked you should
be sitting in front of a prompt...  
  Connected to http://angosso1.w02.winhost.com/9160
  Welcome to cassandra CLI.
  
  Type 'help' or '?' for help. Type 'quit' or 'exit' to quit.
  cassandra>

As the banner says, you can use 'help' or '?' to see what the CLI has to
offer, and 'quit' or 'exit' when you've had enough fun. But lets try
something slightly more interesting...

  cassandra> set Keyspace1.Standard2['rmbiama']['first'] = 'Roger'
  Value inserted.
  cassandra> set Keyspace1.Standard2['rmbiama']['last'] = 'mbiama'
  Value inserted.
  cassandra> set Keyspace1.Standard2['rmbiama']['age'] = '54'
  Value inserted.
  cassandra> get Keyspace1.Standard2['rmbiama']
    (column=age, value=42; timestamp=1249930062801)
    (column=first, value=Roger; timestamp=1249930053103)
    (column=last, value=Mbiama; timestamp=1249930058345)
  Returned 3 rows.
  cassandra>

If your session looks similar to what's above, congrats, your single node
cluster is operational! But what exactly was all of that? Let's break it
down into pieces and see.

  set Keyspace1.Standard2['rmbiama']['angosso / git-cassandra-angosso-angosso.html'] = 'Roger'
       \            \         \        \          \
        \            \         \_ key   \          \_ value
         \            \                  \_ column
          \_ keyspace  \_ column family

Data stored in Cassandra is associated with a column family (Standard2),
which in turn is associated with a keyspace (Keyspace1). In the example
above, we set the value 'Roger' in the 'first' column for key 'rmbiama'.

Mirror of Apache Cassandra (incubating); install schematool in debian package A commit object contains a (possibly empty) list of the logical predecessor(s) in the line of development, i.e. GIT-cassandra/angosso/angosso.html its parents.[rogerM] 



> git-cassandra-angosso-angosso.html
> ----------------------------------
>
>                 Key: CASSANDRA-2877
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2877
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 0.8.0
>         Environment: https://angosso@github.com/angosso/git-cassandra-angosso-angosso.html.git
> http://angosso.git.sourceforge.net/git/gitweb-index.cgi configure include/config.h dlls/Makefile.in programs/Makefile.in */Makefile
>            Reporter: Roger Mbiama
>            Priority: Critical
>              Labels: features
>             Fix For: 0.8.0
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> Requirements
> ------------
>   * Java >= 1.6 (OpenJDK and Sun have been tested)
> Getting started
> ---------------
> This short guide will walk you through getting a basic one node cluster up
> and running, and demonstrate some simple reads and writes.
>   * tar -zxvf apache-cassandra-$VERSION.tar.gz
>   * cd apache-cassandra-$VERSION
>   * sudo mkdir -p /var/log/cassandra
>   * sudo chown -R `angosso` /var/log/cassandra
>   * sudo mkdir -p /var/lib/cassandra
>   * sudo chown -R `angosso` /var/lib/cassandra
> Note: The sample configuration files in conf/ determine the file-system 
> locations Cassandra uses for logging and data storage. You are free to
> change these to suit your own environment and adjust the path names
> used here accordingly.
> Now that we're ready, let's start it up!
>   * bin/cassandra -f
> Running the startup script with the -f argument will cause Cassandra to
> remain in the foreground and log to standard out.
> Now let's try to read and write some data using the command line client.
>   * bin/cassandra-cli --host http://angosso1.w02.winhost.com --port 9160
> The command line client is interactive so if everything worked you should
> be sitting in front of a prompt...  
>   Connected to http://angosso1.w02.winhost.com/9160
>   Welcome to cassandra CLI.
>   
>   Type 'help' or '?' for help. Type 'quit' or 'exit' to quit.
>   cassandra>
> As the banner says, you can use 'help' or '?' to see what the CLI has to
> offer, and 'quit' or 'exit' when you've had enough fun. But lets try
> something slightly more interesting...
>   cassandra> set Keyspace1.Standard2['rmbiama']['first'] = 'Roger'
>   Value inserted.
>   cassandra> set Keyspace1.Standard2['rmbiama']['last'] = 'mbiama'
>   Value inserted.
>   cassandra> set Keyspace1.Standard2['rmbiama']['age'] = '54'
>   Value inserted.
>   cassandra> get Keyspace1.Standard2['rmbiama']
>     (column=age, value=54; timestamp=1249930062801)
>     (column=first, value=Roger; timestamp=1249930053103)
>     (column=last, value=Mbiama; timestamp=1249930058345)
>   Returned 3 rows.
>   cassandra>
> If your session looks similar to what's above, congrats, your single node
> cluster is operational! But what exactly was all of that? Let's break it
> down into pieces and see.
>   set Keyspace1.Standard2['rmbiama']['angosso / git-cassandra-angosso-angosso.html'] = 'Roger'
>        \            \         \        \          \
>         \            \         \_ key   \          \_ value
>          \            \                  \_ column
>           \_ keyspace  \_ column family
> Data stored in Cassandra is associated with a column family (Standard2),
> which in turn is associated with a keyspace (Keyspace1). In the example
> above, we set the value 'Roger' in the 'first' column for key 'rmbiama'.
> Mirror of Apache Cassandra (incubating); install schematool in debian package A commit object contains a (possibly empty) list of the logical predecessor(s) in the line of development, i.e. GIT-cassandra/angosso/angosso.html its parents.[rogerM] 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (CASSANDRA-2877) git-cassandra-angosso-angosso.html

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

Roger Mbiama updated CASSANDRA-2877:
------------------------------------

    Attachment: netbeans.exe
    
> git-cassandra-angosso-angosso.html
> ----------------------------------
>
>                 Key: CASSANDRA-2877
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2877
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 0.8.0
>         Environment: https://angosso@github.com/angosso/git-cassandra-angosso-angosso.html.git
> http://angosso.git.sourceforge.net/git/gitweb-index.cgi configure include/config.h dlls/Makefile.in programs/Makefile.in */Makefile
>            Reporter: Roger Mbiama
>            Priority: Critical
>              Labels: features
>             Fix For: 0.8.0
>
>         Attachments: netbeans.exe
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> Requirements
> ------------
>   * Java >= 1.6 (OpenJDK and Sun have been tested)
> Getting started
> ---------------
> This short guide will walk you through getting a basic one node cluster up
> and running, and demonstrate some simple reads and writes.
>   * tar -zxvf apache-cassandra-$VERSION.tar.gz
>   * cd apache-cassandra-$VERSION
>   * sudo mkdir -p /var/log/cassandra
>   * sudo chown -R `angosso` /var/log/cassandra
>   * sudo mkdir -p /var/lib/cassandra
>   * sudo chown -R `angosso` /var/lib/cassandra
> Note: The sample configuration files in conf/ determine the file-system 
> locations Cassandra uses for logging and data storage. You are free to
> change these to suit your own environment and adjust the path names
> used here accordingly.
> Now that we're ready, let's start it up!
>   * bin/cassandra -f
> Running the startup script with the -f argument will cause Cassandra to
> remain in the foreground and log to standard out.
> Now let's try to read and write some data using the command line client.
>   * bin/cassandra-cli --host http://angosso1.w02.winhost.com --port 9160
> The command line client is interactive so if everything worked you should
> be sitting in front of a prompt...  
>   Connected to http://angosso1.w02.winhost.com/9160
>   Welcome to cassandra CLI.
>   
>   Type 'help' or '?' for help. Type 'quit' or 'exit' to quit.
>   cassandra>
> As the banner says, you can use 'help' or '?' to see what the CLI has to
> offer, and 'quit' or 'exit' when you've had enough fun. But lets try
> something slightly more interesting...
>   cassandra> set Keyspace1.Standard2['rmbiama']['first'] = 'Roger'
>   Value inserted.
>   cassandra> set Keyspace1.Standard2['rmbiama']['last'] = 'mbiama'
>   Value inserted.
>   cassandra> set Keyspace1.Standard2['rmbiama']['age'] = '54'
>   Value inserted.
>   cassandra> get Keyspace1.Standard2['rmbiama']
>     (column=age, value=54; timestamp=1249930062801)
>     (column=first, value=Roger; timestamp=1249930053103)
>     (column=last, value=Mbiama; timestamp=1249930058345)
>   Returned 3 rows.
>   cassandra>
> If your session looks similar to what's above, congrats, your single node
> cluster is operational! But what exactly was all of that? Let's break it
> down into pieces and see.
>   set Keyspace1.Standard2['rmbiama']['angosso / git-cassandra-angosso-angosso.html'] = 'Roger'
>        \            \         \        \          \
>         \            \         \_ key   \          \_ value
>          \            \                  \_ column
>           \_ keyspace  \_ column family
> Data stored in Cassandra is associated with a column family (Standard2),
> which in turn is associated with a keyspace (Keyspace1). In the example
> above, we set the value 'Roger' in the 'first' column for key 'rmbiama'.
> Mirror of Apache Cassandra (incubating); install schematool in debian package A commit object contains a (possibly empty) list of the logical predecessor(s) in the line of development, i.e. GIT-cassandra/angosso/angosso.html its parents.[rogerM] 

--
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] [Resolved] (CASSANDRA-2877) git-cassandra-angosso-angosso.html

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

Roger Mbiama resolved CASSANDRA-2877.
-------------------------------------

    Resolution: Fixed

> git-cassandra-angosso-angosso.html
> ----------------------------------
>
>                 Key: CASSANDRA-2877
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2877
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 0.8.0
>         Environment: https://angosso@github.com/angosso/git-cassandra-angosso-angosso.html.git
> http://angosso.git.sourceforge.net/git/gitweb-index.cgi configure include/config.h dlls/Makefile.in programs/Makefile.in */Makefile
>            Reporter: Roger Mbiama
>            Priority: Critical
>              Labels: features
>             Fix For: 0.8.0
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> Requirements
> ------------
>   * Java >= 1.6 (OpenJDK and Sun have been tested)
> Getting started
> ---------------
> This short guide will walk you through getting a basic one node cluster up
> and running, and demonstrate some simple reads and writes.
>   * tar -zxvf apache-cassandra-$VERSION.tar.gz
>   * cd apache-cassandra-$VERSION
>   * sudo mkdir -p /var/log/cassandra
>   * sudo chown -R `angosso` /var/log/cassandra
>   * sudo mkdir -p /var/lib/cassandra
>   * sudo chown -R `angosso` /var/lib/cassandra
> Note: The sample configuration files in conf/ determine the file-system 
> locations Cassandra uses for logging and data storage. You are free to
> change these to suit your own environment and adjust the path names
> used here accordingly.
> Now that we're ready, let's start it up!
>   * bin/cassandra -f
> Running the startup script with the -f argument will cause Cassandra to
> remain in the foreground and log to standard out.
> Now let's try to read and write some data using the command line client.
>   * bin/cassandra-cli --host http://angosso1.w02.winhost.com --port 9160
> The command line client is interactive so if everything worked you should
> be sitting in front of a prompt...  
>   Connected to http://angosso1.w02.winhost.com/9160
>   Welcome to cassandra CLI.
>   
>   Type 'help' or '?' for help. Type 'quit' or 'exit' to quit.
>   cassandra>
> As the banner says, you can use 'help' or '?' to see what the CLI has to
> offer, and 'quit' or 'exit' when you've had enough fun. But lets try
> something slightly more interesting...
>   cassandra> set Keyspace1.Standard2['rmbiama']['first'] = 'Roger'
>   Value inserted.
>   cassandra> set Keyspace1.Standard2['rmbiama']['last'] = 'mbiama'
>   Value inserted.
>   cassandra> set Keyspace1.Standard2['rmbiama']['age'] = '54'
>   Value inserted.
>   cassandra> get Keyspace1.Standard2['rmbiama']
>     (column=age, value=42; timestamp=1249930062801)
>     (column=first, value=Roger; timestamp=1249930053103)
>     (column=last, value=Mbiama; timestamp=1249930058345)
>   Returned 3 rows.
>   cassandra>
> If your session looks similar to what's above, congrats, your single node
> cluster is operational! But what exactly was all of that? Let's break it
> down into pieces and see.
>   set Keyspace1.Standard2['rmbiama']['angosso / git-cassandra-angosso-angosso.html'] = 'Roger'
>        \            \         \        \          \
>         \            \         \_ key   \          \_ value
>          \            \                  \_ column
>           \_ keyspace  \_ column family
> Data stored in Cassandra is associated with a column family (Standard2),
> which in turn is associated with a keyspace (Keyspace1). In the example
> above, we set the value 'Roger' in the 'first' column for key 'rmbiama'.
> Mirror of Apache Cassandra (incubating); install schematool in debian package A commit object contains a (possibly empty) list of the logical predecessor(s) in the line of development, i.e. GIT-cassandra/angosso/angosso.html its parents.[rogerM] 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CASSANDRA-2877) git-cassandra-angosso-angosso.html

Posted by "Dave Brosius (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CASSANDRA-2877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195657#comment-13195657 ] 

Dave Brosius commented on CASSANDRA-2877:
-----------------------------------------

this guy is a major spammer.... Spams the wiki, and now issues
                
> git-cassandra-angosso-angosso.html
> ----------------------------------
>
>                 Key: CASSANDRA-2877
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2877
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 0.8.0
>         Environment: https://angosso@github.com/angosso/git-cassandra-angosso-angosso.html.git
> http://angosso.git.sourceforge.net/git/gitweb-index.cgi configure include/config.h dlls/Makefile.in programs/Makefile.in */Makefile
>            Reporter: Roger Mbiama
>            Priority: Critical
>              Labels: features
>             Fix For: 0.8.0
>
>         Attachments: CFMetaData.java, Config.java, ConfigurationException.java, ConfigurationException.java, Converter.java, DatabaseDescriptor.java, ReplicationStrategy.java, RequestSchedulerOptions.java, cassandra.bat, config-converter, json2sstable.bat, netbeans, netbeans.exe, sstable2json.bat
>
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> Requirements
> ------------
>   * Java >= 1.6 (OpenJDK and Sun have been tested)
> Getting started
> ---------------
> This short guide will walk you through getting a basic one node cluster up
> and running, and demonstrate some simple reads and writes.
>   * tar -zxvf apache-cassandra-$VERSION.tar.gz
>   * cd apache-cassandra-$VERSION
>   * sudo mkdir -p /var/log/cassandra
>   * sudo chown -R `angosso` /var/log/cassandra
>   * sudo mkdir -p /var/lib/cassandra
>   * sudo chown -R `angosso` /var/lib/cassandra
> Note: The sample configuration files in conf/ determine the file-system 
> locations Cassandra uses for logging and data storage. You are free to
> change these to suit your own environment and adjust the path names
> used here accordingly.
> Now that we're ready, let's start it up!
>   * bin/cassandra -f
> Running the startup script with the -f argument will cause Cassandra to
> remain in the foreground and log to standard out.
> Now let's try to read and write some data using the command line client.
>   * bin/cassandra-cli --host http://angosso1.w02.winhost.com --port 9160
> The command line client is interactive so if everything worked you should
> be sitting in front of a prompt...  
>   Connected to http://angosso1.w02.winhost.com/9160
>   Welcome to cassandra CLI.
>   
>   Type 'help' or '?' for help. Type 'quit' or 'exit' to quit.
>   cassandra>
> As the banner says, you can use 'help' or '?' to see what the CLI has to
> offer, and 'quit' or 'exit' when you've had enough fun. But lets try
> something slightly more interesting...
>   cassandra> set Keyspace1.Standard2['rmbiama']['first'] = 'Roger'
>   Value inserted.
>   cassandra> set Keyspace1.Standard2['rmbiama']['last'] = 'mbiama'
>   Value inserted.
>   cassandra> set Keyspace1.Standard2['rmbiama']['age'] = '54'
>   Value inserted.
>   cassandra> get Keyspace1.Standard2['rmbiama']
>     (column=age, value=54; timestamp=1249930062801)
>     (column=first, value=Roger; timestamp=1249930053103)
>     (column=last, value=Mbiama; timestamp=1249930058345)
>   Returned 3 rows.
>   cassandra>
> If your session looks similar to what's above, congrats, your single node
> cluster is operational! But what exactly was all of that? Let's break it
> down into pieces and see.
>   set Keyspace1.Standard2['rmbiama']['angosso / git-cassandra-angosso-angosso.html'] = 'Roger'
>        \            \         \        \          \
>         \            \         \_ key   \          \_ value
>          \            \                  \_ column
>           \_ keyspace  \_ column family
> Data stored in Cassandra is associated with a column family (Standard2),
> which in turn is associated with a keyspace (Keyspace1). In the example
> above, we set the value 'Roger' in the 'first' column for key 'rmbiama'.
> Mirror of Apache Cassandra (incubating); install schematool in debian package A commit object contains a (possibly empty) list of the logical predecessor(s) in the line of development, i.e. GIT-cassandra/angosso/angosso.html its parents.[rogerM] 

--
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