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

fix: Rename database from 'couchbasedb' to 'couchbase' in documentation and db_engine_specs #29911

Merged
merged 9 commits into from
Aug 13, 2024
Merged

Conversation

ayush-couchbase
Copy link
Contributor

SUMMARY

Changing Name from couchbasedb to couchbase. Makes it more clear and logical about underlying database.
No major change done.

TESTING INSTRUCTIONS

mannual testing

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

@github-actions github-actions bot added the doc Namespace | Anything related to documentation label Aug 10, 2024
@dosubot dosubot bot added the data:connect Namespace | Anything related to db connections / integrations label Aug 10, 2024
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

Congrats on making your first PR and thank you for contributing to Superset! 🎉 ❤️

We hope to see you in our Slack community too! Not signed up? Use our Slack App to self-register.

@ayush-couchbase ayush-couchbase changed the title Rename database from 'couchbasedb' to 'couchbase' in documentation and db_engine_specs fix:Rename database from 'couchbasedb' to 'couchbase' in documentation and db_engine_specs Aug 10, 2024
@ayush-couchbase ayush-couchbase changed the title fix:Rename database from 'couchbasedb' to 'couchbase' in documentation and db_engine_specs fix: Rename database from 'couchbasedb' to 'couchbase' in documentation and db_engine_specs Aug 10, 2024
Copy link

codecov bot commented Aug 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.70%. Comparing base (76d897e) to head (3d6682a).
Report is 1094 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #29911       +/-   ##
===========================================
+ Coverage   60.48%   83.70%   +23.21%     
===========================================
  Files        1931      527     -1404     
  Lines       76236    38055    -38181     
  Branches     8568        0     -8568     
===========================================
- Hits        46114    31853    -14261     
+ Misses      28017     6202    -21815     
+ Partials     2105        0     -2105     
Flag Coverage Δ
hive 49.02% <100.00%> (-0.15%) ⬇️
javascript ?
mysql 76.76% <100.00%> (?)
postgres 76.85% <100.00%> (?)
presto 53.56% <100.00%> (-0.24%) ⬇️
python 83.70% <100.00%> (+20.21%) ⬆️
sqlite 76.34% <100.00%> (?)
unit 60.36% <100.00%> (+2.73%) ⬆️

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@villebro villebro left a comment

Choose a reason for hiding this comment

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

There are some issues reported by CI. In addition, the breaking change is problematic, and would need to at least be addressed in UPDATING.md and/or by adding an alias to the old name.

@@ -102,7 +102,7 @@
"clickhouse": Dialects.CLICKHOUSE,
"clickhousedb": Dialects.CLICKHOUSE,
"cockroachdb": Dialects.POSTGRES,
"couchbasedb": Dialects.MYSQL,
"couchbase": Dialects.MYSQL,
Copy link
Member

Choose a reason for hiding this comment

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

This would entail a breaking change, and would break every Couchbase connection created by existing users. At minimum we would need to create an alias for the old dialect name to ensure old connections still work.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have corrected this in new patch. I am adding alias to old name also. I am seeing all checks passed too.

Copy link
Member

Choose a reason for hiding this comment

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

I am adding alias to old name also.

I don't see the alias here - can you check how the alias is implemented in the Postgres spec?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

My mistake I thought alias means updating sql_parse , I saw oceanbase and postgres db_engine_specs and similar to that I have added engine_aliases = {"couchbase", "couchbasedb"} to db_engine_spec/couchbase.py .

Copy link
Member

@villebro villebro left a comment

Choose a reason for hiding this comment

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

Second pass comment

Copy link
Member

@villebro villebro left a comment

Choose a reason for hiding this comment

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

One last nit, after that this LGTM 👍

engine = "couchbasedb"
class CouchbaseEngineSpec(BasicParametersMixin, BaseEngineSpec):
engine = "couchbase"
engine_aliases = {"couchbase", "couchbasedb"}
Copy link
Member

Choose a reason for hiding this comment

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

You donät need the main name in the alias set, this should be enough:

Suggested change
engine_aliases = {"couchbase", "couchbasedb"}
engine_aliases = {"couchbasedb"}

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There are 2 failed checks, but they were not failing earlier, are they because of my patch ?

Copy link
Member

Choose a reason for hiding this comment

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

The failed MySQL test is flaky - we can restart the test. The docs one seems unrelated - It seems resources/INTHEWILD.md has a link to /www.cnovit.com that isn't working. I think we may need to remove the link if the homepage isn't up anymore. Do you want to do it in this PR? I can also open a PR to fix it if needed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I can fix in this PR. I will upload a new patch.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed

@michael-s-molina michael-s-molina added risk:breaking-change Issues or PRs that will introduce breaking changes review:checkpoint Last PR reviewed during the daily review standup labels Aug 12, 2024
@villebro
Copy link
Member

@michael-s-molina this will not be a breaking change as per the last changes. So I think it's safe to remove that label.

@michael-s-molina michael-s-molina removed the risk:breaking-change Issues or PRs that will introduce breaking changes label Aug 12, 2024
@@ -80,7 +80,6 @@ Join our growing community!
- [Caizin](https://caizin.com/) [@tejaskatariya]
- [Careem](https://www.careem.com/) [@SamraHanifCareem]
- [Cloudsmith](https://cloudsmith.io) [@alancarson]
- [CnOvit](http://www.cnovit.com/) [@xieshaohu]
Copy link
Member

Choose a reason for hiding this comment

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

Is this removal intentional? Maybe you meant to add Couchbase?

Copy link
Contributor Author

@ayush-couchbase ayush-couchbase Aug 12, 2024

Choose a reason for hiding this comment

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

This link is not working. So tests were failing. @villebro is discussing about it in previous conversation. So I removed it

Copy link
Member

Choose a reason for hiding this comment

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

@ayush-couchbase it seems the link was failing due to being http and not https - could you update that? The https one works for me at least. After that I think we're good to go.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure , Updated in new patch

Copy link
Member

Choose a reason for hiding this comment

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

FYI, the link checker does not block merging... it just gives us little to-do items as maintainers. I'll open a PR today to sweep up whatever's left at the moment.

Copy link
Member

@villebro villebro left a comment

Choose a reason for hiding this comment

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

LGTM, thanks for all the patience and iterations!

@villebro villebro merged commit f5d614d into apache:master Aug 13, 2024
39 checks passed
@michael-s-molina michael-s-molina removed the review:checkpoint Last PR reviewed during the daily review standup label Aug 13, 2024
@rusackas rusackas added the v4.1 Label added by the release manager to track PRs to be included in the 4.1 branch label Oct 18, 2024
@rusackas
Copy link
Member

FYI @sadpandajoe the author would like to get this into the next release opportunity. I tagged it as 4.1 in case there's an RC4, but let me know if there's anything else I should do to get it into 4.1.1 if RC3 passes the vote.

sadpandajoe pushed a commit that referenced this pull request Nov 13, 2024
…on and db_engine_specs (#29911)

(cherry picked from commit f5d614d)
@mistercrunch mistercrunch added 🍒 4.1.1 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels labels Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels data:connect Namespace | Anything related to db connections / integrations doc Namespace | Anything related to documentation size/M v4.1 Label added by the release manager to track PRs to be included in the 4.1 branch 🍒 4.1.1
Projects
No open projects
Status: Cherried
Development

Successfully merging this pull request may close these issues.

5 participants