Skip to content

DOCSP-51965: Fix schemaHints option #266

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions source/batch-mode/batch-read-config.txt
Original file line number Diff line number Diff line change
Expand Up @@ -160,9 +160,9 @@ You can configure the following properties when reading data from MongoDB in bat
|
| **Default:** ``false``

* - ``schemaHint``
* - ``schemaHints``
- | Specifies a partial schema of known field types to use when inferring
the schema for the collection. To learn more about the ``schemaHint``
the schema for the collection. To learn more about the ``schemaHints``
option, see the :ref:`spark-schema-hint` section.
|
| **Default:** None
Expand Down
8 changes: 4 additions & 4 deletions source/batch-mode/batch-read.txt
Original file line number Diff line number Diff line change
Expand Up @@ -66,8 +66,8 @@ Specify Known Fields with Schema Hints
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

You can specify a schema containing known field values to use during
schema inference by specifying the ``schemaHint`` configuration option. You can
specify the ``schemaHint`` option in any of the following Spark formats:
schema inference by specifying the ``schemaHints`` configuration option. You can
specify the ``schemaHints`` option in any of the following Spark formats:

.. list-table::
:header-rows: 1
Expand All @@ -90,7 +90,7 @@ specify the ``schemaHint`` option in any of the following Spark formats:
{ "name": "<field name>", "type": "<field type>", "nullable": <true/false> },
{ "name": "<field name>", "type": "<field type>", "nullable": <true/false> }]}

The following example shows how to specify the ``schemaHint`` option in each
The following example shows how to specify the ``schemaHints`` option in each
format by using the Spark shell. The example specifies a string-valued field named
``"value"`` and an integer-valued field named ``"count"``.

Expand All @@ -114,7 +114,7 @@ format by using the Spark shell. The example specifies a string-valued field nam
// Generate JSON format
mySchema.json

You can also specify the ``schemaHint`` option in the Simple String DDL format,
You can also specify the ``schemaHints`` option in the Simple String DDL format,
or in JSON format by using PySpark, as shown in the following example:

.. code-block:: python
Expand Down
4 changes: 2 additions & 2 deletions source/streaming-mode/streaming-read-config.txt
Original file line number Diff line number Diff line change
Expand Up @@ -133,9 +133,9 @@ You can configure the following properties when reading data from MongoDB in str
|
| **Default:** ``false``

* - ``schemaHint``
* - ``schemaHints``
- | Specifies a partial schema of known field types to use when inferring
the schema for the collection. To learn more about the ``schemaHint``
the schema for the collection. To learn more about the ``schemaHints``
option, see the :ref:`spark-schema-hint` section.
|
| **Default:** None
Expand Down
Loading