Matt,
I left java.args.15 out of my scope as I could not find a reason to use it that not connected to the additional step documented by sumo when running NiFi against MapR's environment. But yes, having java.args.15 replaced by a property would streamline deployment of NiFi where custom args are required at bootstrap (e.g. sumo's separate nar). At the present the only instance where I know this is required is where MapR-FS is used as "HDFS" and I agree with the overall idea of preventing modifications targeted at a single vendor. Happy to bring it to the table once we find an agreement around the rest. :-) The hadoop.version and other versions could all be set via the settings.xml profiles but I think this would be clumsy as a required step (particularly when we factor that vendors seem to have an incredible appetite for point releases - vide https://repository.cloudera.com/artifactory/cloudera-repos/org/apache/hadoop/hadoop-common/ ). As consequence, my settings are as simple as: <profiles> <profile> <id>mapr</id> <repositories> <repository> <id>mapr-repo</id> <name>MapR Repository</name> <url>http://repository.mapr.com/maven/</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository> </repositories> </profile> <profile> <id>cdh</id> <repositories> <repository> <id>cloudera</id> <url>https://repository.cloudera.com/artifactory/cloudera-repos/ </url> </repository> </repositories> </profile> </profiles> While I understand people building a complex combination of platforms (MapR-FS running side by side with an CDH cluster offering Impala) may want to customise their build environment I am more concerned about minimising the steps beginners take to use NiFi against the platforms they may have access to (vide Ravi's message @ users). Cheers On Thu, Jun 16, 2016 at 10:26 AM, Matt Burgess <[email protected]> wrote: > Your hadoop.version could also be set by this profile, right? And > conceivably hive.version and hbase.version (et al) if all has been set up > correctly (and we can change if not, as we should be setting all dependency > versions from properties). > > Do you need the java.arg.15 for this? I think it's worth discussing that > (blank by default but ready for action) as a general improvement for NiFi, > not just for Hadoop flavors but for enabling various things via system > properties during build (etc.) > > Regards, > Matt > >
