Releases: civitaspo/embulk-input-dynamodb
Releases · civitaspo/embulk-input-dynamodb
1.0.4
1.0.3
1.0.2
1.0.1
1.0.0
0.3.1
CHANGELOG
- [BugFix] #23 Throw scala.MatchError when using "limit" option. (Fix #21)
- [Enhancement] #23 Use embulk-core tests library instead of embulk-test.
Gem
https://rubygems.org/gems/embulk-input-dynamodb/versions/0.3.1
Code Diff
0.3.0
CHANGELOG
- [Enhancement] Update dependencies
- [Enhancement] #9 Use TestingEmbulk instead of EmbulkEmbed when testing
- [Enhancement] #10 Reduce test dependencies
- [Enhancement] #13 Use Github Actions instead of CircleCI.
- [Enhancement] #15 Improve development environments
- Introduce scalafmt with spotless
- Fix the format violations
- Add scalafmt to CI
- Add CHANGELOG
- Add an example
- Update README about development
- [Enhancement] #16 Cleanup gradle settings
- [New Feature] #18 Introduce new
auth_method
:"session"
,"anonymous"
,"web_identity_token"
,"default"
."anonymous"
: uses anonymous access. This auth method can access only public files."session"
: uses temporary-generated access_key_id, secret_access_key and session_token."assume_role"
: uses temporary-generated credentials by assuming role_arn role."web_identity_token"
: uses temporary-generated credentials by assuming role_arn role with web identity."default"
: uses AWS SDK's default strategy to look up available credentials from runtime environment. This method behaves like the combination of the following methods."env"
"properties"
"web_identity_token"
"profile"
"instance"
- [New Feature] #18 Support
http_proxy
option when generating aws credentials. - [Enhancement] #18 The default value of
auth_method
option become"default"
. Whenaccess_key_id
andsecret_access_key
options are set, use"basic"
asauth_method
for backward compatibility. - [Deprecated] #18 Make
access_key
andsecret_key
options deprecated. Useaccess_key_id
andsecret_access_key
options instead. - [Deprecated] #18 Make
end_point
option deprecated. Useendpoint
option instead. - [Deprecated] #19 The original operation implementation is deprecated, so the below options become deprecated.
- operation: Use query option or scan option instead.
- limit: Use query.batch_size option or query.batch_size instead.
- scan_limit: Use query.batch_size option or query.batch_size instead.
- record_limit: Use query.limit option or query.limit instead.
- filters: Use query.filter_expression option or query.filter_expression instead.
- [New Feature] #19 Introduce new options scan, query to support all configurations for Dynamodb Scan/Query Operation API except legacy configurations.
- NOTE: This operation stores
null
AttributeValue asnull
, though, in the deprecated operation,null
is converted arbitrarily. (string
-> empty string,long
->0
,double
->0.0
,boolean
->false
) - NOTE: This operation stores timestamp values by parsing user-defined format, though the deprecated operation skips storing values when the column type is defined as
timestamp
without any errors. - NOTE: This operation can convert the specific type of the attribute that you specify in column.attribute_type to Embulk types, though the deprecated operation can only convert Embulk types that match a particular Dynamodb Attribute type.
- NOTE: This operation stores
- [Enhancement] #19 You can store each dynamodb item as JSON, so columns option becomes optional.
- [Enhancement] #19 You can specify the
AttributeValue
type (like"S"
,"N"
,"SS"
and so on) used when converting AttributeValue to Embulk type. - [BugFix] #19 Avoid
NullPointerException
when TypeN
AttributeValue hasnull
in the deprecated operation. - [Enhancement] #19 Examples work without real Dynamodb.
- [Enhancement] #19 Add more examples.
Gem
https://rubygems.org/gems/embulk-input-dynamodb/versions/0.3.0