You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucenenet.apache.org by ni...@apache.org on 2021/03/30 15:05:37 UTC
[lucenenet] 10/15: docs: Lucene.Net.Misc: Fixed broken formatting
and links (see #284, #300)
This is an automated email from the ASF dual-hosted git repository.
nightowl888 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/lucenenet.git
commit ba2e0aef43255a83957bb33184be0403e9d0cc73
Author: Shad Storhaug <sh...@shadstorhaug.com>
AuthorDate: Tue Mar 30 19:43:39 2021 +0700
docs: Lucene.Net.Misc: Fixed broken formatting and links (see #284, #300)
---
src/Lucene.Net.Misc/Index/Sorter/package.md | 6 +++---
src/Lucene.Net.Misc/overview.md | 9 ++++++++-
2 files changed, 11 insertions(+), 4 deletions(-)
diff --git a/src/Lucene.Net.Misc/Index/Sorter/package.md b/src/Lucene.Net.Misc/Index/Sorter/package.md
index 4477e73..a039ae3 100644
--- a/src/Lucene.Net.Misc/Index/Sorter/package.md
+++ b/src/Lucene.Net.Misc/Index/Sorter/package.md
@@ -1,4 +1,4 @@
----
+---
uid: Lucene.Net.Index.Sorter
summary: *content
---
@@ -20,9 +20,9 @@ summary: *content
limitations under the License.
-->
-Provides index sorting capablities. The application can use any
+Provides index sorting capabilities. The application can use any
Sort specification, e.g. to sort by fields using DocValues or FieldCache, or to
-reverse the order of the documents (by using SortField.Type.DOC in reverse).
+reverse the order of the documents (by using [SortFieldType.DOC](xref:Lucene.Net.Search.SortFieldType#Lucene_Net_Search_SortFieldType_DOC) in reverse).
Multi-level sorts can be specified the same way you would when searching, by
building Sort from multiple SortFields.
diff --git a/src/Lucene.Net.Misc/overview.md b/src/Lucene.Net.Misc/overview.md
index 29319cb..733530a 100644
--- a/src/Lucene.Net.Misc/overview.md
+++ b/src/Lucene.Net.Misc/overview.md
@@ -26,6 +26,12 @@ summary: *content
The misc package has various tools for splitting/merging indices,
changing norms, finding high freq terms, and others.
+
+<!--
+
+LUCENENET specific - we didn't port the NativeUnixDirectory, and it is not clear whether there is any advantage to doing so in .NET.
+See: https://github.com/apache/lucenenet/issues/276
+
## NativeUnixDirectory
__NOTE__: This uses C++ sources (accessible via JNI), which you'll
@@ -55,4 +61,5 @@ Steps to build:
NativePosixUtil.cpp/java also expose access to the posix_madvise,
madvise, posix_fadvise functions, which are somewhat more cross
platform than O_DIRECT, however, in testing (see above link), these
-APIs did not seem to help prevent buffer cache eviction.
\ No newline at end of file
+APIs did not seem to help prevent buffer cache eviction.
+-->
\ No newline at end of file