Skip to content
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

Multiple sinks #128

Open
szareiangm opened this issue Jul 2, 2019 · 0 comments
Open

Multiple sinks #128

szareiangm opened this issue Jul 2, 2019 · 0 comments

Comments

@szareiangm
Copy link
Contributor

szareiangm commented Jul 2, 2019

The goals is to split the sink based on a field, i.e. app_name or event_name. This way, we would read the stream once and write to multiple clusters with one batch of read.

This also adds a little refactor to the configuration file to support this feature. It could be something like below:

{
 "splitField": "app_name"
  "sinks": [
      {
       "type":"elasticsearch",
       "mapping": {
         "app_name":["theglobeandmail-website","theglobeandmail-amp"]
       },
       "settings":{
          // current details under elasticsearch
        },
       {
       "type":"elasticsearch",
       "mapping": {
         "app_name":["globeadvisor-website","globeinvestor-amp"]
       },
       "settings":{
          // current details under elasticsearch
        }
   ]
}

This might pave the way towards having one repository that would merge snoplow-s3-loader functionality inside this repo or the other way, with "type":"s3"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant