Russell Spitzer

Make a jira https://datastax-oss.atlassian.net/projects/SPARKC/ For tracking (this is how we catch everything up in release notes and track versioning)

It looks to me like the information about ClusteringOrders is in two places within the TableDef. 1) Available as an indexedSequence `clusteringOrder: Option[Seq[ClusteringOrder]] = None,` 2) Available within the clusteringColumn...

This would need to be fixed in the property itself, since the reference.md file is automatically generated from the property's class

Sorry this will need a rebase now that I've merged in the Java driver 4.0 update, but I will check this and get it in as soon as the branch...

Can you write a little bit of the use case for this api? I took a brief look today (sorry so busy) and I think it's a very cool Idea...

I'm wondering if we might be better off with just another api, like a generic "RunPreparedStatements" Which would be something like `RDD[BoundParameters].runPreparedStatements[ReturnType]("CQL HERE with ? PARAMETERS ?")` Of which then...

I think we should pause on this and instead focus on making completely flexible function. Like I described above, that way we don't increase the complexity of the code as...

I think we could add some implicits in Iceberg's Scala Modules outside of Spark as well. That might be a good path forward

@lordk911 the issue here is that the "HiveCatalog" you are creating in the code does not have information required for Spark to actually locate the table. Instead get the table...

> Also just wondering, there's no way to strip the catalog before loading the table in the Spark3BinPackStrategy and have it work, right? Yeah unfortunately the way we have it...