Because some user has had problems configuring these services could be helpful to make some examples or videos about how to properly setup Optimus in this services.

It would be great if there was an option to preserve the original order of variables in plot_histogram(). Currently, variables within each page of the output seem to be ordered alphabetically but the pages themselves follow the original order.

Adding a description for the parameters will help the users understand how to specify values for each parameter. For example, the format of the longitude in Yelp.businesses table; the maximum limit of the results that a user can expect (if we incorporate limit parameter in the future).

For large datasets where computing the summary may be expensive, it would be useful to compute only part of it, be able to explore it, and then compute other parts of it without recomputing the initial report.

The selection of which parts to compute could be by:

• columns in the dataset,
• metrics, or
• row ranges.

This can be useful to get an overview of string structure of a columns
def patterns(self, input_cols, output_cols=None, mode=0):

See https://github.com/ironmussa/Optimus/blob/develop-3.0/optimus/engines/base/columns.py#L153 For more info about the param

Need someone to go through the documentation we do have and determine what is missing and what is needed; develop a roadmap to help organize efforts.

The original model of querying, doc by doc, whether doc ID exists to then insert/update the corresponding doc does not scale