Google Git
Sign in
android / platform / frameworks / support / a68321a7eb6f3db2f926484499d5b9b6867248f2
commita68321a7eb6f3db2f926484499d5b9b6867248f2[log] [tgz]
authorTim Barron <[email protected]>Mon Dec 30 17:02:36 2024 +0000
committerTim Barron <[email protected]>Tue Jan 14 05:56:34 2025 +0000
treea31a64323d4440dbd57df06d87b12e3cdfb8a335
parent8e19671af43788c7449d072c977779ab6dd369cf [diff]
Add SearchContext#setPersistToDiskRecoveryProof.

This option on LocalStorage.SearchContext will allow callers to change
the AppSearch instance to call PersistToDisk RECOVERY_PROOF rather than
PersistToDisk LITE.

RECOVERY_PROOF is a more expensive operation, but guarantees that
recovery will not be needed on the next initialization. LITE, by
contrast, only guarantees no data loss. A recovery will be needed unless
the caller calls AppSearchSession#requestFlush or
AppSearchSession#close.

In the long-term, AppSearch plans on always using RECOVERY_PROOF.
However, we want to keep this behavior opt-in until sufficient soaking
has proven it's stability and performance. At that time, this new method
will be deprecated and then deleted.

Bug: 352556856
Test: AppSearchImplTest

Change-Id: I7169b3935224f262bd08982330a9a25ad682b210
10 files changed
tree: a31a64323d4440dbd57df06d87b12e3cdfb8a335
  1. .github/
  2. .idea/
  3. activity/
  4. annotation/
  5. appcompat/
  6. appfunctions/
  7. appintegration/
  8. appsearch/
  9. arch/
  10. asynclayoutinflater/
  11. autofill/
  12. benchmark/
  13. binarycompatibilityvalidator/
  14. biometric/
  15. bluetooth/
  16. browser/
  17. buildSrc/
  18. buildSrc-tests/
  19. busytown/
  20. camera/
  21. car/
  22. cardview/
  23. collection/
  24. compose/
  25. concurrent/
  26. constraintlayout/
  27. contentpager/
  28. coordinatorlayout/
  29. core/
  30. credentials/
  31. cursoradapter/
  32. customview/
  33. datastore/
  34. development/
  35. docs/
  36. docs-public/
  37. docs-tip-of-tree/
  38. documentfile/
  39. draganddrop/
  40. drawerlayout/
  41. dynamicanimation/
  42. emoji/
  43. emoji2/
  44. enterprise/
  45. exifinterface/
  46. external/
  47. fragment/
  48. glance/
  49. gradle/
  50. graphics/
  51. gridlayout/
  52. health/
  53. heifwriter/
  54. hilt/
  55. ink/
  56. input/
  57. inspection/
  58. interpolator/
  59. javascriptengine/
  60. kruth/
  61. leanback/
  62. lifecycle/
  63. lint/
  64. lint-checks/
  65. loader/
  66. media/
  67. mediarouter/
  68. metrics/
  69. navigation/
  70. navigation3/
  71. paging/
  72. palette/
  73. pdf/
  74. percentlayout/
  75. performance/
  76. placeholder/
  77. placeholder-tests/
  78. playground-common/
  79. playground-projects/
  80. preference/
  81. print/
  82. privacysandbox/
  83. profileinstaller/
  84. recommendation/
  85. recyclerview/
  86. remotecallback/
  87. resourceinspection/
  88. room/
  89. safeparcel/
  90. samples/
  91. savedstate/
  92. security/
  93. sharetarget/
  94. slidingpanelayout/
  95. sqlite/
  96. stableaidl/
  97. startup/
  98. swiperefreshlayout/
  99. test/
  100. testutils/
  101. tracing/
  102. transition/
  103. tv/
  104. tvprovider/
  105. vectordrawable/
  106. versionedparcelable/
  107. viewpager/
  108. viewpager2/
  109. wear/
  110. webkit/
  111. window/
  112. work/
  113. xr/
  114. .gitignore
  115. build.gradle
  116. cleanBuild.sh
  117. code-review.md
  118. CONTRIBUTING.md
  119. gradle.properties
  120. gradlew
  121. libraryversions.toml
  122. license-baseline.txt
  123. LICENSE.txt
  124. OWNERS
  125. PREUPLOAD.cfg
  126. README.md
  127. settings.gradle
  128. studiow
  129. TEXT_OWNERS
README.md

Android Jetpack

Revved up by Develocity

Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.

Jetpack comprises the androidx.* package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.

Our official AARs and JARs binaries are distributed through Google Maven.

You can learn more about using it from Android Jetpack landing page.

Contribution Guide

For contributions via GitHub, see the GitHub Contribution Guide.

Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:

Code Review Etiquette

When contributing to Jetpack, follow the code review etiquette.

Accepted Types of Contributions

  • Bug fixes - needs a corresponding bug report in the Android Issue Tracker
  • Each bug fix is expected to come with tests
  • Fixing spelling errors
  • Updating documentation
  • Adding new tests to the area that is not currently covered by tests
  • New features to existing libraries if the feature request bug has been approved by an AndroidX team member.

We are not currently accepting new modules.

Checking Out the Code

Head over to the onboarding docs to learn more about getting set up and the development workflow!

Continuous integration

Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.

Password and Contributor Agreement before making a change

Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:

Generate a HTTPS password: https://android-review.googlesource.com/new-password

Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement

Getting reviewed

  • After you run repo upload, open r.android.com
  • Sign in into your account (or create one if you do not have one yet)
  • Add an appropriate reviewer (use git log to find who did most modifications on the file you are fixing or check the OWNERS file in the project's directory)

Handling binary dependencies

AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal and prebuilts/androidx/external directories in your checkout. All the dependencies in these directories are also available from google(), or mavenCentral(). We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.