CREATE EXTERNAL TABLE without OPTIONS

[osopardo1]

Description

Fixes #246

Type of change

Allows the creation of an already physically formatted Qbeast Table without the need to specify the options columnsToIndex or cubeSize. In case the table is external, exists, and has Qbeast Metadata, it loads the required parameters from the QbeastSnapshot.

Let's see an example:

val df = Seq(1, 2, 3).toDF("id")
df.write.format("qbeast").option("columnsToIndex", "id").save("/tmp/qbeast_table")

spark.sql("CREATE EXTERNAL TABLE t USING qbeast LOCATION '/tmp/qbeast_table'")

Checklist:

Here is the list of things you should do before submitting this pull request:

• New feature / bug fix has been committed following the Contribution guide.
• Add comments to the code (make it easier for the community!).
• Change the documentation.
• Add tests.
• Your branch is updated to the main branch (dependent changes have been merged).

How Has This Been Tested? (Optional)

It is tested in QbeastSQLIntegrationTest.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (18b4534) 91.76% compared to head (61a7468) 91.78%.
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #248      +/-   ##
==========================================
+ Coverage   91.76%   91.78%   +0.02%     
==========================================
  Files          91       91              
  Lines        2258     2264       +6     
  Branches      167      172       +5     
==========================================
+ Hits         2072     2078       +6     
  Misses        186      186              

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

[osopardo1]

Adding some tests I've found a weird behavior when passing Options/Paramaters/Properties back and forth.

For example, if a Table already exists with Options A and B, the user can:

• Not specify options, and A and B should be considered.
• Specify options, and A and B should be verified and overriden if necessary.

In the second case, options A and B weren't passed to the save methods, and subsequently not overridden.

Fixing them!!