Getting error while running emr-etl-runner

For engineers Enrichment
1

i am trying to use Scala Stream Collector > raw stream > s3 > emr-etl-runner > redshift
but i am getting error while running emr-etl-runner

command:

./snowplow-emr-etl-runner --config emr.conf --resolver resolver.json

Error:

F, [2017-03-07T07:44:33.024000 #3191] FATAL – :

Psych::SyntaxError ((): found character ‘\t(TAB)’ that cannot start any token. (Do not use \t(TAB) for indentation) while scanning for the next token at line 13 column 1):
org/jruby/ext/psych/PsychParser.java:227:in parse' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:376:in parse_stream’
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:324:in parse' uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/psych.rb:251:in load’
uri:classloader:/emr-etl-runner/lib/snowplow-emr-etl-runner/cli.rb:152:in load_config' uri:classloader:/gems/contracts-0.11.0/lib/contracts/method_reference.rb:43:in send_to’
uri:classloader:/gems/contracts-0.11.0/lib/contracts/call_with.rb:76:in call_with' uri:classloader:/gems/contracts-0.11.0/lib/contracts/method_handler.rb:138:in block in redefine_method’
uri:classloader:/emr-etl-runner/lib/snowplow-emr-etl-runner/cli.rb:106:in process_options' uri:classloader:/emr-etl-runner/lib/snowplow-emr-etl-runner/cli.rb:92:in get_args_config_enrichments_resolver’
uri:classloader:/gems/contracts-0.11.0/lib/contracts/method_reference.rb:43:in send_to' uri:classloader:/gems/contracts-0.11.0/lib/contracts/call_with.rb:76:in call_with’
uri:classloader:/gems/contracts-0.11.0/lib/contracts/method_handler.rb:138:in block in redefine_method' uri:classloader:/emr-etl-runner/bin/snowplow-emr-etl-runner:37:in ’
org/jruby/RubyKernel.java:973:in load' uri:classloader:/META-INF/main.rb:1:in ’
org/jruby/RubyKernel.java:955:in require' uri:classloader:/META-INF/main.rb:1:in (root)’
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `’

emr.conf

aws:

Credentials can be hardcoded or set in environment variables

access_key_id: key
secret_access_key: key
s3:
region: us-west-2
buckets:
assets: s3://snowplow-hosted-assets # DO NOT CHANGE unless you are hosting the jarfiles etc yourself in your own bucket
jsonpath_assets: # If you have defined your own JSON Schemas, add the s3:// path to your own JSON Path files in your own bucket here
log: s3://snowplow-logs-xxxx/slog/
raw:
in:
s3://snowplow-logs-xxxx/logs
processing: s3://snowplow-logs-xxxx/raw/processing
archive: s3://snowplow-logs-xxxx/archive/raw
enriched:
good: s3://snowplow-logs-xxxx/enrich/good
bad: s3://snowplow-logs-xxxx/enrich/bad
errors: s3://snowplow-logs-xxxx/enrich/errors
archive: s3://snowplow-logs-xxxx/enriched
shredded:
good: s3://snowplow-logs-xxxx/shredded/good
bad: s3://snowplow-logs-xxxx/shredded/bad
errors: s3://snowplow-logs-xxxx/shredded/errors
archive: s3://snowplow-logs-xxxx/archive/shredded emr:
ami_version: 4.5.0
region: us-west-2
jobflow_role: EMR_EC2_DefaultRole
service_role: EMR_DefaultRole
placement: # Set this if not running in VPC. Leave blank otherwise
ec2_subnet_id: subnet-xxxxxxxx # Set this if running in VPC. Leave blank otherwise
ec2_key_name: snowplow-key
bootstrap: # Set this to specify custom boostrap actions. Leave empty otherwise
software:
hbase: # Optional. To launch on cluster, provide version, “0.92.0”, keep quotes. Leave empty otherwise.
lingual: # Optional. To launch on cluster, provide version, “1.1”, keep quotes. Leave empty otherwise.
# Adjust your Hadoop cluster below
jobflow:
master_instance_type: m1.medium
core_instance_count: 2
core_instance_type: m1.medium
core_instance_ebs: # Optional. Attach an EBS volume to each core instance.
volume_size: 100 # Gigabytes
volume_type: “gp2”
volume_iops: 400 # Optional. Will only be used if volume_type is “io1”
ebs_optimized: false # Optional. Will default to true
task_instance_count: 0 # Increase to use spot instances
task_instance_type: m1.medium
task_instance_bid: 0.015 # In USD. Adjust bid, or leave blank for non-spot-priced (i.e. on-demand) task instances
bootstrap_failure_tries: 3 # Number of times to attempt the job in the event of bootstrap failures
additional_info: # Optional JSON string for selecting additional features
collectors:
format: thrift # For example: ‘clj-tomcat’ for the Clojure Collector, ‘thrift’ for Thrift records, ‘tsv/com.amazon.aws.cloudfront/wd_access_log’ for Cloudfront access logs or ‘ndjson/urbanairship.connect/v1’ for UrbanAirship Connect events
enrich:
job_name: Snowplow ETL # Give your job a name
versions:
hadoop_enrich: 1.8.0 # Version of the Hadoop Enrichment process
hadoop_shred: 0.10.0 # Version of the Hadoop Shredding process
hadoop_elasticsearch: 0.1.0 # Version of the Hadoop to Elasticsearch copying process
continue_on_unexpected_error: false # Set to ‘true’ (and set :out_errors: above) if you don’t want any exceptions thrown from ETL
output_compression: NONE # Compression only supported with Redshift, set to NONE if you have Postgres targets. Allowed formats: NONE, GZIP
storage:
download:
folder: # Postgres-only config option. Where to store the downloaded files. Leave blank for Redshift
targets:
- name: “sp”
type: redshift
host: xx.xxxxxxxxxxxxxx.us-west-2.redshift.amazonaws.com # The endpoint as shown in the Redshift console
database: snowplow # Name of database
port: 5439 # Default Redshift port
ssl_mode: disable # One of disable (default), require, verify-ca or verify-full
table: atomic.events
username: username
password: password
maxerror: 1 # Stop loading on first error, or increase to permit more load errors
comprows: 200000 # Default for a 1 XL node cluster. Not used unless --include compupdate specified
monitoring:
tags: {} # Name-value pairs describing this job
logging:
level: DEBUG # You can optionally switch to INFO for production
snowplow:
method: get
app_id: emrapp # e.g. snowplow
collector: sp.domainname.com # e.g. d3rkrsqld9gmqf.cloudfront.net

2

This one seems pretty obvious, the error messages already explains the problem. I guess you have a Tab in your config files (emr.conf, resolver.json)

3 Likes