Ivan Longin

@skshetry It was user-focused API but I would say it's just deprecated recently in favor of the new `Datachain`

How will we overcome the issue that was solved in that https://github.com/iterative/dvcx/pull/1068 you mentioned if we are not going to copy query to temp table?

Looks like this was explicitly not supported for some reason, as can be seen in error message

Yes, the only solution is to flatten the top level column. As I spoke with Dmitry, this is not that high priority so removing myself form assignment. Added quick better...

I think this should be prioritized as it's sometimes hard to refactor / change codebase as this old indexing part needs to be adopted. It would been much easier if...

> Can we introduce something like `strict` mode in schema, similar to `pydantic` to support non-nullable types? > > https://docs.pydantic.dev/latest/concepts/strict_mode/ The thing here is actually this is not null vs...

> @ilongin what is the status of this? @shcheklein It's ready for merge but I know we needed some more discussions / clarification in one of our meetings so I...

Maybe this can be calculated right in the listing process itself if it is guaranteed that we always get all versions of a file in the same "batch" when traversing...

@dmpetrov should we rename functions to `switch_storage` instead of `switch_bucket` since it should also work for local files and we usually use `storage` terminology for this?

@dmpetrov can you explain why do we need to reset (and later update) all those `File` columns like `is_latest`, `version`, `size`, `last_modified` and `etag`? ... Won't those stay the same...