-
Notifications
You must be signed in to change notification settings - Fork 434
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
GEOMESA-3371 Lambda - Allow for customization of Kafka topic name (#3153
- Loading branch information
1 parent
9d9341f
commit a667fa3
Showing
7 changed files
with
96 additions
and
29 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
Lambda Index Configuration | ||
========================== | ||
|
||
GeoMesa exposes a variety of configuration options that can be used to customize and optimize a given installation. | ||
The Lambda data store supports most of the general options described under :ref:`index_config`. | ||
|
||
Kafka Topic Name | ||
---------------- | ||
|
||
Each SimpleFeatureType (or schema) will be written to a unique Kafka topic. By default, the topic will be | ||
named based on the persistent data store and the SimpleFeatureType name. | ||
|
||
If desired, the topic name can be set to an arbitrary value by setting the user data key ``geomesa.lambda.topic`` | ||
before calling ``createSchema``: | ||
|
||
.. code-block:: java | ||
SimpleFeatureType sft = ....; | ||
sft.getUserData().put("geomesa.lambda.topic", "myTopicName"); | ||
For more information on how to set schema options, see :ref:`set_sft_options`. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters