http://www.datastax.com/support-forums/topic/inserting-records-in-column-family-with-hive-uses-incorrect-timestamp Software, Support, and Training for Apache Cassandra en-US Fri, 24 May 2013 19:03:54 +0000 http://bbpress.org/?v=1.0.3 q http://www.datastax.com/support-forums/search.php http://www.datastax.com/support-forums/topic/inserting-records-in-column-family-with-hive-uses-incorrect-timestamp#post-1700 Wed, 18 Apr 2012 21:50:26 +0000 Anonymous 1700@http://www.datastax.com/support-forums/ <p>Thanks Joaquin,</p> <p>Had another crack at this with my specific db and script. Tested to make sure hive was picking up the correct unix_timestamp(). That was OK. Ran my script and found it was updating with the correct timestamp!!! Records that were not updated still showed the incorrect timestamp of 1970-01-16. </p> <p>I'm not sure what was happening here, but I don't think it was hive, something odd with my system! Please consider this closed.</p> <p>Thanks for your help.<br /> regards Ross. </p> http://www.datastax.com/support-forums/topic/inserting-records-in-column-family-with-hive-uses-incorrect-timestamp#post-1692 Wed, 18 Apr 2012 18:21:53 +0000 joaquin 1692@http://www.datastax.com/support-forums/ <p>Hello,</p> <p>The script seems to have a lower precision than what is currently used by the cassandra-cli. The rest of the PortfolioDemo scripts do take this into account however.</p> <p>If you were trying to change the values, try doing this with CQL which would allow to you set and/or change timestamps.</p> <p>The cassandra-cli is typically seen and used as a basic monitoring/testing tool and unfortunately does not support custom timestamps.</p> <p>Do let us know if you have any further questions.</p> <p>Thanks,<br /> Joaquin </p> http://www.datastax.com/support-forums/topic/inserting-records-in-column-family-with-hive-uses-incorrect-timestamp#post-1615 Fri, 13 Apr 2012 03:28:49 +0000 Anonymous 1615@http://www.datastax.com/support-forums/ <p>Test case using PortfolioDemo.<br /> The script 10_day_loss.q was run populating HistLoss.<br /> cassandra-cli was then run with the following commands:</p> <p>[default@unknown] connect localhost/9160;<br /> connect localhost/9160;<br /> Connected to: "Test Cluster" on localhost/9160<br /> [default@unknown] use PortfolioDemo;<br /> use PortfolioDemo;<br /> Authenticated to keyspace: PortfolioDemo<br /> [default@PortfolioDemo] set HistLoss['100']['test']='test';<br /> set HistLoss['100']['test']='test';<br /> Value inserted.<br /> Elapsed time: 23 msec(s).<br /> [default@PortfolioDemo] get HistLoss[utf8('100')]<br /> get HistLoss[utf8('100')];<br /> =&gt; (column=loss, value=-1492.8402867337113, timestamp=1334287269078)<br /> =&gt; (column=test, value=test, timestamp=1334287414757000)<br /> =&gt; (column=worst_date, value=2012-02-07, timestamp=1334287269078)<br /> Returned 3 results.<br /> Elapsed time: 14 msec(s).</p> <p>The timestamps for loss and worst_date are 1970-01-16 20:38:07.269<br /> The time stamp for test is 2012-04-13 13:23:34.757</p> <p>Is there some setting required for Hive to insert the correct timestamps? </p>