List view

• Provide mechanism to inject custom generators and output interceptors

  We want users to be able to: * define their own custom generators. Eg if one of the banks wants their own special generator for valid bank account ids they should be able to implement an interface and inject their class into our code at runtime and reference it in the profile.json. Created task #1430 for this * intercept an output row and inject some post processing. Created task #1458 for this For custom generators need to: * Work out how we can use and integrate custom generators into the profile.json and the code - see how our other generators (eg ISIN) are used in the code and what needed ot be implemented so can get an idea of how custom generators can get integrated - may need to refactor ISIN etc so they all use a common approach and integrate into the code in same way * Define an interface that the custom generator needs to implement - i believe there could be a few methods need to implement - eg there could be a "negation" method we need to provide * work out how to inject a class/jar at runtime into our data helix code and how we can get hold of the class) - Clement has thought about this for the profiler so talk to him about how he envisioned injecting plug-in classifiers to the profiler * define an example custom generator and make sure can inject it and use it For output interceptors need to: * define exactly where intercept it. As we can have multiple output formats we need to work out how we can change the output row before its formatted to csv/json format or decide if * think of the kinds of things want to do so can work out what interface want to provide * define interface and create plugin framework similar to what do for custom generators

  No due date

  •2/4 issues closed
  50% complete2 open2 closed

• Allow field values to depend on multiple other field values

  See #1317 for the original epic about this (which converted to this milestone) Recently we added some single date dependency relationships in #804 and #1235 (which should do first) exists to do the same for numbers We now want to be able to handle having fields depend on multiple fields rather than only one. This is so can define Open, Close, High and Low price columns where: Both Open and Close prices are constrained to be between Low and High; Low is <= High Ideally would make the solution generic across dates and numbers so that there is less repeated code. Want to be able to do things like: Number 1 > Number 2 and Number 1 < Number 3. ``` { "field": "Open", "is": "lessThan", "otherField": "High" } { "field": "Open", "is": "greaterThan", "otherField": "Close" } ``` Not currently supported: Number 1 = Number 2 - Number 3 ``` { "field": "bar", "is": "equalTo", "otherField": "foo", "offsetField": "foobar" } ``` Likewise for dates and any other fields that can do single dependencies for. There is already a story for this at #1240

  No due date

  •4/5 issues closed
  80% complete1 open4 closed