Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated intro message #75

Merged
merged 2 commits into from
Sep 29, 2023
Merged

Updated intro message #75

merged 2 commits into from
Sep 29, 2023

Conversation

edurdevic
Copy link
Contributor

No description provided.

@codecov
Copy link

codecov bot commented Sep 27, 2023

Codecov Report

Merging #75 (b47ca5e) into master (2cf4b18) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #75   +/-   ##
=======================================
  Coverage   92.51%   92.51%           
=======================================
  Files           9        9           
  Lines         681      681           
  Branches      110      110           
=======================================
  Hits          630      630           
  Misses         29       29           
  Partials       22       22           
Flag Coverage Δ
unittests 92.51% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
discoverx/dx.py 90.90% <ø> (ø)

@@ -61,10 +61,18 @@ def intro(self):
<h1>Hi there, I'm DiscoverX.</h1>

<p>
I'm here to help you discover data in your lakehouse.<br />
You can scan your lakehouse by using
I'm here to help you paralelize multi-table operations across your lakehouse.<br />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: should be parallelize I think ...

<ul>
<li><code>.apply_sql(...)</code> - Runs a SQL template on each table</li>
<li><code>.scan(...)</code> - Scan your lakehouse for columns matching the given rules</li>
<li><code>.search(...)</code> - Search your lakehouse for columns matching the given search term</li>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking a bit about the .search and if we should keep it here because this won't reflect the "new" api. But I guess it is fine and it will work the same way in the future when we plan to use tags. What do you think?

@edurdevic edurdevic merged commit bbfe878 into master Sep 29, 2023
4 checks passed
@edurdevic edurdevic deleted the docs-info-update branch September 29, 2023 10:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants