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

Major restructure/refactoring #92

Merged
merged 2 commits into from Oct 16, 2020
Merged

Major restructure/refactoring #92

merged 2 commits into from Oct 16, 2020

Conversation

jf-tech
Copy link
Owner

@jf-tech jf-tech commented Oct 16, 2020

  • Upgrade omni schema version to omni.2.1 due a number of incompatible schema changes:
    • 'result_type' -> 'type'
    • 'ignore_error_and_return_empty_str -> 'ignore_error'
    • 'keep_leading_trailing_space' -> 'no_trim'
  • Changed how we handle custom functions: previously we always use strings as in param type as well as result param type. Not anymore, all types are supported for custom function in and out params.
  • Changed the way how we package custom functions for extensions: previously we collect custom functions from all extensions and then pass all of them to the extension that is used; This feels weird, now changed to only the custom functions included in a particular extension are used in that extension.
  • Deprecated/removed most of the custom functions in favor of using 'javascript'.
  • A number of package renaming.

fixes #87, #89.

sorry for the largish PR. too hard / too lazy to tease it part.

- Upgrade omni schema version to `omni.2.1` due a number of incompatible schema changes:
    - `'result_type'` -> `'type'`
    - `'ignore_error_and_return_empty_str` -> `'ignore_error'`
    - `'keep_leading_trailing_space'` -> `'no_trim'`
- Changed how we handle custom functions: previously we always use strings as in param type as well as result param
type. Not anymore, all types are supported for custom function in and out params.
- Changed the way how we package custom functions for extensions: previously we collect custom functions from all
extensions and then pass all of them to the extension that is used; This feels weird, now changed to only the custom
functions included in a particular extension are used in that extension.
- Deprecated/removed most of the custom functions in favor of using 'javascript'.
- A number of package renaming.
@codecov
Copy link

codecov bot commented Oct 16, 2020

Codecov Report

Merging #92 into master will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##            master       #92    +/-   ##
==========================================
  Coverage   100.00%   100.00%            
==========================================
  Files           36        35     -1     
  Lines         1640      1439   -201     
==========================================
- Hits          1640      1439   -201     
Impacted Files Coverage Δ
customfuncs/customFuncs.go 100.00% <ø> (ø)
customfuncs/datetime.go 100.00% <ø> (ø)
extensions/omniv21/fileformat/csv/decl.go 100.00% <ø> (ø)
extensions/omniv21/fileformat/csv/reader.go 100.00% <ø> (ø)
extensions/omniv21/fileformat/json/format.go 100.00% <ø> (ø)
extensions/omniv21/fileformat/json/reader.go 100.00% <ø> (ø)
extensions/omniv21/fileformat/xml/format.go 100.00% <ø> (ø)
extensions/omniv21/fileformat/xml/reader.go 100.00% <ø> (ø)
extensions/omniv21/ingester.go 100.00% <ø> (ø)
transform.go 100.00% <ø> (ø)
... and 16 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ef2fd9a...a8b89b7. Read the comment docs.

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

Successfully merging this pull request may close these issues.

Let 'javascript' handle aggregation!
1 participant