This is an automated email from the ASF dual-hosted git repository.
jagadish pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/samza.git
The following commit(s) were added to refs/heads/master by this push:
new 057a90a SAMZA-2086: Documentation fixes: change .md to .html
057a90a is described below
commit 057a90a544a03c3494d22cb43eff7b95a6450acd
Author: pchhokra <pchho...@linkedin.com>
AuthorDate: Fri Feb 1 13:10:28 2019 -0800
SAMZA-2086: Documentation fixes: change .md to .html
Author: pchhokra <pchho...@linkedin.com>
Reviewers: Jagadish<jagad...@apache.org>
Closes #894 from PawasChhokra/documentation
---
docs/learn/documentation/versioned/api/low-level-api.md | 2 +-
docs/learn/documentation/versioned/api/programming-model.md | 6 +++---
docs/learn/documentation/versioned/connectors/eventhubs.md | 2 +-
docs/learn/documentation/versioned/rest/monitors.md | 2 +-
4 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/learn/documentation/versioned/api/low-level-api.md
b/docs/learn/documentation/versioned/api/low-level-api.md
index 34d2b06..e3466af 100644
--- a/docs/learn/documentation/versioned/api/low-level-api.md
+++ b/docs/learn/documentation/versioned/api/low-level-api.md
@@ -276,7 +276,7 @@ For example:
### Legacy Applications
-For legacy Low Level API applications, you can continue specifying your
system, stream and store properties along with your task.class in
configuration. An incomplete example of configuration for legacy task
application looks like this (see the [configuration](../jobs/configuration.md)
documentation for more detail):
+For legacy Low Level API applications, you can continue specifying your
system, stream and store properties along with your task.class in
configuration. An incomplete example of configuration for legacy task
application looks like this (see the
[configuration](../jobs/configuration.html) documentation for more detail):
{% highlight jproperties %}
diff --git a/docs/learn/documentation/versioned/api/programming-model.md
b/docs/learn/documentation/versioned/api/programming-model.md
index efdcfa3..943c573 100644
--- a/docs/learn/documentation/versioned/api/programming-model.md
+++ b/docs/learn/documentation/versioned/api/programming-model.md
@@ -22,9 +22,9 @@ title: Programming Model
Samza provides multiple programming APIs to fit your use case:
1. Java APIs: Samza's provides two Java programming APIs that are ideal for
building advanced Stream Processing applications.
- 1. [High Level Streams API](high-level-api.md): Samza's flexible High
Level Streams API lets you describe your complex stream processing pipeline in
the form of a Directional Acyclic Graph (DAG) of operations on message streams.
It provides a rich set of built-in operators that simplify common stream
processing operations such as filtering, projection, repartitioning, joins, and
windows.
- 2. [Low Level Task API](low-level-api.md): Samza's powerful Low Level Task
API lets you write your application in terms of processing logic for each
incoming message.
-2. [Samza SQL](samza-sql.md): Samza SQL provides a declarative query language
for describing your stream processing logic. It lets you manipulate streams
using SQL predicates and UDFs instead of working with the physical
implementation details.
+ 1. [High Level Streams API](high-level-api.html): Samza's flexible High
Level Streams API lets you describe your complex stream processing pipeline in
the form of a Directional Acyclic Graph (DAG) of operations on message streams.
It provides a rich set of built-in operators that simplify common stream
processing operations such as filtering, projection, repartitioning, joins, and
windows.
+ 2. [Low Level Task API](low-level-api.html): Samza's powerful Low Level
Task API lets you write your application in terms of processing logic for each
incoming message.
+2. [Samza SQL](samza-sql.html): Samza SQL provides a declarative query
language for describing your stream processing logic. It lets you manipulate
streams using SQL predicates and UDFs instead of working with the physical
implementation details.
3. Apache Beam API: Samza also provides a [Apache Beam
runner](https://beam.apache.org/documentation/runners/capability-matrix/) to
run applications written using the Apache Beam API. This is considered as an
extension to the operators supported by the High Level Streams API in Samza.
diff --git a/docs/learn/documentation/versioned/connectors/eventhubs.md
b/docs/learn/documentation/versioned/connectors/eventhubs.md
index 11de3ff..a7c7a70 100644
--- a/docs/learn/documentation/versioned/connectors/eventhubs.md
+++ b/docs/learn/documentation/versioned/connectors/eventhubs.md
@@ -23,7 +23,7 @@ title: Event Hubs Connector
The Samza EventHubs connector provides access to [Azure
EventHubs](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-features),
Microsoft’s data streaming service on Azure. An eventhub is similar to a Kafka
topic and can have multiple partitions with producers and consumers. Each
message produced or consumed from an event hub is an instance of
[EventData](https://docs.microsoft.com/en-us/java/api/com.microsoft.azure.eventhubs._event_data).
-The [hello-samza](https://github.com/apache/samza-hello-samza) project
includes an
[example](../../../tutorials/versioned/samza-event-hubs-standalone.md) of
reading and writing to EventHubs.
+The [hello-samza](https://github.com/apache/samza-hello-samza) project
includes an
[example](../../../tutorials/versioned/samza-event-hubs-standalone.html) of
reading and writing to EventHubs.
### Concepts
diff --git a/docs/learn/documentation/versioned/rest/monitors.md
b/docs/learn/documentation/versioned/rest/monitors.md
index 7946968..2ca43e3 100644
--- a/docs/learn/documentation/versioned/rest/monitors.md
+++ b/docs/learn/documentation/versioned/rest/monitors.md
@@ -101,6 +101,6 @@ The configuration key
`monitor.monitorName.scheduling.interval.ms` defines the p
the `monitor()` method in milli seconds.
## Reporting metrics from Monitors
-Samza REST service allows the users to create and report metrics from their
monitors. Reporting metrics to a metrics system is encapsulated by the metrics
reporter, which should be defined in the samza-rest configuration file.
Configurations for metrics reporters in Samza REST service are the same as
[that of Samza Jobs](../container/metrics.md).
+Samza REST service allows the users to create and report metrics from their
monitors. Reporting metrics to a metrics system is encapsulated by the metrics
reporter, which should be defined in the samza-rest configuration file.
Configurations for metrics reporters in Samza REST service are the same as
[that of Samza Jobs](../container/metrics.html).
## [Resource Reference »](resource-directory.html)
