-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Index V2 consumption #4462
Index V2 consumption #4462
Changes from all commits
de58c99
a6e1566
db8d933
7160b50
b3e5387
e2e370a
94cea95
67d7c62
25eba2f
5d8c384
259f113
fa7533c
d13e68c
07daa84
f8466ab
8c66bf2
7c8ea4d
0e0ca0b
3e74a07
bcde1ab
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -345,3 +345,20 @@ You can enable the feature as shown below. | |
"configureExport": true | ||
}, | ||
``` | ||
|
||
### indexV2 | ||
|
||
This feature enables the `winget` source to retrieve the V2 index, which is significantly smaller. | ||
Regardless of the state of this feature, if the index on the machine contains a V2 index, it will be used. | ||
If there is a bug with the V2 index stopping the `winget` CLI from working, disable the feature in your settings file and run this command: | ||
``` | ||
> winget uninstall -s msstore Microsoft.Winget.Source_8wekyb3d8bbwe | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nit: "-s msstore", is this listed in store source? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No, that was an intentional "if the winget source is broken, lets avoid using it" flag. Commands targeting the local data don't really need a source, but we don't have a way to use a null one. |
||
``` | ||
|
||
You can enable the feature as shown below. | ||
|
||
```json | ||
"experimentalFeatures": { | ||
"indexV2": true | ||
}, | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to clarify - If the V2 index is outdated, and a newer V1 index is available, will the V1 index be used?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Editing for more complete answer]
If the feature is enabled, the V2 index will always be preferred if it exists.
If the feature is disabled, a newer V1 index will replace the V2 index when it becomes available.