Clone
Abdullah Alamoudi <bamousaa@gmail.com>
committed
on 25 Jul 18
[NO ISSUE] Allow MetadataProvider config to store non String values
- user model changes: no
- storage format changes: no
- interface change… Show more
[NO ISSUE] Allow MetadataProvider config to store non String values

- user model changes: no

- storage format changes: no

- interface changes: yes

Details:

- In many cases, we would like to associate a value with a key

 in MetadataProvider to be accessed during the compilation

 of jobs. However, currently, there is no place to store

 such values, so we ended up storing them in the config

 map.

- The config map is a <String, String> map and so, we would

 write our values as a string and then parse them when needed.

- To avoid this, and to avoid introducing a new map, we simply

 change the config stored in MetadataProvider from <String,String>

 to <String, Object>.

Change-Id: I55b392ad199d74b0f3cffdc38b54593b12ec1a06

Reviewed-on: https://asterix-gerrit.ics.uci.edu/2795

Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>

Contrib: Jenkins <jenkins@fulliautomatix.ics.uci.edu>

Reviewed-by: Murtadha Hubail <mhubail@apache.org>

Integration-Tests: Murtadha Hubail <mhubail@apache.org>

Show less