You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by ho...@apache.org on 2017/05/09 00:06:09 UTC

[1/2] lucene-solr:jira/solr-10290: remove TODOs added by automated conversion that have already been manually dealt with

Repository: lucene-solr
Updated Branches:
  refs/heads/jira/solr-10290 172bf3963 -> db902f5c9


remove TODOs added by automated conversion that have already been manually dealt with


Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/e00e2b8d
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/e00e2b8d
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/e00e2b8d

Branch: refs/heads/jira/solr-10290
Commit: e00e2b8d2e3503422eafb045c6bb6a5fee0152ae
Parents: 172bf39
Author: Chris Hostetter <ho...@apache.org>
Authored: Mon May 8 16:45:36 2017 -0700
Committer: Chris Hostetter <ho...@apache.org>
Committed: Mon May 8 16:45:36 2017 -0700

----------------------------------------------------------------------
 solr/solr-ref-guide/src/pagination-of-results.adoc    | 2 --
 solr/solr-ref-guide/src/upgrading-a-solr-cluster.adoc | 2 --
 2 files changed, 4 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/e00e2b8d/solr/solr-ref-guide/src/pagination-of-results.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/pagination-of-results.adoc b/solr/solr-ref-guide/src/pagination-of-results.adoc
index 9302c8a..78ee8ca 100644
--- a/solr/solr-ref-guide/src/pagination-of-results.adoc
+++ b/solr/solr-ref-guide/src/pagination-of-results.adoc
@@ -81,8 +81,6 @@ In addition to returning the top N sorted results (where you can control N using
 
 There are a few important constraints to be aware of when using `cursorMark` parameter in a Solr request
 
-// TODO: This 'ol' has problematic nested lists inside of it, needs manual editing
-
 . `cursorMark` and `start` are mutually exclusive parameters.
 * Your requests must either not include a `start` parameter, or it must be specified with a value of "```0```".
 . `sort` clauses must include the uniqueKey field (either `asc` or `desc`).

http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/e00e2b8d/solr/solr-ref-guide/src/upgrading-a-solr-cluster.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/upgrading-a-solr-cluster.adoc b/solr/solr-ref-guide/src/upgrading-a-solr-cluster.adoc
index 1751cba..b520633 100644
--- a/solr/solr-ref-guide/src/upgrading-a-solr-cluster.adoc
+++ b/solr/solr-ref-guide/src/upgrading-a-solr-cluster.adoc
@@ -17,8 +17,6 @@ The steps outlined on this page assume you use the default service name of "```s
 
 Here is a checklist of things you need to prepare before starting the upgrade process:
 
-// TODO: This 'ol' has problematic nested lists inside of it, needs manual editing
-
 1.  Examine the <<upgrading-solr.adoc#upgrading-solr,Upgrading Solr>> page to determine if any behavior changes in the new version of Solr will affect your installation.
 2.  If not using replication (ie: collections with replicationFactor > 1), then you should make a backup of each collection. If all of your collections use replication, then you don't technically need to make a backup since you will be upgrading and verifying each node individually.
 3.  Determine which Solr node is currently hosting the Overseer leader process in SolrCloud, as you should upgrade this node last. To determine the Overseer, use the Overseer Status API, see: <<collections-api.adoc#collections-api,Collections API>>.


[2/2] lucene-solr:jira/solr-10290: beef up TODO with some more details for fixing in future

Posted by ho...@apache.org.
beef up TODO with some more details for fixing in future


Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/db902f5c
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/db902f5c
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/db902f5c

Branch: refs/heads/jira/solr-10290
Commit: db902f5c97c12628cb1ef6534e5bea4fe9bebaa4
Parents: e00e2b8
Author: Chris Hostetter <ho...@apache.org>
Authored: Mon May 8 17:06:04 2017 -0700
Committer: Chris Hostetter <ho...@apache.org>
Committed: Mon May 8 17:06:04 2017 -0700

----------------------------------------------------------------------
 .../src/field-type-definitions-and-properties.adoc            | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/db902f5c/solr/solr-ref-guide/src/field-type-definitions-and-properties.adoc
----------------------------------------------------------------------
diff --git a/solr/solr-ref-guide/src/field-type-definitions-and-properties.adoc b/solr/solr-ref-guide/src/field-type-definitions-and-properties.adoc
index d49bef9..b2adacb 100644
--- a/solr/solr-ref-guide/src/field-type-definitions-and-properties.adoc
+++ b/solr/solr-ref-guide/src/field-type-definitions-and-properties.adoc
@@ -16,7 +16,12 @@ A field type definition can include four types of information:
 
 Field types are defined in `schema.xml`. Each field type is defined between `fieldType` elements. They can optionally be grouped within a `types` element. Here is an example of a field type definition for a type called `text_general`:
 
-//TODO callout isn't working in the PDF
+// TODO callout isn't working in the PDF...
+//    http://asciidoctor.org/docs/user-manual/#xml-callouts
+// TODO: relevant github issues w/possible font related work arounds...
+//  - https://github.com/asciidoctor/asciidoctor-pdf/issues/409
+//  - https://github.com/asciidoctor/asciidoctor-pdf/issues/377
+//  - https://github.com/asciidoctor/asciidoctor-pdf/issues/133
 [source,xml]
 ----
 <fieldType name="text_general" class="solr.TextField" positionIncrementGap="100"> <!--1-->