[BEAM-12675] Fix issue with language switcher on hadoop page (#15243)
diff --git a/website/CONTRIBUTE.md b/website/CONTRIBUTE.md
index 13fa561..b2023f4 100644
--- a/website/CONTRIBUTE.md
+++ b/website/CONTRIBUTE.md
@@ -184,6 +184,33 @@
The purpose is to switch languages of codeblocks.
+You can also provide language tabs without the language switcher widget. To do so, place `{{< highlight >}}` shortcodes next to each other, like this:
+
+```
+{{< highlight java >}}
+// Java code here...
+{{< /highlight >}}
+{{< highlight py >}}
+# Python code here...
+{{< /highlight >}}
+```
+
+Note that the `{{< highlight >}}` blocks should be directly adjacent to each other, without an extra return between them.
+
+Do NOT do this:
+
+```
+{{< highlight java >}}
+// Java code here...
+{{< /highlight >}}
+
+{{< highlight py >}}
+# Python code here...
+{{< /highlight >}}
+```
+
+In some circumstances, the Hugo markdown parser will generate a pair of empty `<p>` tags for the extra return, and that breaks the formatting of the code tabs. TODO: Fix this issue: [BEAM-12688](https://issues.apache.org/jira/browse/BEAM-12688).
+
### Code highlighting
To be consistent, please prefer to use `{{< highlight >}}` syntax instead of ` ``` `, for code-blocks or syntax-highlighters.
diff --git a/website/www/site/content/en/documentation/io/built-in/hadoop.md b/website/www/site/content/en/documentation/io/built-in/hadoop.md
index 9dc9104..48d6a4b 100644
--- a/website/www/site/content/en/documentation/io/built-in/hadoop.md
+++ b/website/www/site/content/en/documentation/io/built-in/hadoop.md
@@ -34,6 +34,7 @@
- `value.class` - The `Value` class returned by the `InputFormat` in `mapreduce.job.inputformat.class`.
For example:
+
{{< highlight java >}}
Configuration myHadoopConfiguration = new Configuration(false);
// Set Hadoop InputFormat, key and value class in configuration
@@ -50,6 +51,7 @@
You will need to check if the `Key` and `Value` classes output by the `InputFormat` have a Beam `Coder` available. If not, you can use `withKeyTranslation` or `withValueTranslation` to specify a method transforming instances of those classes into another class that is supported by a Beam `Coder`. These settings are optional and you don't need to specify translation for both key and value.
For example:
+
{{< highlight java >}}
SimpleFunction<InputFormatKeyClass, MyKeyClass> myOutputKeyType =
new SimpleFunction<InputFormatKeyClass, MyKeyClass>() {
@@ -64,7 +66,6 @@
}
};
{{< /highlight >}}
-
{{< highlight py >}}
# The Beam SDK for Python does not support Hadoop Input/Output Format IO.
{{< /highlight >}}
@@ -291,6 +292,7 @@
There are scenarios when this may prove faster than accessing content through the region servers using the `HBaseIO`.
A table snapshot can be taken using the HBase shell or programmatically:
+
{{< highlight java >}}
try (
Connection connection = ConnectionFactory.createConnection(hbaseConf);
@@ -364,6 +366,7 @@
_Note_: All mentioned values have appropriate constants. E.g.: `HadoopFormatIO.OUTPUT_FORMAT_CLASS_ATTR`.
For example:
+
{{< highlight java >}}
Configuration myHadoopConfiguration = new Configuration(false);
// Set Hadoop OutputFormat, key and value class in configuration
