Thanks Joe. For community:
You did bring up a good point about external viewer and what we actually ended up doing was run a subset of the mime.type to and ExecuteStream processor that could convert it to text and then we UpdateAttribute to mime.type = text/plain > Then auto terminate success. Then we can view the provenance event of the success out of the UpdateAttribute. The use requirement to view other mime types was mainly for troubleshooting purposes so the flow I described above will work for us. On Wed, May 17, 2017 at 9:38 AM Joe Witt <[email protected]> wrote: > At present it is not designed as a clearly API separated extension > point like processors or controller services and the like. It might > make more sense to enable integration to an external viewer > service/capability than to make it a first class extension point. > But, for now, it requires internal changes and a custom build. > > thanks > > On Wed, May 17, 2017 at 9:35 AM, Juan Sequeiros <[email protected]> > wrote: > > Good morning, > > > > How involved is it to add an additional content viewer for a mime type? > > Our quick preliminary research leads us to modifying a few pieces of > > framework. > > > > Is this right path? Has anyone been able to add an additional mime type > to > > be viewed under provenance "view" function? > > > > Thank you. >
