How does authentication work in this scheme? The view uses separate S3 credentials, which are configured per external user consuming the database?

Via the AWS extension

https://duckdb.org/docs/guides/network_cloud_storage/s3_impo... https://duckdb.org/docs/extensions/aws

Would love the community's thoughts on this take on pre-processing unstructured and multimodal data for LLM apps. The thesis is that the classical ETL pattern will come back to the fore in the case of multimodal data, given the steps to make such data valuable for AI app development.

Please let me know your thoughts and please let me know of any questions about Datavolo, powered by Apache NiFi!

You'd probably be interested in the research of Hugo Mercier and Dan Sperber on this very point: http://www.nytimes.com/2011/06/15/arts/people-argue-just-to-... People Argue Just to Win, Scholars Assert - The New York Times

Are there any plans for Warehouses support for IBM's DashDB?

Hey slachterman DashDB isn't yet on the roadmap, mind filling this out so we can follow up?

https://segment.com/contact/requests/warehouse

Impala supports LAG and LEAD, etc.: http://www.cloudera.com/documentation/archive/impala/2-x/2-0...

So do most databased, but they are SLOOOOOOOW.

I don't think that's correct per https://letsencrypt.org/certificates/

Our intermediate is signed by ISRG Root X1. However, since we are a very new certificate authority, ISRG Root X1 is not yet trusted in most browsers. In order to be broadly trusted right away, our intermediate is also cross-signed by another certificate authority, IdenTrust, whose root is already trusted in all major browsers. Specifically, IdenTrust has cross-signed our intermediate using their DST Root CA X3.