BigTable

I am trying to connect to Titan 1.0.0 with Hadoop 2 (HBase 1.0.2 client) (available in https://github.com/thinkaurelius/titan/wiki/Downloads ) with Google Cloud Bigtable service, using its HBase client. I could successfully connect to Bigtable from an HBase shell in a GCE instance, by following this procedure . The hbase-site.xml is according to the template, and I have downloaded Bigtable jars for ALPN_VERSION=8.1.5.v20150921 (Oracle JDK SE 1.8.0_60) <configuration> <property> <name>hbase.client.connection.impl</name> <value>com.google.cloud.bigtable.hbase1_0.BigtableConnection</value> <

How do you put on a big table of xtable the table header on each page?, So that is easier to read the table the table between pages. I use the following in Sweave: test.big<- xtable(test,label="table",caption='test') align(test.big) <- "|c|c|c|c|l|c|c|c|" print(test.big,tabular.environment='longtable',include.colnames = TRUE,floating=FALSE) Thanks for your answers The longtable (LaTeX) package specification can be found at that URL. The section of code in the examples whose output appears on pages 2 and 3 is in section 8 and I have reproduced bit of it below: \caption[]{(continued)}\\ \hline

I'm building an index of data, which will entail storing lots of triplets in the form (document, term, weight) . I will be storing up to a few million such rows. Currently I'm doing this in MySQL as a simple table. I'm storing the document and term identifiers as string values than foreign keys to other tables. I'm re-writing the software and looking for better ways of storing the data. Looking at the way HBase works, this seems to fit the schema rather well. Instead of storing lots of triplets, I could map document to {term => weight} . I'm doing this on a single node , so I don't care about

Let's say I have a booking database consisting of users : user_id fname lname and their tickets ticket_id user_id flight_no and associated flights flight_no airline departure_time arrival_time What would I need to change to move this Google AppEngine? I understand AppEngine doesn't allow joins . Does that mean my table should become one big schmudge of fields all lumped together? bookings : user_id fname lname ticket_id flight_no airline departure_time arrival_time In other words, all of my queries now run against the same table? What changes you need depends mostly on what queries you need to

I'm still learning my lessons about data modeling in bigtable/nosql and would appreciate some feedback. Would it be fair to say that I should avoid parent->child relationships in my data modeling if I frequently need to deal with the children in aggregate across parents? As an example, let's say I'm building a blog that will be contributed to by a number of authors, and each other has posts, and each post has tags. So I could potentially set up something like this: class Author(db.Model): owner = db.UserProperty() class Post(db.Model): owner = db.ReferenceProperty(Author, collection_name=