4/24/2018 12:45:28 AM
search bug
|
4/23/2018 7:26:14 PM
won't support schedule like:
run every second
run every 2 second
run every minute at 2nd second.
The check is done on project uploading.
|
4/23/2018 2:09:56 PM
should produce less false positives without intervention in the environment by:
*increasing time interval in a MetricManagerTest
*fixing the source for computing of the time interval in a MetricManagerTest
*closing file descriptors in a DirectoryFlowLoaderTest
Also, some typos were fixed.
|
4/20/2018 6:47:32 PM
trigger and flow trigger instances:
1. scheduled flow trigger
2. new tab of list of recent flow trigger instances for a particular flow
3. flow trigger properties for a particular flow
4. flow trigger instances status for a flow execution
5. page for a flow trigger instance execution(page link http://AZURL/executor/triggerinstanceid=XXX):
|
4/20/2018 6:45:48 PM
test related Jar functions and were messing /temp/HadoopTest folder. It caused out test fail.
In this PR, I changed the temp folder to the $buildDir/temp folder. $buildDir/temp is already ignored in .gitignore file.
|
4/20/2018 5:53:01 PM
was a fault to keep the pig file in a non-module folder. So moving it back to az-hadoop-jobtype-plugin module.
|
4/20/2018 2:34:01 PM
(#1742)
|
4/17/2018 9:23:14 PM
fix to #1618 Any logged user could download a zip from project by a request to `host/manager?project=projectName&download=true`, so this PR creates a check for READ permission to download.
### Before: Accessing `host/manager?project=projectName&download=true`, any logged user could download the project with no permission
### After:
`guest` has no permission to `READ` project `blabla`.
`host/manager?project=blabla&download=true`
|
4/16/2018 6:32:15 PM
(#1730)
We found a security hole in #1325 that any job is able to leverage execute-as-user to impersonate any unix account. when we tryied rolling out this fix to Reportal server, we run into an exception for all ReportalPig jobs:
The cause is that the job process is not able to create a file under the same source script folder, because of the change (#1325).
In this PR, I used the most straightforward solution to create the bak file under the root working directory.
|
4/7/2018 12:36:16 AM
3.46.0
should be able to use a custom job log format such as GMT timestamps
|
