You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

ConfigConstants.java 12KB

DFS: A storage layer for JGit In practice the DHT storage layer has not been performing as well as large scale server environments want to see from a Git server. The performance of the DHT schema degrades rapidly as small changes are pushed into the repository due to the chunk size being less than 1/3 of the pushed pack size. Small chunks cause poor prefetch performance during reading, and require significantly longer prefetch lists inside of the chunk meta field to work around the small size. The DHT code is very complex (>17,000 lines of code) and is very sensitive to the underlying database round-trip time, as well as the way objects were written into the pack stream that was chunked and stored on the database. A poor pack layout (from any version of C Git prior to Junio reworking it) can cause the DHT code to be unable to enumerate the objects of the linux-2.6 repository in a completable time scale. Performing a clone from a DHT stored repository of 2 million objects takes 2 million row lookups in the DHT to locate the OBJECT_INDEX row for each object being cloned. This is very difficult for some DHTs to scale, even at 5000 rows/second the lookup stage alone takes 6 minutes (on local filesystem, this is almost too fast to bother measuring). Some servers like Apache Cassandra just fall over and cannot complete the 2 million lookups in rapid fire. On a ~400 MiB repository, the DHT schema has an extra 25 MiB of redundant data that gets downloaded to the JGit process, and that is before you consider the cost of the OBJECT_INDEX table also being fully loaded, which is at least 223 MiB of data for the linux kernel repository. In the DHT schema answering a `git clone` of the ~400 MiB linux kernel needs to load 248 MiB of "index" data from the DHT, in addition to the ~400 MiB of pack data that gets sent to the client. This is 193 MiB more data to be accessed than the native filesystem format, but it needs to come over a much smaller pipe (local Ethernet typically) than the local SATA disk drive. I also never got around to writing the "repack" support for the DHT schema, as it turns out to be fairly complex to safely repack data in the repository while also trying to minimize the amount of changes made to the database, due to very common limitations on database mutation rates.. This new DFS storage layer fixes a lot of those issues by taking the simple approach for storing relatively standard Git pack and index files on an abstract filesystem. Packs are accessed by an in-process buffer cache, similar to the WindowCache used by the local filesystem storage layer. Unlike the local file IO, there are some assumptions that the storage system has relatively high latency and no concept of "file handles". Instead it looks at the file more like HTTP byte range requests, where a read channel is a simply a thunk to trigger a read request over the network. The DFS code in this change is still abstract, it does not store on any particular filesystem, but is fairly well suited to the Amazon S3 or Apache Hadoop HDFS. Storing packs directly on HDFS rather than HBase removes a layer of abstraction, as most HBase row reads turn into an HDFS read. Most of the DFS code in this change was blatently copied from the local filesystem code. Most parts should be refactored to be shared between the two storage systems, but right now I am hesistent to do this due to how well tuned the local filesystem code currently is. Change-Id: Iec524abdf172e9ec5485d6c88ca6512cd8a6eafb
13 years ago
DFS: A storage layer for JGit In practice the DHT storage layer has not been performing as well as large scale server environments want to see from a Git server. The performance of the DHT schema degrades rapidly as small changes are pushed into the repository due to the chunk size being less than 1/3 of the pushed pack size. Small chunks cause poor prefetch performance during reading, and require significantly longer prefetch lists inside of the chunk meta field to work around the small size. The DHT code is very complex (>17,000 lines of code) and is very sensitive to the underlying database round-trip time, as well as the way objects were written into the pack stream that was chunked and stored on the database. A poor pack layout (from any version of C Git prior to Junio reworking it) can cause the DHT code to be unable to enumerate the objects of the linux-2.6 repository in a completable time scale. Performing a clone from a DHT stored repository of 2 million objects takes 2 million row lookups in the DHT to locate the OBJECT_INDEX row for each object being cloned. This is very difficult for some DHTs to scale, even at 5000 rows/second the lookup stage alone takes 6 minutes (on local filesystem, this is almost too fast to bother measuring). Some servers like Apache Cassandra just fall over and cannot complete the 2 million lookups in rapid fire. On a ~400 MiB repository, the DHT schema has an extra 25 MiB of redundant data that gets downloaded to the JGit process, and that is before you consider the cost of the OBJECT_INDEX table also being fully loaded, which is at least 223 MiB of data for the linux kernel repository. In the DHT schema answering a `git clone` of the ~400 MiB linux kernel needs to load 248 MiB of "index" data from the DHT, in addition to the ~400 MiB of pack data that gets sent to the client. This is 193 MiB more data to be accessed than the native filesystem format, but it needs to come over a much smaller pipe (local Ethernet typically) than the local SATA disk drive. I also never got around to writing the "repack" support for the DHT schema, as it turns out to be fairly complex to safely repack data in the repository while also trying to minimize the amount of changes made to the database, due to very common limitations on database mutation rates.. This new DFS storage layer fixes a lot of those issues by taking the simple approach for storing relatively standard Git pack and index files on an abstract filesystem. Packs are accessed by an in-process buffer cache, similar to the WindowCache used by the local filesystem storage layer. Unlike the local file IO, there are some assumptions that the storage system has relatively high latency and no concept of "file handles". Instead it looks at the file more like HTTP byte range requests, where a read channel is a simply a thunk to trigger a read request over the network. The DFS code in this change is still abstract, it does not store on any particular filesystem, but is fairly well suited to the Amazon S3 or Apache Hadoop HDFS. Storing packs directly on HDFS rather than HBase removes a layer of abstraction, as most HBase row reads turn into an HDFS read. Most of the DFS code in this change was blatently copied from the local filesystem code. Most parts should be refactored to be shared between the two storage systems, but right now I am hesistent to do this due to how well tuned the local filesystem code currently is. Change-Id: Iec524abdf172e9ec5485d6c88ca6512cd8a6eafb
13 years ago
DFS: A storage layer for JGit In practice the DHT storage layer has not been performing as well as large scale server environments want to see from a Git server. The performance of the DHT schema degrades rapidly as small changes are pushed into the repository due to the chunk size being less than 1/3 of the pushed pack size. Small chunks cause poor prefetch performance during reading, and require significantly longer prefetch lists inside of the chunk meta field to work around the small size. The DHT code is very complex (>17,000 lines of code) and is very sensitive to the underlying database round-trip time, as well as the way objects were written into the pack stream that was chunked and stored on the database. A poor pack layout (from any version of C Git prior to Junio reworking it) can cause the DHT code to be unable to enumerate the objects of the linux-2.6 repository in a completable time scale. Performing a clone from a DHT stored repository of 2 million objects takes 2 million row lookups in the DHT to locate the OBJECT_INDEX row for each object being cloned. This is very difficult for some DHTs to scale, even at 5000 rows/second the lookup stage alone takes 6 minutes (on local filesystem, this is almost too fast to bother measuring). Some servers like Apache Cassandra just fall over and cannot complete the 2 million lookups in rapid fire. On a ~400 MiB repository, the DHT schema has an extra 25 MiB of redundant data that gets downloaded to the JGit process, and that is before you consider the cost of the OBJECT_INDEX table also being fully loaded, which is at least 223 MiB of data for the linux kernel repository. In the DHT schema answering a `git clone` of the ~400 MiB linux kernel needs to load 248 MiB of "index" data from the DHT, in addition to the ~400 MiB of pack data that gets sent to the client. This is 193 MiB more data to be accessed than the native filesystem format, but it needs to come over a much smaller pipe (local Ethernet typically) than the local SATA disk drive. I also never got around to writing the "repack" support for the DHT schema, as it turns out to be fairly complex to safely repack data in the repository while also trying to minimize the amount of changes made to the database, due to very common limitations on database mutation rates.. This new DFS storage layer fixes a lot of those issues by taking the simple approach for storing relatively standard Git pack and index files on an abstract filesystem. Packs are accessed by an in-process buffer cache, similar to the WindowCache used by the local filesystem storage layer. Unlike the local file IO, there are some assumptions that the storage system has relatively high latency and no concept of "file handles". Instead it looks at the file more like HTTP byte range requests, where a read channel is a simply a thunk to trigger a read request over the network. The DFS code in this change is still abstract, it does not store on any particular filesystem, but is fairly well suited to the Amazon S3 or Apache Hadoop HDFS. Storing packs directly on HDFS rather than HBase removes a layer of abstraction, as most HBase row reads turn into an HDFS read. Most of the DFS code in this change was blatently copied from the local filesystem code. Most parts should be refactored to be shared between the two storage systems, but right now I am hesistent to do this due to how well tuned the local filesystem code currently is. Change-Id: Iec524abdf172e9ec5485d6c88ca6512cd8a6eafb
13 years ago
DFS: A storage layer for JGit In practice the DHT storage layer has not been performing as well as large scale server environments want to see from a Git server. The performance of the DHT schema degrades rapidly as small changes are pushed into the repository due to the chunk size being less than 1/3 of the pushed pack size. Small chunks cause poor prefetch performance during reading, and require significantly longer prefetch lists inside of the chunk meta field to work around the small size. The DHT code is very complex (>17,000 lines of code) and is very sensitive to the underlying database round-trip time, as well as the way objects were written into the pack stream that was chunked and stored on the database. A poor pack layout (from any version of C Git prior to Junio reworking it) can cause the DHT code to be unable to enumerate the objects of the linux-2.6 repository in a completable time scale. Performing a clone from a DHT stored repository of 2 million objects takes 2 million row lookups in the DHT to locate the OBJECT_INDEX row for each object being cloned. This is very difficult for some DHTs to scale, even at 5000 rows/second the lookup stage alone takes 6 minutes (on local filesystem, this is almost too fast to bother measuring). Some servers like Apache Cassandra just fall over and cannot complete the 2 million lookups in rapid fire. On a ~400 MiB repository, the DHT schema has an extra 25 MiB of redundant data that gets downloaded to the JGit process, and that is before you consider the cost of the OBJECT_INDEX table also being fully loaded, which is at least 223 MiB of data for the linux kernel repository. In the DHT schema answering a `git clone` of the ~400 MiB linux kernel needs to load 248 MiB of "index" data from the DHT, in addition to the ~400 MiB of pack data that gets sent to the client. This is 193 MiB more data to be accessed than the native filesystem format, but it needs to come over a much smaller pipe (local Ethernet typically) than the local SATA disk drive. I also never got around to writing the "repack" support for the DHT schema, as it turns out to be fairly complex to safely repack data in the repository while also trying to minimize the amount of changes made to the database, due to very common limitations on database mutation rates.. This new DFS storage layer fixes a lot of those issues by taking the simple approach for storing relatively standard Git pack and index files on an abstract filesystem. Packs are accessed by an in-process buffer cache, similar to the WindowCache used by the local filesystem storage layer. Unlike the local file IO, there are some assumptions that the storage system has relatively high latency and no concept of "file handles". Instead it looks at the file more like HTTP byte range requests, where a read channel is a simply a thunk to trigger a read request over the network. The DFS code in this change is still abstract, it does not store on any particular filesystem, but is fairly well suited to the Amazon S3 or Apache Hadoop HDFS. Storing packs directly on HDFS rather than HBase removes a layer of abstraction, as most HBase row reads turn into an HDFS read. Most of the DFS code in this change was blatently copied from the local filesystem code. Most parts should be refactored to be shared between the two storage systems, but right now I am hesistent to do this due to how well tuned the local filesystem code currently is. Change-Id: Iec524abdf172e9ec5485d6c88ca6512cd8a6eafb
13 years ago
Persist filesystem timestamp resolution and allow manual configuration To enable persisting filesystem timestamp resolution per FileStore add a new config section to the user global git configuration: - Config section is "filesystem" - Config subsection is concatenation of - Java vendor (system property "java.vm.vendor") - runtime version (system property "java.vm.version") - FileStore's name - separated by '|' e.g. "AdoptOpenJDK|1.8.0_212-b03|/dev/disk1s1" The prefix is needed since some Java versions do not expose the full timestamp resolution of the underlying filesystem. This may also depend on the underlying operating system hence concrete key values may not be portable. - Config key for timestamp resolution is "timestampResolution" as a time value, supported time units are those supported by DefaultTypedConfigGetter#getTimeUnit If timestamp resolution is already configured for a given FileStore the configured value is used instead of measuring the resolution. When timestamp resolution was measured it is persisted in the user global git configuration. Example: [filesystem "AdoptOpenJDK|1.8.0_212-b03|/dev/disk1s1"] timestampResolution = 1 seconds If locking the git config file fails retry saving the resolution up to 5 times in order to workaround races with another thread. In order to avoid stack overflow use the fallback filesystem timestamp resolution when loading FileBasedConfig which creates itself a FileSnapshot to help checking if the config changed. Note: - on some OSes Java 8,9 truncate to milliseconds or seconds, see https://bugs.openjdk.java.net/browse/JDK-8177809, fixed in Java 10 - UnixFileAttributes up to Java 12 truncates timestamp resolution to microseconds when converting the internal representation to FileTime exposed in the API, see https://bugs.openjdk.java.net/browse/JDK-8181493 - WindowsFileAttributes also provides only microsecond resolution up to Java 12 Hence do not attempt to manually configure a higher timestamp resolution than supported by the Java version being used at runtime. Bug: 546891 Bug: 548188 Change-Id: Iff91b8f9e6e5e2295e1463f87c8e95edf4abbcf8 Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>
5 years ago
Persist minimal racy threshold and allow manual configuration To enable persisting the minimal racy threshold per FileStore add a new config option to the user global git configuration: - Config section is "filesystem" - Config subsection is concatenation of - Java vendor (system property "java.vendor") - Java version (system property "java.version") - FileStore's name, on Windows we use the attribute volume:vsn instead since the name is not necessarily unique. - separated by '|' e.g. "AdoptOpenJDK|1.8.0_212-b03|/dev/disk1s1" The same prefix is used as for filesystem timestamp resolution, so both values are stored in the same config section - The config key for minmal racy threshold is "minRacyThreshold" as a time value, supported time units are those supported by DefaultTypedConfigGetter#getTimeUnit - measure for 3 seconds to limit runtime which depends on hardware, OS and Java version being used If the minimal racy threshold is configured for a given FileStore the configured value is used instead of measuring it. When the minimal racy threshold was measured it is persisted in the user global git configuration. Rename FileStoreAttributeCache to FileStoreAttributes since this class is now declared public in order to enable exposing all attributes in one object. Example: [filesystem "AdoptOpenJDK|11.0.3|/dev/disk1s1"] timestampResolution = 7000 nanoseconds minRacyThreshold = 3440 microseconds Change-Id: I22195e488453aae8d011b0a8e3276fe3d99deaea Signed-off-by: Matthias Sohn <matthias.sohn@sap.com> Also-By: Marc Strapetz <marc.strapetz@syntevo.com>
4 years ago
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454
  1. /*
  2. * Copyright (C) 2010, Mathias Kinzler <mathias.kinzler@sap.com>
  3. * Copyright (C) 2010, Chris Aniszczyk <caniszczyk@gmail.com>
  4. * Copyright (C) 2012-2013, Robin Rosenberg
  5. * and other copyright owners as documented in the project's IP log.
  6. *
  7. * This program and the accompanying materials are made available
  8. * under the terms of the Eclipse Distribution License v1.0 which
  9. * accompanies this distribution, is reproduced below, and is
  10. * available at http://www.eclipse.org/org/documents/edl-v10.php
  11. *
  12. * All rights reserved.
  13. *
  14. * Redistribution and use in source and binary forms, with or
  15. * without modification, are permitted provided that the following
  16. * conditions are met:
  17. *
  18. * - Redistributions of source code must retain the above copyright
  19. * notice, this list of conditions and the following disclaimer.
  20. *
  21. * - Redistributions in binary form must reproduce the above
  22. * copyright notice, this list of conditions and the following
  23. * disclaimer in the documentation and/or other materials provided
  24. * with the distribution.
  25. *
  26. * - Neither the name of the Eclipse Foundation, Inc. nor the
  27. * names of its contributors may be used to endorse or promote
  28. * products derived from this software without specific prior
  29. * written permission.
  30. *
  31. * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
  32. * CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
  33. * INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
  34. * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
  35. * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR
  36. * CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
  37. * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
  38. * NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
  39. * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
  40. * CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
  41. * STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
  42. * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
  43. * ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  44. */
  45. package org.eclipse.jgit.lib;
  46. /**
  47. * Constants for use with the Configuration classes: section names,
  48. * configuration keys
  49. */
  50. @SuppressWarnings("nls")
  51. public final class ConfigConstants {
  52. /** The "core" section */
  53. public static final String CONFIG_CORE_SECTION = "core";
  54. /** The "branch" section */
  55. public static final String CONFIG_BRANCH_SECTION = "branch";
  56. /** The "remote" section */
  57. public static final String CONFIG_REMOTE_SECTION = "remote";
  58. /** The "diff" section */
  59. public static final String CONFIG_DIFF_SECTION = "diff";
  60. /** The "dfs" section */
  61. public static final String CONFIG_DFS_SECTION = "dfs";
  62. /**
  63. * The "receive" section
  64. * @since 4.6
  65. */
  66. public static final String CONFIG_RECEIVE_SECTION = "receive";
  67. /** The "user" section */
  68. public static final String CONFIG_USER_SECTION = "user";
  69. /** The "gerrit" section */
  70. public static final String CONFIG_GERRIT_SECTION = "gerrit";
  71. /** The "workflow" section */
  72. public static final String CONFIG_WORKFLOW_SECTION = "workflow";
  73. /** The "submodule" section */
  74. public static final String CONFIG_SUBMODULE_SECTION = "submodule";
  75. /**
  76. * The "rebase" section
  77. * @since 3.2
  78. */
  79. public static final String CONFIG_REBASE_SECTION = "rebase";
  80. /** The "gc" section */
  81. public static final String CONFIG_GC_SECTION = "gc";
  82. /** The "pack" section */
  83. public static final String CONFIG_PACK_SECTION = "pack";
  84. /**
  85. * The "fetch" section
  86. * @since 3.3
  87. */
  88. public static final String CONFIG_FETCH_SECTION = "fetch";
  89. /**
  90. * The "pull" section
  91. * @since 3.5
  92. */
  93. public static final String CONFIG_PULL_SECTION = "pull";
  94. /**
  95. * The "merge" section
  96. * @since 4.9
  97. */
  98. public static final String CONFIG_MERGE_SECTION = "merge";
  99. /**
  100. * The "filter" section
  101. * @since 4.6
  102. */
  103. public static final String CONFIG_FILTER_SECTION = "filter";
  104. /** The "algorithm" key */
  105. public static final String CONFIG_KEY_ALGORITHM = "algorithm";
  106. /** The "autocrlf" key */
  107. public static final String CONFIG_KEY_AUTOCRLF = "autocrlf";
  108. /**
  109. * The "auto" key
  110. * @since 4.6
  111. */
  112. public static final String CONFIG_KEY_AUTO = "auto";
  113. /**
  114. * The "autogc" key
  115. * @since 4.6
  116. */
  117. public static final String CONFIG_KEY_AUTOGC = "autogc";
  118. /**
  119. * The "autopacklimit" key
  120. * @since 4.6
  121. */
  122. public static final String CONFIG_KEY_AUTOPACKLIMIT = "autopacklimit";
  123. /**
  124. * The "eol" key
  125. *
  126. * @since 4.3
  127. */
  128. public static final String CONFIG_KEY_EOL = "eol";
  129. /** The "bare" key */
  130. public static final String CONFIG_KEY_BARE = "bare";
  131. /** The "excludesfile" key */
  132. public static final String CONFIG_KEY_EXCLUDESFILE = "excludesfile";
  133. /**
  134. * The "attributesfile" key
  135. *
  136. * @since 3.7
  137. */
  138. public static final String CONFIG_KEY_ATTRIBUTESFILE = "attributesfile";
  139. /** The "filemode" key */
  140. public static final String CONFIG_KEY_FILEMODE = "filemode";
  141. /** The "logallrefupdates" key */
  142. public static final String CONFIG_KEY_LOGALLREFUPDATES = "logallrefupdates";
  143. /** The "repositoryformatversion" key */
  144. public static final String CONFIG_KEY_REPO_FORMAT_VERSION = "repositoryformatversion";
  145. /** The "worktree" key */
  146. public static final String CONFIG_KEY_WORKTREE = "worktree";
  147. /** The "blockLimit" key */
  148. public static final String CONFIG_KEY_BLOCK_LIMIT = "blockLimit";
  149. /** The "blockSize" key */
  150. public static final String CONFIG_KEY_BLOCK_SIZE = "blockSize";
  151. /**
  152. * The "concurrencyLevel" key
  153. *
  154. * @since 4.6
  155. */
  156. public static final String CONFIG_KEY_CONCURRENCY_LEVEL = "concurrencyLevel";
  157. /** The "deltaBaseCacheLimit" key */
  158. public static final String CONFIG_KEY_DELTA_BASE_CACHE_LIMIT = "deltaBaseCacheLimit";
  159. /**
  160. * The "symlinks" key
  161. * @since 3.3
  162. */
  163. public static final String CONFIG_KEY_SYMLINKS = "symlinks";
  164. /** The "streamFileThreshold" key */
  165. public static final String CONFIG_KEY_STREAM_FILE_TRESHOLD = "streamFileThreshold";
  166. /** The "remote" key */
  167. public static final String CONFIG_KEY_REMOTE = "remote";
  168. /** The "merge" key */
  169. public static final String CONFIG_KEY_MERGE = "merge";
  170. /** The "rebase" key */
  171. public static final String CONFIG_KEY_REBASE = "rebase";
  172. /** The "url" key */
  173. public static final String CONFIG_KEY_URL = "url";
  174. /** The "autosetupmerge" key */
  175. public static final String CONFIG_KEY_AUTOSETUPMERGE = "autosetupmerge";
  176. /** The "autosetuprebase" key */
  177. public static final String CONFIG_KEY_AUTOSETUPREBASE = "autosetuprebase";
  178. /**
  179. * The "autostash" key
  180. * @since 3.2
  181. */
  182. public static final String CONFIG_KEY_AUTOSTASH = "autostash";
  183. /** The "name" key */
  184. public static final String CONFIG_KEY_NAME = "name";
  185. /** The "email" key */
  186. public static final String CONFIG_KEY_EMAIL = "email";
  187. /** The "false" key (used to configure {@link #CONFIG_KEY_AUTOSETUPMERGE} */
  188. public static final String CONFIG_KEY_FALSE = "false";
  189. /** The "true" key (used to configure {@link #CONFIG_KEY_AUTOSETUPMERGE} */
  190. public static final String CONFIG_KEY_TRUE = "true";
  191. /**
  192. * The "always" key (used to configure {@link #CONFIG_KEY_AUTOSETUPREBASE}
  193. * and {@link #CONFIG_KEY_AUTOSETUPMERGE}
  194. */
  195. public static final String CONFIG_KEY_ALWAYS = "always";
  196. /** The "never" key (used to configure {@link #CONFIG_KEY_AUTOSETUPREBASE} */
  197. public static final String CONFIG_KEY_NEVER = "never";
  198. /** The "local" key (used to configure {@link #CONFIG_KEY_AUTOSETUPREBASE} */
  199. public static final String CONFIG_KEY_LOCAL = "local";
  200. /** The "createchangeid" key */
  201. public static final String CONFIG_KEY_CREATECHANGEID = "createchangeid";
  202. /** The "defaultsourceref" key */
  203. public static final String CONFIG_KEY_DEFBRANCHSTARTPOINT = "defbranchstartpoint";
  204. /** The "path" key */
  205. public static final String CONFIG_KEY_PATH = "path";
  206. /** The "update" key */
  207. public static final String CONFIG_KEY_UPDATE = "update";
  208. /**
  209. * The "ignore" key
  210. * @since 3.6
  211. */
  212. public static final String CONFIG_KEY_IGNORE = "ignore";
  213. /** The "compression" key */
  214. public static final String CONFIG_KEY_COMPRESSION = "compression";
  215. /** The "indexversion" key */
  216. public static final String CONFIG_KEY_INDEXVERSION = "indexversion";
  217. /**
  218. * The "hidedotfiles" key
  219. * @since 3.5
  220. */
  221. public static final String CONFIG_KEY_HIDEDOTFILES = "hidedotfiles";
  222. /**
  223. * The "dirnogitlinks" key
  224. * @since 4.3
  225. */
  226. public static final String CONFIG_KEY_DIRNOGITLINKS = "dirNoGitLinks";
  227. /** The "precomposeunicode" key */
  228. public static final String CONFIG_KEY_PRECOMPOSEUNICODE = "precomposeunicode";
  229. /** The "pruneexpire" key */
  230. public static final String CONFIG_KEY_PRUNEEXPIRE = "pruneexpire";
  231. /**
  232. * The "prunepackexpire" key
  233. * @since 4.3
  234. */
  235. public static final String CONFIG_KEY_PRUNEPACKEXPIRE = "prunepackexpire";
  236. /**
  237. * The "logexpiry" key
  238. *
  239. * @since 4.7
  240. */
  241. public static final String CONFIG_KEY_LOGEXPIRY = "logExpiry";
  242. /**
  243. * The "autodetach" key
  244. *
  245. * @since 4.7
  246. */
  247. public static final String CONFIG_KEY_AUTODETACH = "autoDetach";
  248. /**
  249. * The "aggressiveDepth" key
  250. * @since 3.6
  251. */
  252. public static final String CONFIG_KEY_AGGRESSIVE_DEPTH = "aggressiveDepth";
  253. /**
  254. * The "aggressiveWindow" key
  255. * @since 3.6
  256. */
  257. public static final String CONFIG_KEY_AGGRESSIVE_WINDOW = "aggressiveWindow";
  258. /** The "mergeoptions" key */
  259. public static final String CONFIG_KEY_MERGEOPTIONS = "mergeoptions";
  260. /** The "ff" key */
  261. public static final String CONFIG_KEY_FF = "ff";
  262. /**
  263. * The "checkstat" key
  264. * @since 3.0
  265. */
  266. public static final String CONFIG_KEY_CHECKSTAT = "checkstat";
  267. /**
  268. * The "renamelimit" key in the "diff section"
  269. * @since 3.0
  270. */
  271. public static final String CONFIG_KEY_RENAMELIMIT = "renamelimit";
  272. /**
  273. * The "trustfolderstat" key in the "core section"
  274. * @since 3.6
  275. */
  276. public static final String CONFIG_KEY_TRUSTFOLDERSTAT = "trustfolderstat";
  277. /**
  278. * The "supportsAtomicFileCreation" key in the "core section"
  279. *
  280. * @since 4.5
  281. */
  282. public static final String CONFIG_KEY_SUPPORTSATOMICFILECREATION = "supportsatomicfilecreation";
  283. /**
  284. * The "noprefix" key in the "diff section"
  285. * @since 3.0
  286. */
  287. public static final String CONFIG_KEY_NOPREFIX = "noprefix";
  288. /**
  289. * A "renamelimit" value in the "diff section"
  290. * @since 3.0
  291. */
  292. public static final String CONFIG_RENAMELIMIT_COPY = "copy";
  293. /**
  294. * A "renamelimit" value in the "diff section"
  295. * @since 3.0
  296. */
  297. public static final String CONFIG_RENAMELIMIT_COPIES = "copies";
  298. /**
  299. * The "renames" key in the "diff section"
  300. * @since 3.0
  301. */
  302. public static final String CONFIG_KEY_RENAMES = "renames";
  303. /**
  304. * The "inCoreLimit" key in the "merge section". It's a size limit (bytes) used to
  305. * control a file to be stored in {@code Heap} or {@code LocalFile} during the merge.
  306. * @since 4.9
  307. */
  308. public static final String CONFIG_KEY_IN_CORE_LIMIT = "inCoreLimit";
  309. /**
  310. * The "prune" key
  311. * @since 3.3
  312. */
  313. public static final String CONFIG_KEY_PRUNE = "prune";
  314. /**
  315. * The "streamBuffer" key
  316. * @since 4.0
  317. */
  318. public static final String CONFIG_KEY_STREAM_BUFFER = "streamBuffer";
  319. /**
  320. * The "streamRatio" key
  321. * @since 4.0
  322. */
  323. public static final String CONFIG_KEY_STREAM_RATIO = "streamRatio";
  324. /**
  325. * Flag in the filter section whether to use JGit's implementations of
  326. * filters and hooks
  327. * @since 4.6
  328. */
  329. public static final String CONFIG_KEY_USEJGITBUILTIN = "useJGitBuiltin";
  330. /**
  331. * The "fetchRecurseSubmodules" key
  332. * @since 4.7
  333. */
  334. public static final String CONFIG_KEY_FETCH_RECURSE_SUBMODULES = "fetchRecurseSubmodules";
  335. /**
  336. * The "recurseSubmodules" key
  337. * @since 4.7
  338. */
  339. public static final String CONFIG_KEY_RECURSE_SUBMODULES = "recurseSubmodules";
  340. /**
  341. * The "required" key
  342. * @since 4.11
  343. */
  344. public static final String CONFIG_KEY_REQUIRED = "required";
  345. /**
  346. * The "lfs" section
  347. * @since 4.11
  348. */
  349. public static final String CONFIG_SECTION_LFS = "lfs";
  350. /**
  351. * The "filesystem" section
  352. * @since 5.1.9
  353. */
  354. public static final String CONFIG_FILESYSTEM_SECTION = "filesystem";
  355. /**
  356. * The "timestampResolution" key
  357. * @since 5.1.9
  358. */
  359. public static final String CONFIG_KEY_TIMESTAMP_RESOLUTION = "timestampResolution";
  360. /**
  361. * The "minRacyThreshold" key
  362. *
  363. * @since 5.1.9
  364. */
  365. public static final String CONFIG_KEY_MIN_RACY_THRESHOLD = "minRacyThreshold";
  366. }