Hey Andrew, If your message is a valid JSON (it seems to be), then a parser is able to read it an decode a literal string. The next trick is to put this results into a FlowFile content/body and run another EvaluateJsonPath/JoltTransformer chain. I did a quick experiment here, and it seems to work fine. ... View more

There is no hard-coded limit, but there is definitely some limit in terms of performance. Flow File attributes are held in memory (in addition to being persisted to disk) so more attributes means more Java objects on the heap, means more garbage collection pressure. I don't think there is any way to set what the limit is because it depends on how much data is in the attributes, how much memory you have, how many flow files, etc. ... View more

There is no preset limit on the number of fields that you can define in Solr. You will be limited by the resources that you allow Solr to access; RAM, disk etc. There are also cache settings to take into consideration. But when you mention numbers like 100K-1000K, I would suggest that you look at the design of your collections instead. The limit in size for a particular field varies with the type of field. Here is a link to the solr wiki describing built-in solr fields. ... View more

@Andrew Watson You can set cell level acls via the HBase shell or via HBase's Java API. This type of policy is not exposed or controlled via Ranger. If possible, I would implement row level policies in a client-side application, as HBase's cell ACLs are expensive (additional metadata must be stored and read with every cell). My favorite solution is to create a Phoenix View that exposes only specific rows. As noted above, your client-side app would have to decide whether to allow access to a given view. ... View more