data-engineering

For a sqllab query that returns a large number of columns (I observed this in a query with ~70 columns), the sorting functionality is broken. Columns do not sort at all.

I'm not sure how easy this is to fix. Do we want to consider this a limitation of sqllab or is this fixable?

Expected results

Columns have the ability to sort

Actual results

When you click on the column head

Opened from the Prefect Public Slack Community

elliot: Hey folks is anyone else getting a deprecation warning on marshmallow? Something like:

...
/home/rof/.pyenv/versions/3.9.1/lib/python3.9/site-packages/marshmallow/fields.py:198
/home/rof/.pyenv/versions/3.9.1/lib/python3.9/site-packages/marshmallow/fields.py:198: RemovedInMarshmallow4Warning: Passing fi

Describe the bug
data docs columns shrink to 1 character width with long query

To Reproduce
Steps to reproduce the behavior:

1. make a batch from a long query string
2. run validation
3. render result to data docs
4. See screenshot
   <img width="1525" alt="Data_documentation_compiled_by_Great_Expectations" src="https://user-images.githubusercontent.com/928247/103230647-30eca500-4

Refer users to the documentation from the webui. For example, the Create-Repo dialog can link to the quickstart-create-repo doc page. Inspiration taken from Airbyte; while choosing the postgres Source:

if they are not class methods then the method would be invoked for every test and a session would be created for each of those tests.

`class PySparkTest(unittest.TestCase):
@classmethod
def suppress_py4j_logging(cls):
logger = logging.getLogger('py4j')
logger.setLevel(logging.WARN)

@classmethod
def create_testing_pyspark_session(cls):
    return Sp

Hi ,

I am using some basic functions from pyjanitor such as - clean_names() , collapse_levels() in one of my code which I want to productionise.
And there are limitations on the size of the production code base.
Currently ,if I just look at the requirements.txt for just "pyjanitor" , its huge .
I don't think I require all the dependencies in my code.
How can I remove the unnecessary ones ?

In the repository handler

• removeEntity tries to delete then if delete is not supported issues a purge, the purge method issues an audit log
• There are 2 callers to purgeRelationship only one of which audit logs

This is inconsistent.
I suggest we move the relationship audit log to the purge method, which means that both callers will audit log.

We have a new cookbook section: https://github.com/ploomber/projects/tree/master/cookbook

where we add minimal examples for certain use cases, we should add links to each one on the relevant sections in the docs