READY: RTS-667 / RTS-796

[lukebakken]

• Add DESCRIBE tests
• Add method to encapsulate retrieving table description
• Add tests to ensure CREATE TABLE works correctly via query method

[lukebakken]

This is a new feature that I don't necessarily have to include. It eliminates the redundancy of specifying the table name as the first parameter to ts_query() as well as within the query string. However, if the query string is itself a format string, the user must remember to escape the parameter via {{table}} as you can see in the tests.

[hazen]

test_query_that_matches_more_data (riak.tests.test_timeseries.TimeseriesTests) ... ERROR
test_query_that_matches_some_data (riak.tests.test_timeseries.TimeseriesTests) ... ERROR
test_query_that_matches_some_data_using_interpolation (riak.tests.test_timeseries.TimeseriesTests) ... ERROR

Looks like these were failing with TS 1.0 and the Python 2.3.0 client, too

[lukebakken]

@javajolt - really? I'll give that a try. I know they worked at one point with a 1.0 RC.

[hazen]

So is this interpolation because of the random table names?

[lukebakken]

No, because I have {table} in the query string, but do not use fmt to replace it before passing to ts_query. Within the code for queries, it will check for {table} and, if present, insert the table name.

Note that ts_query takes a table parameter than can be a Table object or a string. Either can provide the name of the table so it is convenient to replace the table name for the user.

See my comment here:

https://github.com/basho/riak-python-client/pull/422/files#r48791174

[lukebakken]

@javajolt TS tests pass this morning with RC7

[hazen]

👍 6f169a7

[hazen]

@borshop merge