Skip to content
This repository has been archived by the owner on Jun 21, 2023. It is now read-only.

Commit

Permalink
Remove outdated text from Readme (close #9)
Browse files Browse the repository at this point in the history
  • Loading branch information
joaolcorreia authored and adatzer committed Aug 25, 2022
1 parent 97323c9 commit 8be8ed9
Showing 1 changed file with 1 addition and 7 deletions.
8 changes: 1 addition & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,17 +42,11 @@ For Windows:
> java -jar /path/to/igluctl lint /path/to/schemas/com.mycompany/my_new_event_or_context
```

Igluctl has two severity levels that it can use when validating schemas. By default it uses level (1), which checks that the schemas are simply valid. We recommend validating schemas against a higher level (2). This will fail schemas that:
Igluctl will fail validating schemas that:

1. Define a string field without a `maxLength` property. That ensures that when e.g. the corresponding Redshift table DDL is generated, the correct associated column length can be unambiguously set
2. Define a numeric field without a `minimum` and `maximum` properties. That ensures that the when e.g. the corresponding Redshift table DDL is generated, the right numeric field type is set.

To lint the schemas using the higher severity level (2) run:

```
$ /path/to/igluctl lint /path/to/schemas/com.mycompany/my_new_event_or_context --severityLevel 2
```

## 2. Uploading the schemas to Iglu

Once you have created or updated your schemas, you need to push them to Iglu so that they're accessible to the Snowplow data pipeline.
Expand Down

0 comments on commit 8be8ed9

Please sign in to comment.