Skip to content

Releases: bricolages/bricolage

version 5.18.0 released

13 Oct 04:13
Compare
Choose a tag to compare
  • [new] New parameter "no-backup" for my-import and my-migrate job classes.
  • [new] New parameter "sql_log_level" for the psql data source.
  • [new] Shows SQL source location before the query.
  • Raises ConnectionError for all connection-level problems, while it raises SQLError for SQL-level errors.

version 5.17.2 released

29 Sep 05:43
Compare
Choose a tag to compare
  • [fix] Using CommandLineApplication with --environment option causes unexpected option error

version 5.17.1 released

22 Sep 15:51
Compare
Choose a tag to compare
  • [fix] --dry-run option did not work for my-import job class.
  • [new] AWS access key id & secret key are now optional for S3 data sources (to allow using EC2 instance or ECS task attached IAM role)

version 5.17.0 released

14 Sep 10:04
Compare
Choose a tag to compare
  • [new] Supports Redshfit attached IAM role for COPY and UNLOAD.

version 5.16.7 released

14 Jun 03:16
Compare
Choose a tag to compare
  • [fix] require 'bricolage/context' wrongly caused NameError.
  • [new] PostgresConnection#drop_table_force utilizes DROP TABLE IF EXISTS.

version 5.16.6 released

14 Jun 03:15
Compare
Choose a tag to compare
  • rebuild-rename, rebuild-drop, my-import, my-migrate, create, createview: Reduces the number of transactions for speed.

version 5.16.5 released

14 Jun 03:14
Compare
Choose a tag to compare
  • [fix] my-import: mys3dump: Fixes buffer size problem.
  • [fix] my-import: mys3dump: Escapes more meta characters (e.g. \n, \r, \v, ...).

version 5.16.4 released

25 May 03:33
Compare
Choose a tag to compare
  • [fix] Adds gem dependency to rake
  • [fix] my-import: Reduces warning log messages

version 5.16.3 relaesed

25 May 03:34
Compare
Choose a tag to compare
  • [fix] streaming_load: Disables statupdate for log staging table, it is useless.

version 5.16.2 released

07 Apr 10:10
Compare
Choose a tag to compare
  • [fix] streaming_load: Disables compupdate on COPY. This might cause Assert error on some clusters.