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

Sync upstream #5

Closed
wants to merge 1,182 commits into from
Closed

Conversation

amitgilad3
Copy link

@amitgilad3 amitgilad3 commented Feb 12, 2025

Hey @zinking - i rebased from upstream to make sure the pr can be merged,

Fokko and others added 30 commits December 11, 2024 13:45
* Hive: Optimize tableExists API in hive catalog

Skip creation of hive table operation when check existence of iceberg table in hive catalog

* Add a newline after if/else

* Add current thread interrupt

* Handle metadata tables and separate the tests

* Add comment back

* Address feedback

* Add extra  comment for EcsCatalog override method

* Move javadoc  around

* Added note if hive table with same name exists

* Added note if hive table with same name exists

* Add test with invalid identifier
Co-authored-by: Bharath Kumar Avusherla <bavusherla@expediagroup.com>
Bumps `nessie` from 0.101.0 to 0.101.2.

Updates `org.projectnessie.nessie:nessie-client` from 0.101.0 to 0.101.2

Updates `org.projectnessie.nessie:nessie-jaxrs-testextension` from 0.101.0 to 0.101.2

Updates `org.projectnessie.nessie:nessie-versioned-storage-inmemory-tests` from 0.101.0 to 0.101.2

Updates `org.projectnessie.nessie:nessie-versioned-storage-testextension` from 0.101.0 to 0.101.2

---
updated-dependencies:
- dependency-name: org.projectnessie.nessie:nessie-client
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.projectnessie.nessie:nessie-jaxrs-testextension
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.projectnessie.nessie:nessie-versioned-storage-inmemory-tests
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: org.projectnessie.nessie:nessie-versioned-storage-testextension
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…e#11793)

Bumps software.amazon.awssdk:bom from 2.29.29 to 2.29.34.

---
updated-dependencies:
- dependency-name: software.amazon.awssdk:bom
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [mkdocs-material](https://github.com/squidfunk/mkdocs-material) from 9.5.47 to 9.5.48.
- [Release notes](https://github.com/squidfunk/mkdocs-material/releases)
- [Changelog](https://github.com/squidfunk/mkdocs-material/blob/master/CHANGELOG)
- [Commits](squidfunk/mkdocs-material@9.5.47...9.5.48)

---
updated-dependencies:
- dependency-name: mkdocs-material
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* REST: Use apache/iceberg-rest-fixture docker image

* Fix CI failure
* Auth Manager API part 1: HTTPRequest, HTTPHeader

* review

* remove static methods

* verify error messages

* checkstyle

* review

* review

* review
@amitgilad3
Copy link
Author

Hey @zinking - seems like the tests pass , can we please merge it so we can get a pass on our rewrite target branch pr :)

@zinking
Copy link
Owner

zinking commented Feb 13, 2025

seems it is still conflicted. I guess you don't really work on this branch. feel free to start your branch and just reference those commits. @amitgilad3

@amitgilad3
Copy link
Author

I didnt see any conflicts, is there any chance you can give me permissions to this repo so i can finish the work? Or the you prefer i just create a new pr?

@amitgilad3 amitgilad3 closed this by deleting the head repository Feb 13, 2025
@zinking
Copy link
Owner

zinking commented Feb 13, 2025

just create your own PR is fine. @amitgilad3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment