[jira] [Updated] (KNOX-715) submitJava should allow multiple argument via arg()
[
https://issues.apache.org/jira/browse/KNOX-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Larry McCay updated KNOX-715:
-
Status: Patch Available (was: Open)
> submitJava should allow multiple argument via arg()
> ---
>
> Key: KNOX-715
> URL: https://issues.apache.org/jira/browse/KNOX-715
> Project: Apache Knox
> Issue Type: Bug
> Components: ClientDSL
>Affects Versions: 0.7.0
>Reporter: Pierre Regazzoni
>Assignee: Pierre Regazzoni
> Fix For: 0.9.1
>
> Attachments: KNOX-715-002.patch, KNOX-715-003.patch, KNOX-715.patch
>
>
> Like with submitPig (KNOX-712). I want to be able to provide multiple
> argument when submitting a jar via submitJava. For example, should be able to
> do:
> {noformat}
> jobId = Job.submitJava(session) \
> .jar( "path-to-my-jar" ) \
> .app( "class-name" ) \
> .arg( "argument1").arg("value1") \
> .arg( "argument2").arg("value2") \
> .arg( "argument3") \
> .output("path-to-output-dir ) \
> .now().jobId
> {noformat}
> Current code limits execution to only specifying jar,class,input,output. I
> should have a patch for it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KNOX-715) submitJava should allow multiple argument via arg()
[
https://issues.apache.org/jira/browse/KNOX-715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324925#comment-15324925
]
Larry McCay commented on KNOX-715:
--
I've tried to reproduce the compilation and rat violations locally but haven't
been able to.
Going to resubmit the patch to let jenkins run again.
I am also still not able to get the expected output from running the new sample.
Will spend some more time to try and get it to succeed.
> submitJava should allow multiple argument via arg()
> ---
>
> Key: KNOX-715
> URL: https://issues.apache.org/jira/browse/KNOX-715
> Project: Apache Knox
> Issue Type: Bug
> Components: ClientDSL
>Affects Versions: 0.7.0
>Reporter: Pierre Regazzoni
>Assignee: Pierre Regazzoni
> Fix For: 0.9.1
>
> Attachments: KNOX-715-002.patch, KNOX-715-003.patch, KNOX-715.patch
>
>
> Like with submitPig (KNOX-712). I want to be able to provide multiple
> argument when submitting a jar via submitJava. For example, should be able to
> do:
> {noformat}
> jobId = Job.submitJava(session) \
> .jar( "path-to-my-jar" ) \
> .app( "class-name" ) \
> .arg( "argument1").arg("value1") \
> .arg( "argument2").arg("value2") \
> .arg( "argument3") \
> .output("path-to-output-dir ) \
> .now().jobId
> {noformat}
> Current code limits execution to only specifying jar,class,input,output. I
> should have a patch for it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KNOX-715) submitJava should allow multiple argument via arg()
[
https://issues.apache.org/jira/browse/KNOX-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Larry McCay updated KNOX-715:
-
Status: Open (was: Patch Available)
> submitJava should allow multiple argument via arg()
> ---
>
> Key: KNOX-715
> URL: https://issues.apache.org/jira/browse/KNOX-715
> Project: Apache Knox
> Issue Type: Bug
> Components: ClientDSL
>Affects Versions: 0.7.0
>Reporter: Pierre Regazzoni
>Assignee: Pierre Regazzoni
> Fix For: 0.9.1
>
> Attachments: KNOX-715-002.patch, KNOX-715-003.patch, KNOX-715.patch
>
>
> Like with submitPig (KNOX-712). I want to be able to provide multiple
> argument when submitting a jar via submitJava. For example, should be able to
> do:
> {noformat}
> jobId = Job.submitJava(session) \
> .jar( "path-to-my-jar" ) \
> .app( "class-name" ) \
> .arg( "argument1").arg("value1") \
> .arg( "argument2").arg("value2") \
> .arg( "argument3") \
> .output("path-to-output-dir ) \
> .now().jobId
> {noformat}
> Current code limits execution to only specifying jar,class,input,output. I
> should have a patch for it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KNOX-705) Views in Ambari UI don't render when proxied by the AMBARIUI service
[ https://issues.apache.org/jira/browse/KNOX-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324446#comment-15324446 ] Larry McCay commented on KNOX-705: -- [~sumit.gupta] - what is the status of this issue? Are we able to spin off another child for outstanding issues and target those in a follow up release? Do we have some sense of what the core Ambari views are and which currently work? > Views in Ambari UI don't render when proxied by the AMBARIUI service > > > Key: KNOX-705 > URL: https://issues.apache.org/jira/browse/KNOX-705 > Project: Apache Knox > Issue Type: Bug > Components: Server >Affects Versions: 0.9.0 >Reporter: Sumit Gupta >Assignee: Sumit Gupta > Fix For: 0.9.1 > > > When using the AMBARIUI service to proxy the Ambari service's UI, the various > 'views' don't render. The rest of the UI around management of services works > correctly. The URL's for the views are not being rewritten correctly right > now as they are missing the gateway's context path. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KNOX-714) Remove Permissive MIT License from NOTICE File
[ https://issues.apache.org/jira/browse/KNOX-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry McCay resolved KNOX-714. -- Resolution: Fixed > Remove Permissive MIT License from NOTICE File > -- > > Key: KNOX-714 > URL: https://issues.apache.org/jira/browse/KNOX-714 > Project: Apache Knox > Issue Type: Bug > Components: Release >Reporter: Larry McCay >Assignee: Larry McCay > Fix For: 0.9.1 > > > Mention of MIT license for JQuery within the NOTICE file is inappropriate and > needs to be removed. The actual MIT license is already reflected in the > LICENSE file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KNOX-711) Global Rewrite Rules for a Topology are Problematic
[ https://issues.apache.org/jira/browse/KNOX-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324409#comment-15324409 ] Larry McCay commented on KNOX-711: -- Hi [~sumit.gupta] - can we close this JIRA? > Global Rewrite Rules for a Topology are Problematic > --- > > Key: KNOX-711 > URL: https://issues.apache.org/jira/browse/KNOX-711 > Project: Apache Knox > Issue Type: Bug > Components: Server >Reporter: Larry McCay >Assignee: Sumit Gupta > Fix For: 0.9.1 > > Attachments: KNOX_711-2.patch, KNOX_711.patch > > > Due to the fact that the rewrite rules for a topology are global, matching > patterns that are more generic may cause indeterminate URL rewriting. This is > more of a problem for proxying UIs than it is for services but since the > patterns are up to the discretion of the developer they could certainly also > apply to service definitions. > For instance, the JOBHISTORY UI rewrite.xml contains a pattern like > "/static/**". This pattern will match an root relative URLs that start with > "static". Since other hadoop UIs that may be proxied through the same > topology will reference similar resources, the URL rewriting may match the > pattern from the wrong application and interject the service/UI name into the > URL which will result in 404's. > This has been observed for the HBase UI when the JOBHISTORY UI is also in the > same topology. > The workaround for this issue is to deploy separate topologies for UIs that > have overlapping matching patterns. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
