See Table 2 in the original paper found here

The corresponding website can be found here

In our API docs we currently use

.. autosummary::
   Client
   Client.call_stack
   Client.cancel
    ...

To generate a table of Client methods at the top of the page. Later on we use

.. autoclass:: Client
   :members:

to display the docstrings for all the public methods on Client (here an example for

Problem description

When I use the function of concatenating multiple columns, I find that it does not handle null values as expected.

This is the current output

df.concatenate_columns(["cat_1","cat_2","cat_3"],"cat",sep=",")

Problem description

Our dask update graphs are not properly optimized.

We ussually use dask.dataframe optimization and set ave_width=repartition_ratio for kartothek.io.dask.dataframe.update_dataset_from_ddf graphs. We should return an optimized graph from update_dataset_from_ddf to make our users' life simple.

We already have code that does this, whoever picks this up can ping me

In trying to write tests for #189, I'm finding very difficult to add columns to existing tests, as in some cases like the all_types table, the table is defined in a separate file than the tests and multiple tests try to write to the same table.

Additionally, our test suite doesn't prove that the data that are uploaded are the same as the data downloaded for all types.

We should consider m

The assert_array_shape call is used a lot in REGENIE, and serves both as a runtime check and as documentation for the reader. We should sprinkle it liberally through other functions.