fix: Disable prefetch on list by default

[efirs]

No description provided.

[Copilot]

Pull Request Overview

This PR changes the behavior of the Tigris prefetch functionality by disabling it by default. It updates the CLI flag name from a negative ("no-tigris-prefetch") to a positive ("tigris-prefetch") flag and adjusts the associated logic in both flag population and default flag settings.

[tvogel]

I am interested in the background of this. Would it make sense for me to use --no-tigris-prefetch with the release 1.2.1 when I am primarily interested in ctime and size (for determining incremental backup scope)? Are there other optimizations, I should look at?

[ovaistariq]

Prefetch is disabled by default now. You don't have to pass the --no-tigris-prefetch flag.

[tvogel]

I don't think, this applies to the latest tagged release, see https://github.com/tigrisdata/tigrisfs/blob/v1.2.1/core/cfg/flags.go#L1141 .

What was the reason to disable it by default (in this PR)?

[ovaistariq]

You are right.

It was disabled by default because users with large datasets found the prefetching of files on listing unexpected. So we want to let the users choose this behavior.