[jira] [Created] (ATLAS-2068) Update atlas website about 0.8.1 release

2017-08-18 Thread Sarath Subramanian (JIRA)
Sarath Subramanian created ATLAS-2068:
-

 Summary: Update atlas website about 0.8.1 release
 Key: ATLAS-2068
 URL: https://issues.apache.org/jira/browse/ATLAS-2068
 Project: Atlas
  Issue Type: Sub-task
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
 Fix For: 0.8.1-incubating






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (ATLAS-2067) Publish release artifacts

2017-08-18 Thread Sarath Subramanian (JIRA)
Sarath Subramanian created ATLAS-2067:
-

 Summary: Publish release artifacts
 Key: ATLAS-2067
 URL: https://issues.apache.org/jira/browse/ATLAS-2067
 Project: Atlas
  Issue Type: Sub-task
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
 Fix For: 0.8.1-incubating






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (ATLAS-2065) Release Atlas 0.8.1

2017-08-18 Thread Sarath Subramanian (JIRA)
Sarath Subramanian created ATLAS-2065:
-

 Summary: Release Atlas 0.8.1
 Key: ATLAS-2065
 URL: https://issues.apache.org/jira/browse/ATLAS-2065
 Project: Atlas
  Issue Type: Task
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
 Fix For: 0.8.1-incubating






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Build failed in Jenkins: Atlas-master-UnitTests #22

2017-08-18 Thread Apache Jenkins Server
See 


Changes:

[ssubramanian] ATLAS-2062: Add flag to disable v1 gremlin search API using

[madhan] ATLAS-2061: fixed basic-search handling of enum attributes in filter

--
[...truncated 479.46 KB...]
at sun.nio.ch.Net.bind(Net.java:455)
at 
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:67)
at 
org.apache.zookeeper.server.NIOServerCnxnFactory.configure(NIOServerCnxnFactory.java:95)
at 
org.apache.zookeeper.server.ServerCnxnFactory.createFactory(ServerCnxnFactory.java:126)
at 
org.apache.atlas.kafka.KafkaNotification.startZk(KafkaNotification.java:303)
at 
org.apache.atlas.kafka.KafkaNotification.start(KafkaNotification.java:152)
... 75 more
[WARNING] FAILED ServerConnector@28e1573b{HTTP/1.1}{0.0.0.0:31000}: 
java.net.BindException: Address already in use
java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:463)
at sun.nio.ch.Net.bind(Net.java:455)
at 
sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at 
org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:321)
at 
org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at 
org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:236)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at 
org.eclipse.jetty.maven.plugin.MavenServerConnector.doStart(MavenServerConnector.java:120)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at org.eclipse.jetty.server.Server.doStart(Server.java:366)
at 
org.eclipse.jetty.maven.plugin.JettyServer.doStart(JettyServer.java:73)
at 
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
at 
org.eclipse.jetty.maven.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:534)
at 
org.eclipse.jetty.maven.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:357)
at 
org.eclipse.jetty.maven.plugin.JettyRunWarMojo.execute(JettyRunWarMojo.java:64)
at 
org.eclipse.jetty.maven.plugin.JettyDeployWar.execute(JettyDeployWar.java:67)
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[WARNING] FAILED org.eclipse.jetty.maven.plugin.MavenServerConnector@2a991303: 
java.net.BindException: Address already in use
java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:463)
at sun.nio.ch.Net.bind(Net.java:455)
at 

Build failed in Jenkins: Atlas-master-IntegrationTests #21

2017-08-18 Thread Apache Jenkins Server
See 


Changes:

[ssubramanian] ATLAS-2062: Add flag to disable v1 gremlin search API using

[madhan] ATLAS-2061: fixed basic-search handling of enum attributes in filter

--
[...truncated 664.12 KB...]
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "GET 
/api/atlas/v2/types/typedef/name/class_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "GET 
/api/atlas/v2/types/typedef/name/secure_trait HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "GET 
/api/atlas/v2/types/typedef/name/pii_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "GET 
/api/atlas/v2/types/typedef/name/ssn_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "GET 
/api/atlas/v2/types/typedef/name/salary_trait HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "GET 
/api/atlas/v2/types/typedef/name/sox_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "GET /api/atlas/types?type=TRAIT 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "GET 
/api/atlas/v2/types/typedef/name/AYoltlBZtxx HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "GET 
/api/atlas/v2/types/typedef/name/A1YuKUImFQX7 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:55 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:56 +] "GET 
/api/atlas/v2/types/typedef/name/BrK8aw9ZIT9 HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:56 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:56 +] "GET 
/api/atlas/v2/types/typedef/name/CwLrzBaqQr5 HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:56 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:56 +] "GET 
/api/atlas/types?type=CLASS=AYoltlBZtxx=BrK8aw9ZIT9 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:56 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:56 +] "PUT /api/atlas/types HTTP/1.1" 200 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:47:56 +] "GET /api/atlas/types/UOQApidYw2 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:00 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:01 +] "GET /api/atlas/types HTTP/1.1" 200 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:01 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:01 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:01 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:01 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:01 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:01 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:01 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:01 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:01 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:01 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:01 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:01 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:01 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:02 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:48:02 +] "POST /api/atlas/entities 

[jira] [Resolved] (ATLAS-2061) Regression : Entity,Tag filter fetches empty results when applied on an enum attribute.

2017-08-18 Thread Madhan Neethiraj (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Madhan Neethiraj resolved ATLAS-2061.
-
   Resolution: Fixed
Fix Version/s: 0.8.1-incubating
   0.9-incubating

Committed to the following branches:
 - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/ce8f65c9
 - 0.8-incubating: http://git-wip-us.apache.org/repos/asf/atlas/commit/acdcb7df

> Regression : Entity,Tag filter fetches empty results when applied on an enum 
> attribute.
> ---
>
> Key: ATLAS-2061
> URL: https://issues.apache.org/jira/browse/ATLAS-2061
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Blocker
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: 
> 0001-ATLAS-2061-Entity-Tag-filter-fetches-empty-results-w.patch
>
>
> 1.Created a tag with an attribute fileAction of type file_action.
> 2.Associated the tag to an entity with fileAction value "EXECUTE"
> 3.Fired a basic query with classification =  and tag filter : 
> fileAction = EXECUTE.  The entity was not fetched.
> No results are fetched with "!=" operator too on values other than EXECUTE 
> like WRITE , READ etc.,
> Hence , enum filtering is not fetching results. 
> This is a regression , as few commits back,  enum filtering was working as 
> expected.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Build failed in Jenkins: Atlas-0.8-IntegrationTests #16

2017-08-18 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS-2018: UI: Attribute filter does not preserve state

--
[...truncated 655.02 KB...]
127.0.0.1 - - [19/Aug/2017:00:02:15 +] "GET 
/api/atlas/v2/types/typedef/name/classification HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:15 +] "GET 
/api/atlas/v2/types/typedef/name/pii HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:15 +] "GET 
/api/atlas/v2/types/typedef/name/phi HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:15 +] "GET 
/api/atlas/v2/types/typedef/name/pci HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:15 +] "GET 
/api/atlas/v2/types/typedef/name/sox HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:15 +] "GET 
/api/atlas/v2/types/typedef/name/sec HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:15 +] "GET 
/api/atlas/v2/types/typedef/name/finance HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:15 +] "GET 
/api/atlas/v2/types/typedef/name/FactpN9wDwpmsx HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:15 +] "GET 
/api/atlas/v2/types/typedef/name/ETLAh90nCCGTb HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:15 +] "GET 
/api/atlas/v2/types/typedef/name/DimensionB6ISY8LtUa HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:15 +] "GET 
/api/atlas/v2/types/typedef/name/Metricg115Qvrv4B HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:15 +] "GET 
/api/atlas/v2/types/typedef/name/hive_db_v1 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:15 +] "GET 
/api/atlas/v2/types/typedef/name/hive_column_v1 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:15 +] "GET 
/api/atlas/v2/types/typedef/name/hive_table_v1 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:15 +] "GET 
/api/atlas/v2/types/typedef/name/hive_process_v1 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:15 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:16 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:16 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:16 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:16 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:16 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:17 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:17 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:17 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:17 +] "GET 
/api/atlas/lineage/hive/table/sales_fact_monthly_mvnRzbJoTa6K/inputs/graph 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:19 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_facti7bGprnHn3
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:19 +] "GET 
/api/atlas/lineage/37eebe71-fc1d-440d-83b0-07aab81fe459/outputs/graph HTTP/1.1" 
200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:20 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_factKjYzQoOIFA
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:20 +] "GET 
/api/atlas/v2/lineage/3cc51844-f208-4a87-a929-40b98b531f2d?direction=OUTPUT=5
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:21 +] "GET 
/api/atlas/lineage/hive/table/blah/schema HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:21 +] "GET 
/api/atlas/lineage/hive/table/sales_facti7bGprnHn3/outputs/graph HTTP/1.1" 200 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:23 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_fact_monthly_mvnRzbJoTa6K
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:23 +] "GET 
/api/atlas/lineage/ecf3fbe5-2a35-478e-bfac-0f43d61b102c/inputs/graph HTTP/1.1" 
200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:24 +] "GET 
/api/atlas/lineage/hive/table/SalesYk3x0KsJSO/schema HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:24 +] "GET 
/api/atlas/entities?type=hive_table_v1=qualifiedName=sales_facti7bGprnHn3
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [19/Aug/2017:00:02:24 +] "GET 
/api/atlas/lineage/37eebe71-fc1d-440d-83b0-07aab81fe459/schema HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"

Build failed in Jenkins: Atlas-master-IntegrationTests #20

2017-08-18 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS-2018: UI: Attribute filter does not preserve state

--
[...truncated 662.56 KB...]
127.0.0.1 - - [18/Aug/2017:23:57:19 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:19 +] "GET 
/api/atlas/v2/types/typedef/name/ssn_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:19 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:19 +] "GET 
/api/atlas/v2/types/typedef/name/salary_trait HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:19 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:19 +] "GET 
/api/atlas/v2/types/typedef/name/sox_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:19 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:19 +] "GET /api/atlas/types?type=TRAIT 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:19 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:20 +] "PUT /api/atlas/types HTTP/1.1" 200 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:20 +] "GET /api/atlas/types/HcXdYHAM4Q 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:20 +] "GET 
/api/atlas/v2/types/typedef/name/ABl5T6sfG8h HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:20 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:20 +] "GET 
/api/atlas/v2/types/typedef/name/A1uim3j1olbP HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:20 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:20 +] "GET 
/api/atlas/v2/types/typedef/name/BC68VODJAea HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:20 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:20 +] "GET 
/api/atlas/v2/types/typedef/name/CnzGhjRD0bj HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:20 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:20 +] "GET 
/api/atlas/types?type=CLASS=ABl5T6sfG8h=BC68VODJAea 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:20 +] "GET /api/atlas/types/blah HTTP/1.1" 
404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/tableType HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/serdeType HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/classification HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/pii HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/phi HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/pci HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/sox HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/sec HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/finance HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/FactQRcVpIHvKQ HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/ETLwPnzsDBEHs HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/DimensionhdsjmH5emQ HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/MetricBsJXHDQtuy HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/hive_db_v1 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/hive_column_v1 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/hive_table_v1 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "GET 
/api/atlas/v2/types/typedef/name/hive_process_v1 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:23:57:26 

[jira] [Commented] (ATLAS-2062) Add flag to disable v1 gremlin search API using atlas-application property

2017-08-18 Thread Sarath Subramanian (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133794#comment-16133794
 ] 

Sarath Subramanian commented on ATLAS-2062:
---

Committed to: 
0.8-incubating: http://git-wip-us.apache.org/repos/asf/atlas/commit/caf89a30
master: http://git-wip-us.apache.org/repos/asf/atlas/commit/2c84d702


> Add flag to disable v1 gremlin search API using atlas-application property
> --
>
> Key: ATLAS-2062
> URL: https://issues.apache.org/jira/browse/ATLAS-2062
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 0.8-incubating, 0.9-incubating
>
> Attachments: ATLAS-2062.1.patch
>
>
> Add *atlas.search.gremlin.enable* property in atlas-application.properties to 
> disable gremlin search API.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Re: Review Request 61764: ATLAS-2061: Entity, Tag filter fetches empty results when applied on an enum attribute.

2017-08-18 Thread Madhan Neethiraj

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61764/#review183282
---


Ship it!




Ship It!

- Madhan Neethiraj


On Aug. 18, 2017, 11:26 p.m., Apoorv Naik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61764/
> ---
> 
> (Updated Aug. 18, 2017, 11:26 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Sarath Subramanian.
> 
> 
> Bugs: ATLAS-2061
> https://issues.apache.org/jira/browse/ATLAS-2061
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Entity,Tag filter fetches empty results when applied on an enum attribute.
> 
> 
> Diffs
> -
> 
>   repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 
> 15564fc0 
> 
> 
> Diff: https://reviews.apache.org/r/61764/diff/1/
> 
> 
> Testing
> ---
> 
> UI and REST tests give correct results
> 
> 
> Thanks,
> 
> Apoorv Naik
> 
>



[jira] [Assigned] (ATLAS-2061) Regression : Entity,Tag filter fetches empty results when applied on an enum attribute.

2017-08-18 Thread Apoorv Naik (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Apoorv Naik reassigned ATLAS-2061:
--

Assignee: Apoorv Naik

> Regression : Entity,Tag filter fetches empty results when applied on an enum 
> attribute.
> ---
>
> Key: ATLAS-2061
> URL: https://issues.apache.org/jira/browse/ATLAS-2061
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Assignee: Apoorv Naik
>Priority: Blocker
> Attachments: 
> 0001-ATLAS-2061-Entity-Tag-filter-fetches-empty-results-w.patch
>
>
> 1.Created a tag with an attribute fileAction of type file_action.
> 2.Associated the tag to an entity with fileAction value "EXECUTE"
> 3.Fired a basic query with classification =  and tag filter : 
> fileAction = EXECUTE.  The entity was not fetched.
> No results are fetched with "!=" operator too on values other than EXECUTE 
> like WRITE , READ etc.,
> Hence , enum filtering is not fetching results. 
> This is a regression , as few commits back,  enum filtering was working as 
> expected.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Review Request 61764: ATLAS-2061: Entity, Tag filter fetches empty results when applied on an enum attribute.

2017-08-18 Thread Apoorv Naik

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61764/
---

Review request for atlas, Madhan Neethiraj and Sarath Subramanian.


Bugs: ATLAS-2061
https://issues.apache.org/jira/browse/ATLAS-2061


Repository: atlas


Description
---

Entity,Tag filter fetches empty results when applied on an enum attribute.


Diffs
-

  repository/src/main/java/org/apache/atlas/discovery/SearchProcessor.java 
15564fc0 


Diff: https://reviews.apache.org/r/61764/diff/1/


Testing
---

UI and REST tests give correct results


Thanks,

Apoorv Naik



[jira] [Updated] (ATLAS-2061) Regression : Entity,Tag filter fetches empty results when applied on an enum attribute.

2017-08-18 Thread Apoorv Naik (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Apoorv Naik updated ATLAS-2061:
---
Attachment: 0001-ATLAS-2061-Entity-Tag-filter-fetches-empty-results-w.patch

> Regression : Entity,Tag filter fetches empty results when applied on an enum 
> attribute.
> ---
>
> Key: ATLAS-2061
> URL: https://issues.apache.org/jira/browse/ATLAS-2061
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sharmadha Sainath
>Priority: Blocker
> Attachments: 
> 0001-ATLAS-2061-Entity-Tag-filter-fetches-empty-results-w.patch
>
>
> 1.Created a tag with an attribute fileAction of type file_action.
> 2.Associated the tag to an entity with fileAction value "EXECUTE"
> 3.Fired a basic query with classification =  and tag filter : 
> fileAction = EXECUTE.  The entity was not fetched.
> No results are fetched with "!=" operator too on values other than EXECUTE 
> like WRITE , READ etc.,
> Hence , enum filtering is not fetching results. 
> This is a regression , as few commits back,  enum filtering was working as 
> expected.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Re: Review Request 61762: [ATLAS-2062]: Add flag to disable v1 gremlin search API using atlas-application property

2017-08-18 Thread Sarath Subramanian

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61762/
---

(Updated Aug. 18, 2017, 4:13 p.m.)


Review request for atlas and Madhan Neethiraj.


Changes
---

injected configuration in constructor.


Bugs: ATLAS-2062
https://issues.apache.org/jira/browse/ATLAS-2062


Repository: atlas


Description
---

Add atlas.search.gremlin.enable property in atlas-application.properties to 
disable gremlin search API.


Diffs (updated)
-

  distro/src/conf/atlas-application.properties 29a4cc17 
  
webapp/src/main/java/org/apache/atlas/web/resources/MetadataDiscoveryResource.java
 d29c8da1 


Diff: https://reviews.apache.org/r/61762/diff/2/

Changes: https://reviews.apache.org/r/61762/diff/1-2/


Testing
---

validated that the gremlin saerch is enabled/disabled by toggling the flag 
atlas.search.gremlin.enable in atlas-application.properties


Thanks,

Sarath Subramanian



Review Request 61761: ATLAS-2064: Compressed Messages Posted by Hooks

2017-08-18 Thread Ashutosh Mestry

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61761/
---

Review request for atlas, Madhan Neethiraj and Nixon Rodrigues.


Bugs: ATLAS-2064
https://issues.apache.org/jira/browse/ATLAS-2064


Repository: atlas


Description
---

**Analysis**
Kafka is not able handle messages generated by Atlas' hooks, as are over 1MB in 
size. Since messages produced are JSON strings, compression will yield huge 
savings.
Compared various compression options. Also referred to this 
[presentation](https://www.slideshare.net/oom65/file-format-benchmarks-avro-json-orc-parquet).
 
**Implementation**
- Extended _AtlasType_ to include methods to compress/decompress JSON.
- Messages now produces are GZIP compressed.
- _VersionedMessgaeSerializer_ now supports very old (no version), old 
(uncompressed) and new (compressed) deserialization.
- Added new _CompressedVersionedMessage_ message type. 
- Modified message structure to add envelope message that holds messages of 
different types.
 
 
**Additional Information**
It is possible to add compression to Kafka message by configuring Kafka 
property: compression.codec=1
See 
[here](https://www.cloudera.com/documentation/kafka/latest/topics/kafka_performance.html#concept_gqw_rcz_yq)
 for details.


Diffs
-

  intg/src/main/java/org/apache/atlas/type/AtlasType.java c99eb7f 
  intg/src/test/java/org/apache/atlas/TestAtlasTypeJSONSerialize.java 
PRE-CREATION 
  
notification/src/main/java/org/apache/atlas/notification/AbstractNotification.java
 cb44fc6 
  
notification/src/main/java/org/apache/atlas/notification/CompressedVersionedMessage.java
 PRE-CREATION 
  notification/src/main/java/org/apache/atlas/notification/MessageVersion.java 
6ef407a 
  
notification/src/main/java/org/apache/atlas/notification/VersionedMessage.java 
1929eb4 
  
notification/src/main/java/org/apache/atlas/notification/VersionedMessageDeserializer.java
 cc2099e 
  
notification/src/test/java/org/apache/atlas/notification/hook/HookNotificationTest.java
 dd3257e 


Diff: https://reviews.apache.org/r/61761/diff/1/


Testing
---

**Unit tests**
- New unit tests added to verify compression and decompression of strings 
across locales.
- Message de-serialization with backward compatibility.

**Functional tests**
- Simulated scenario where Atlas is on newer version and hooks are on older 
(uncompressed) version.
- Updated hive hook and Atlas to new version and verified hive hook 
functionality for Atlas.


Thanks,

Ashutosh Mestry



Re: Review Request 61762: [ATLAS-2062]: Add flag to disable v1 gremlin search API using atlas-application property

2017-08-18 Thread Apoorv Naik

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61762/#review183275
---


Fix it, then Ship it!





webapp/src/main/java/org/apache/atlas/web/resources/MetadataDiscoveryResource.java
Line 76 (original), 83 (patched)


Inject configuration here instead.


- Apoorv Naik


On Aug. 18, 2017, 11:01 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61762/
> ---
> 
> (Updated Aug. 18, 2017, 11:01 p.m.)
> 
> 
> Review request for atlas and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-2062
> https://issues.apache.org/jira/browse/ATLAS-2062
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Add atlas.search.gremlin.enable property in atlas-application.properties to 
> disable gremlin search API.
> 
> 
> Diffs
> -
> 
>   distro/src/conf/atlas-application.properties 29a4cc17 
>   
> webapp/src/main/java/org/apache/atlas/web/resources/MetadataDiscoveryResource.java
>  d29c8da1 
> 
> 
> Diff: https://reviews.apache.org/r/61762/diff/1/
> 
> 
> Testing
> ---
> 
> validated that the gremlin saerch is enabled/disabled by toggling the flag 
> atlas.search.gremlin.enable in atlas-application.properties
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>



[jira] [Updated] (ATLAS-2062) Add flag to disable v1 gremlin search API using atlas-application property

2017-08-18 Thread Sarath Subramanian (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sarath Subramanian updated ATLAS-2062:
--
Attachment: ATLAS-2062.1.patch

> Add flag to disable v1 gremlin search API using atlas-application property
> --
>
> Key: ATLAS-2062
> URL: https://issues.apache.org/jira/browse/ATLAS-2062
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating, 0.9-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
>Priority: Minor
> Fix For: 0.8-incubating, 0.9-incubating
>
> Attachments: ATLAS-2062.1.patch
>
>
> Add *atlas.search.gremlin.enable* property in atlas-application.properties to 
> disable gremlin search API.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2064) Compress Hook Messages Posted to Kafka

2017-08-18 Thread Ashutosh Mestry (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashutosh Mestry updated ATLAS-2064:
---
Summary: Compress Hook Messages Posted to Kafka  (was: Compressed HiveHook 
Messages)

> Compress Hook Messages Posted to Kafka
> --
>
> Key: ATLAS-2064
> URL: https://issues.apache.org/jira/browse/ATLAS-2064
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
> Fix For: trunk
>
> Attachments: ATLAS-2064-compressed-hook-message-envelope.patch
>
>
> *Background*
> Messages posted by hooks to Atlas Kafka topics are JSON format. 
> Kafka imposes a 1MB limit on the message size.
> Occasionally, depending on operations performed, this threshold is reached. 
> This results in messages being dropped.
> The entities are thus not reflected in Atlas.
> *Solution*
> Applying compression to these message will alleviate the problem.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2064) Compress Hook Messages Posted to Kafka Atlas Topic

2017-08-18 Thread Ashutosh Mestry (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashutosh Mestry updated ATLAS-2064:
---
Summary: Compress Hook Messages Posted to Kafka Atlas Topic  (was: Compress 
Hook Messages Posted to Kafka)

> Compress Hook Messages Posted to Kafka Atlas Topic
> --
>
> Key: ATLAS-2064
> URL: https://issues.apache.org/jira/browse/ATLAS-2064
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
> Fix For: trunk
>
> Attachments: ATLAS-2064-compressed-hook-message-envelope.patch
>
>
> *Background*
> Messages posted by hooks to Atlas Kafka topics are JSON format. 
> Kafka imposes a 1MB limit on the message size.
> Occasionally, depending on operations performed, this threshold is reached. 
> This results in messages being dropped.
> The entities are thus not reflected in Atlas.
> *Solution*
> Applying compression to these message will alleviate the problem.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2064) Compressed HiveHook Messages

2017-08-18 Thread Ashutosh Mestry (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ashutosh Mestry updated ATLAS-2064:
---
Attachment: ATLAS-2064-compressed-hook-message-envelope.patch

> Compressed HiveHook Messages
> 
>
> Key: ATLAS-2064
> URL: https://issues.apache.org/jira/browse/ATLAS-2064
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-intg
>Affects Versions: 0.8-incubating
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
> Fix For: trunk
>
> Attachments: ATLAS-2064-compressed-hook-message-envelope.patch
>
>
> *Background*
> Messages posted by hooks to Atlas Kafka topics are JSON format. 
> Kafka imposes a 1MB limit on the message size.
> Occasionally, depending on operations performed, this threshold is reached. 
> This results in messages being dropped.
> The entities are thus not reflected in Atlas.
> *Solution*
> Applying compression to these message will alleviate the problem.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (ATLAS-2064) Compressed HiveHook Messages

2017-08-18 Thread Ashutosh Mestry (JIRA)
Ashutosh Mestry created ATLAS-2064:
--

 Summary: Compressed HiveHook Messages
 Key: ATLAS-2064
 URL: https://issues.apache.org/jira/browse/ATLAS-2064
 Project: Atlas
  Issue Type: Improvement
  Components: atlas-intg
Affects Versions: 0.8-incubating
Reporter: Ashutosh Mestry
Assignee: Ashutosh Mestry
 Fix For: trunk


*Background*
Messages posted by hooks to Atlas Kafka topics are JSON format. 

Kafka imposes a 1MB limit on the message size.

Occasionally, depending on operations performed, this threshold is reached. 
This results in messages being dropped.

The entities are thus not reflected in Atlas.

*Solution*
Applying compression to these message will alleviate the problem.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (ATLAS-2063) Compressed HiveHook Messages

2017-08-18 Thread Ashutosh Mestry (JIRA)
Ashutosh Mestry created ATLAS-2063:
--

 Summary: Compressed HiveHook Messages
 Key: ATLAS-2063
 URL: https://issues.apache.org/jira/browse/ATLAS-2063
 Project: Atlas
  Issue Type: Improvement
  Components: atlas-intg
Affects Versions: 0.8-incubating
Reporter: Ashutosh Mestry
Assignee: Ashutosh Mestry
 Fix For: trunk


*Background*
Messages posted by hooks to Atlas Kafka topics are JSON format. 

Kafka imposes a 1MB limit on the message size.

Occasionally, depending on operations performed, this threshold is reached. 
This results in messages being dropped.

The entities are thus not reflected in Atlas.

*Solution*
Applying compression to these message will alleviate the problem.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (ATLAS-2062) Add flag to disable v1 gremlin search API using atlas-application property

2017-08-18 Thread Sarath Subramanian (JIRA)
Sarath Subramanian created ATLAS-2062:
-

 Summary: Add flag to disable v1 gremlin search API using 
atlas-application property
 Key: ATLAS-2062
 URL: https://issues.apache.org/jira/browse/ATLAS-2062
 Project: Atlas
  Issue Type: Improvement
  Components:  atlas-core
Affects Versions: 0.8-incubating, 0.9-incubating
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
Priority: Minor
 Fix For: 0.9-incubating, 0.8-incubating


Add *atlas.search.gremlin.enable* property in atlas-application.properties to 
disable gremlin search API.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (ATLAS-2018) UI: Attribute filter will not preserving state

2017-08-18 Thread Madhan Neethiraj (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133683#comment-16133683
 ] 

Madhan Neethiraj commented on ATLAS-2018:
-

+1 for the patch. Thanks [~kevalbhatt].

> UI: Attribute filter will not preserving state
> --
>
> Key: ATLAS-2018
> URL: https://issues.apache.org/jira/browse/ATLAS-2018
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.8-incubating, 0.9-incubating
>
> Attachments: ATLAS-2018.patch
>
>
> Steps to reproduce.
> # Click on the filter button to open filter pop-up.
> # Select an attribute and apply the condition.
> # Click on the apply button.
> # Now Click on Filter button again it won't show previously applied filter.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (ATLAS-2061) Regression : Entity,Tag filter fetches empty results when applied on an enum attribute.

2017-08-18 Thread Sharmadha Sainath (JIRA)
Sharmadha Sainath created ATLAS-2061:


 Summary: Regression : Entity,Tag filter fetches empty results when 
applied on an enum attribute.
 Key: ATLAS-2061
 URL: https://issues.apache.org/jira/browse/ATLAS-2061
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Priority: Blocker


1.Created a tag with an attribute fileAction of type file_action.
2.Associated the tag to an entity with fileAction value "EXECUTE"
3.Fired a basic query with classification =  and tag filter : 
fileAction = EXECUTE.  The entity was not fetched.
No results are fetched with "!=" operator too on values other than EXECUTE like 
WRITE , READ etc.,

Hence , enum filtering is not fetching results. 
This is a regression , as few commits back,  enum filtering was working as 
expected.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2060) Fix logger class name typos

2017-08-18 Thread Richard Ding (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Ding updated ATLAS-2060:

Attachment: ATLAS-2060.patch

> Fix logger class name typos
> ---
>
> Key: ATLAS-2060
> URL: https://issues.apache.org/jira/browse/ATLAS-2060
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 0.8-incubating
>Reporter: Richard Ding
>Assignee: Richard Ding
>Priority: Trivial
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-2060.patch
>
>
> There are two classes in intg module that have incorrect logger class names.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (ATLAS-2060) Fix logger class name typos

2017-08-18 Thread Richard Ding (JIRA)
Richard Ding created ATLAS-2060:
---

 Summary: Fix logger class name typos
 Key: ATLAS-2060
 URL: https://issues.apache.org/jira/browse/ATLAS-2060
 Project: Atlas
  Issue Type: Bug
  Components: atlas-intg
Affects Versions: 0.8-incubating
Reporter: Richard Ding
Assignee: Richard Ding
Priority: Trivial
 Fix For: 0.9-incubating


There are two classes in intg module that have incorrect logger class names.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Build failed in Jenkins: Atlas-0.8-IntegrationTests #15

2017-08-18 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS-2056: removed unused library references

[ssubramanian] ATLAS-2059: Update test-patch.sh script for PreCommit-ATLAS-Build

--
[...truncated 668.53 KB...]
127.0.0.1 - - [18/Aug/2017:19:41:41 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:42 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:42 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:42 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:42 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:42 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:42 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:42 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:42 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:42 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:42 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:43 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:43 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:43 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:43 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:43 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:43 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:43 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:43 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:43 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:44 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:44 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:44 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:44 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:44 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:44 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:44 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:44 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:44 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:45 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:45 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:45 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:41:45 +] "GET 
/api/atlas/entities/11cbfe39-2039-4003-a279-6890ba68fa2b 

Build failed in Jenkins: Atlas-master-IntegrationTests #19

2017-08-18 Thread Apache Jenkins Server
See 


Changes:

[ssubramanian] ATLAS-2059: Update test-patch.sh script for PreCommit-ATLAS-Build

--
[...truncated 664.58 KB...]
127.0.0.1 - - [18/Aug/2017:19:39:40 +] "PUT /api/atlas/v2/types/typedefs/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:40 +] "GET 
/api/atlas/v2/types/typedefs/?type=ENTITY HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:40 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:40 +] "POST /api/atlas/types HTTP/1.1" 409 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:40 +] "GET /api/atlas/types/blah HTTP/1.1" 
404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:40 +] "GET 
/api/atlas/v2/types/typedef/name/class_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:40 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:40 +] "GET 
/api/atlas/v2/types/typedef/name/secure_trait HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:40 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:40 +] "GET 
/api/atlas/v2/types/typedef/name/pii_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:40 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:40 +] "GET 
/api/atlas/v2/types/typedef/name/ssn_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:40 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:41 +] "GET 
/api/atlas/v2/types/typedef/name/salary_trait HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:41 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:41 +] "GET 
/api/atlas/v2/types/typedef/name/sox_trait HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:41 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:41 +] "GET /api/atlas/types?type=TRAIT 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:41 +] "GET 
/api/atlas/v2/types/typedef/name/ASfeWwTgDtE HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:41 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:41 +] "GET 
/api/atlas/v2/types/typedef/name/A1T0xqlmdpg8 HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:41 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:41 +] "GET 
/api/atlas/v2/types/typedef/name/Bd6wzsnDCKG HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:41 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:41 +] "GET 
/api/atlas/v2/types/typedef/name/CT6CkH4Kut9 HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:41 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:41 +] "GET 
/api/atlas/types?type=CLASS=ASfeWwTgDtE=Bd6wzsnDCKG 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:41 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:41 +] "PUT /api/atlas/types HTTP/1.1" 200 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:42 +] "GET /api/atlas/types/FWxqhZwC4F 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:54 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:55 +] "GET /api/atlas/types HTTP/1.1" 200 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:55 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:55 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:55 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:55 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:55 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:55 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:55 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:55 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:55 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [18/Aug/2017:19:39:55 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - 

Re: Review Request 61747: [ATLAS-2059]: Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job

2017-08-18 Thread Apoorv Naik

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61747/#review183254
---


Ship it!




Ship It!

- Apoorv Naik


On Aug. 18, 2017, 6:11 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61747/
> ---
> 
> (Updated Aug. 18, 2017, 6:11 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-2059
> https://issues.apache.org/jira/browse/ATLAS-2059
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job and fix for 
> one failed IT
> 
> 
> Diffs
> -
> 
>   dev-support/test-patch.sh 9e63575d 
>   webapp/src/test/java/org/apache/atlas/examples/QuickStartV2IT.java 773a514d 
>   webapp/src/test/java/org/apache/atlas/web/integration/BaseResourceIT.java 
> 496185fe 
>   
> webapp/src/test/java/org/apache/atlas/web/integration/EntityJerseyResourceIT.java
>  b527583a 
> 
> 
> Diff: https://reviews.apache.org/r/61747/diff/1/
> 
> 
> Testing
> ---
> 
> validated in jenkins test job - 
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/
> 
> We can test patches using jenkins job (Build with parameters) using:
> * Review Board ID
> * JIRA ID
> * Local Atlas Patch
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>



[jira] [Commented] (ATLAS-2059) Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job

2017-08-18 Thread Sarath Subramanian (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133445#comment-16133445
 ] 

Sarath Subramanian commented on ATLAS-2059:
---

Committed to:
master: http://git-wip-us.apache.org/repos/asf/atlas/commit/86fb9da4
0.8-incubating:  http://git-wip-us.apache.org/repos/asf/atlas/commit/e14485b5

> Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job
> -
>
> Key: ATLAS-2059
> URL: https://issues.apache.org/jira/browse/ATLAS-2059
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 0.8-incubating, 0.9-incubating
>
> Attachments: ATLAS-2059.1.patch
>
>
> Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job and fix for 
> one failed IT
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/
> We can test patches using jenkins job (Build with parameters) using:
> * Review Board ID  
> * JIRA ID
> * Local Atlas Patch



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Re: Review Request 61747: [ATLAS-2059]: Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job

2017-08-18 Thread Madhan Neethiraj

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61747/#review183245
---


Ship it!




Ship It!

- Madhan Neethiraj


On Aug. 18, 2017, 6:11 p.m., Sarath Subramanian wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61747/
> ---
> 
> (Updated Aug. 18, 2017, 6:11 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik and Madhan Neethiraj.
> 
> 
> Bugs: ATLAS-2059
> https://issues.apache.org/jira/browse/ATLAS-2059
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job and fix for 
> one failed IT
> 
> 
> Diffs
> -
> 
>   dev-support/test-patch.sh 9e63575d 
>   webapp/src/test/java/org/apache/atlas/examples/QuickStartV2IT.java 773a514d 
>   webapp/src/test/java/org/apache/atlas/web/integration/BaseResourceIT.java 
> 496185fe 
>   
> webapp/src/test/java/org/apache/atlas/web/integration/EntityJerseyResourceIT.java
>  b527583a 
> 
> 
> Diff: https://reviews.apache.org/r/61747/diff/1/
> 
> 
> Testing
> ---
> 
> validated in jenkins test job - 
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/
> 
> We can test patches using jenkins job (Build with parameters) using:
> * Review Board ID
> * JIRA ID
> * Local Atlas Patch
> 
> 
> Thanks,
> 
> Sarath Subramanian
> 
>



[jira] [Updated] (ATLAS-2059) Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job

2017-08-18 Thread Sarath Subramanian (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sarath Subramanian updated ATLAS-2059:
--
Description: 
Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job and fix for 
one failed IT

We can test patches using jenkins job (Build with parameters) using:
* Review Board ID  
* JIRA ID
* Local Atlas Patch

  was:Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job and fix 
for one failed IT


> Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job
> -
>
> Key: ATLAS-2059
> URL: https://issues.apache.org/jira/browse/ATLAS-2059
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-2059.1.patch
>
>
> Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job and fix for 
> one failed IT
> We can test patches using jenkins job (Build with parameters) using:
> * Review Board ID  
> * JIRA ID
> * Local Atlas Patch



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2059) Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job

2017-08-18 Thread Sarath Subramanian (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sarath Subramanian updated ATLAS-2059:
--
Description: 
Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job and fix for 
one failed IT

https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/

We can test patches using jenkins job (Build with parameters) using:
* Review Board ID  
* JIRA ID
* Local Atlas Patch

  was:
Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job and fix for 
one failed IT

We can test patches using jenkins job (Build with parameters) using:
* Review Board ID  
* JIRA ID
* Local Atlas Patch


> Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job
> -
>
> Key: ATLAS-2059
> URL: https://issues.apache.org/jira/browse/ATLAS-2059
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-2059.1.patch
>
>
> Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job and fix for 
> one failed IT
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/
> We can test patches using jenkins job (Build with parameters) using:
> * Review Board ID  
> * JIRA ID
> * Local Atlas Patch



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Review Request 61747: [ATLAS-2059]: Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job

2017-08-18 Thread Sarath Subramanian

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61747/
---

Review request for atlas, Apoorv Naik and Madhan Neethiraj.


Bugs: ATLAS-2059
https://issues.apache.org/jira/browse/ATLAS-2059


Repository: atlas


Description
---

Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job and fix for 
one failed IT


Diffs
-

  dev-support/test-patch.sh 9e63575d 
  webapp/src/test/java/org/apache/atlas/examples/QuickStartV2IT.java 773a514d 
  webapp/src/test/java/org/apache/atlas/web/integration/BaseResourceIT.java 
496185fe 
  
webapp/src/test/java/org/apache/atlas/web/integration/EntityJerseyResourceIT.java
 b527583a 


Diff: https://reviews.apache.org/r/61747/diff/1/


Testing
---

validated in jenkins test job - 
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/

We can test patches using jenkins job (Build with parameters) using:
* Review Board ID
* JIRA ID
* Local Atlas Patch


Thanks,

Sarath Subramanian



[jira] [Updated] (ATLAS-2059) Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job

2017-08-18 Thread Sarath Subramanian (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sarath Subramanian updated ATLAS-2059:
--
Attachment: ATLAS-2059.1.patch

> Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job
> -
>
> Key: ATLAS-2059
> URL: https://issues.apache.org/jira/browse/ATLAS-2059
> Project: Atlas
>  Issue Type: New Feature
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>Reporter: Sarath Subramanian
>Assignee: Sarath Subramanian
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-2059.1.patch
>
>
> Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job and fix for 
> one failed IT



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (ATLAS-2059) Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job

2017-08-18 Thread Sarath Subramanian (JIRA)
Sarath Subramanian created ATLAS-2059:
-

 Summary: Update test-patch.sh script for PreCommit-ATLAS-Build 
jenkins job
 Key: ATLAS-2059
 URL: https://issues.apache.org/jira/browse/ATLAS-2059
 Project: Atlas
  Issue Type: New Feature
  Components:  atlas-core
Affects Versions: 0.9-incubating
Reporter: Sarath Subramanian
Assignee: Sarath Subramanian
 Fix For: 0.9-incubating


Update test-patch.sh script for PreCommit-ATLAS-Build jenkins job and fix for 
one failed IT



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Jenkins build is back to normal : Atlas-0.8-UnitTests #17

2017-08-18 Thread Apache Jenkins Server
See 



Re: Review Request 61736: ATLAS-2049 Document common standards for OMAS interfaces

2017-08-18 Thread David Radley

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61736/#review183222
---




docs/src/site/twiki/OMAS-Standards.twiki
Lines 9 (patched)


I would not be this blunt. All of the existing applicaiton use the entity 
API. Instead, I suggest saying something like, 
" the OMAS APIs are access APIs that are not chatty and should be ideally 
tailors for consumers to access Atlas. As such we are looking to encourage 
Atlas application to move away from the lower level APIs and use the OMAS API 
instead.



docs/src/site/twiki/OMAS-Standards.twiki
Lines 12 (patched)


I think you need to explain what OMRS and OMRS connectors are).



docs/src/site/twiki/OMAS-Standards.twiki
Lines 16 (patched)


When you say "transforming, mapping data from Atlas/OMRS as required" - I 
suggest saying the OMAS implmentation will call the lower level resource 
specific APIs. I suggest not mentioning that the OMAS call Atlas - it calls 
OMRS which could be Atlas behind it.



docs/src/site/twiki/OMAS-Standards.twiki
Lines 20 (patched)


what do you mean by "some duplication is expected"?



docs/src/site/twiki/OMAS-Standards.twiki
Lines 22 (patched)


I think of the interface as the API - maybe we should say the implmnetaion 
of the OMAS interface or something like that.



docs/src/site/twiki/OMAS-Standards.twiki
Lines 26 (patched)


You talk of OMAS interfaces and OMAS interface. Is there one or many. Do we 
require separate OMAS build for each OMAS?



docs/src/site/twiki/OMAS-Standards.twiki
Lines 42 (patched)


you refer to the connector OMAS. In this context how would I find that? Do 
you actually mean the asset OMAS to the connector framework?



docs/src/site/twiki/OMAS-Standards.twiki
Lines 46 (patched)


tab



docs/src/site/twiki/OMAS-Standards.twiki
Lines 50 (patched)


you mention Atlas here - when it might not be Atlas



docs/src/site/twiki/OMAS-Standards.twiki
Lines 135 (patched)


tab



docs/src/site/twiki/index.twiki
Lines 61 (patched)


Might be less ambiguous to remove Atlas from the title.


- David Radley


On Aug. 18, 2017, 2:55 p.m., Nigel Jones wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61736/
> ---
> 
> (Updated Aug. 18, 2017, 2:55 p.m.)
> 
> 
> Review request for atlas.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2049 Document common standards for OMAS interfaces
> 
> As we start to build OMAS interfaces it seems having some common standards 
> would be a good idea. I wanted to get this discussion going so opted to 
> document this in twiki format & submit via review board. The intent isn't 
> this first pass is correct, but that we come to a consensus ...
> 
> Open to suggestions as to whether this is a useful approach - Alternatives 
> include
>  - Simply posting on wiki - but I think we want to keep that for more 
> consumer style documentation that's been agreed
>  - Posting as a word doc or similar within the JIRA
> 
> See more info in the JIRA(s)
> 
> -- Nigel.
> 
> 
> Diffs
> -
> 
>   docs/src/site/twiki/OMAS-Standards.twiki PRE-CREATION 
>   docs/src/site/twiki/index.twiki a8e7de9fb74bca0548eda5f5832e1e2bff3f7aec 
> 
> 
> Diff: https://reviews.apache.org/r/61736/diff/1/
> 
> 
> Testing
> ---
> 
> * Rebuilt twiki documentation to validate formatting, and reviewed in Safari.
> 
> 
> Thanks,
> 
> Nigel Jones
> 
>



Review Request 61736: ATLAS-2049 Document common standards for OMAS interfaces

2017-08-18 Thread Nigel Jones

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61736/
---

Review request for atlas.


Repository: atlas


Description
---

ATLAS-2049 Document common standards for OMAS interfaces

As we start to build OMAS interfaces it seems having some common standards 
would be a good idea. I wanted to get this discussion going so opted to 
document this in twiki format & submit via review board. The intent isn't this 
first pass is correct, but that we come to a consensus ...

Open to suggestions as to whether this is a useful approach - Alternatives 
include
 - Simply posting on wiki - but I think we want to keep that for more consumer 
style documentation that's been agreed
 - Posting as a word doc or similar within the JIRA

See more info in the JIRA(s)

-- Nigel.


Diffs
-

  docs/src/site/twiki/OMAS-Standards.twiki PRE-CREATION 
  docs/src/site/twiki/index.twiki a8e7de9fb74bca0548eda5f5832e1e2bff3f7aec 


Diff: https://reviews.apache.org/r/61736/diff/1/


Testing
---

* Rebuilt twiki documentation to validate formatting, and reviewed in Safari.


Thanks,

Nigel Jones



[jira] [Comment Edited] (ATLAS-1836) Area 0 of the open metadata model

2017-08-18 Thread David Radley (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16132991#comment-16132991
 ] 

David Radley edited comment on ATLAS-1836 at 8/18/17 1:59 PM:
--

added patch ATLAS-1836-1 : 
- removed 2 infrastructure supertypes I had added
- changed all attributes to optional and not to be indexed
- added descriptions to all the entities where we have the text readily 
available  
- fixed a couple of glitches I noticed 
- added 0017 model 


was (Author: davidrad):
This latest patch: 
- removed 2 infrastructure supertypes I had added
- changed all attributes to optional and not to be indexed
- added descriptions to all the entities where we have the text readily 
available  
- fixed a couple of glitches I noticed 

> Area 0 of the open metadata model
> -
>
> Key: ATLAS-1836
> URL: https://issues.apache.org/jira/browse/ATLAS-1836
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
> Attachments: ATLAS-1836-1.patch, ATLAS-1836.patch
>
>
> This task delivers the JSON files for the new models that describe types for 
> Area 0 in the open metadata model.  This area covers base types.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Comment Edited] (ATLAS-1836) Area 0 of the open metadata model

2017-08-18 Thread David Radley (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16132991#comment-16132991
 ] 

David Radley edited comment on ATLAS-1836 at 8/18/17 1:57 PM:
--

This latest patch: 
- removed 2 infrastructure supertypes I had added
- changed all attributes to optional and not to be indexed
- added descriptions to all the entities where we have the text readily 
available  
- fixed a couple of glitches I noticed 


was (Author: davidrad):
This latest patch: 
- 2 infrastructure supertypes I had added
- changes all attributes to optional and not to be indexed
- added descriptions to all the entities where we have the text readily 
available  
- fixed a couple of glitches I noticed 

> Area 0 of the open metadata model
> -
>
> Key: ATLAS-1836
> URL: https://issues.apache.org/jira/browse/ATLAS-1836
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
> Attachments: ATLAS-1836-1.patch, ATLAS-1836.patch
>
>
> This task delivers the JSON files for the new models that describe types for 
> Area 0 in the open metadata model.  This area covers base types.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-1836) Area 0 of the open metadata model

2017-08-18 Thread David Radley (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Radley updated ATLAS-1836:

Attachment: ATLAS-1836-1.patch

This latest patch: 
- 2 infrastructure supertypes I had added
- changes all attributes to optional and not to be indexed
- added descriptions to all the entities where we have the text readily 
available  
- fixed a couple of glitches I noticed 

> Area 0 of the open metadata model
> -
>
> Key: ATLAS-1836
> URL: https://issues.apache.org/jira/browse/ATLAS-1836
> Project: Atlas
>  Issue Type: Task
>  Components:  atlas-core
>Reporter: Mandy Chessell
>Assignee: David Radley
>  Labels: OpenMetadata, VirtualDataConnector
> Attachments: ATLAS-1836-1.patch, ATLAS-1836.patch
>
>
> This task delivers the JSON files for the new models that describe types for 
> Area 0 in the open metadata model.  This area covers base types.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Re: Review Request 61688: ATLAS-1836 Add Area 0 models

2017-08-18 Thread David Radley

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/61688/
---

(Updated Aug. 18, 2017, 1:53 p.m.)


Review request for atlas, Madhan Neethiraj and Mandy Chessell.


Repository: atlas


Description
---

ATLAS-1836 Add Area 0 models

Note that these models will change:
- add in model 0017
- to add additional restrictions to the ClassificationDefs to restrict them to 
a set of named entityTypes (Jira 2029)
- to add more specific attributeDef types - for example image (Jira 1955)


Diffs (updated)
-

  addons/models/0015-LinkedMediaTypes_model.json PRE-CREATION 
  addons/models/0017-ExternalIdentifiers_model.json PRE-CREATION 
  addons/models/0020-PropertyFacets_model.json PRE-CREATION 
  addons/models/0025-Locations_model.json PRE-CREATION 
  addons/models/0030-HostsAndPlatforms_model.json PRE-CREATION 
  addons/models/0035-ComplexHosts_model.json PRE-CREATION 
  addons/models/0040-Servers_model.json PRE-CREATION 
  addons/models/0070-NetworksAndGateways_model.json PRE-CREATION 
  addons/models/0090-CloudPlatformsAndServices.json PRE-CREATION 


Diff: https://reviews.apache.org/r/61688/diff/4/

Changes: https://reviews.apache.org/r/61688/diff/3-4/


Testing
---

Run junits
Start Atlas - check logs there are no errors.
Query the typeDefs to check they exist.


Thanks,

David Radley



[jira] [Updated] (ATLAS-2018) UI: Attribute filter will not preserving state

2017-08-18 Thread Keval Bhatt (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keval Bhatt updated ATLAS-2018:
---
Fix Version/s: 0.8-incubating
   0.9-incubating

> UI: Attribute filter will not preserving state
> --
>
> Key: ATLAS-2018
> URL: https://issues.apache.org/jira/browse/ATLAS-2018
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.8-incubating, 0.9-incubating
>
> Attachments: ATLAS-2018.patch
>
>
> Steps to reproduce.
> # Click on the filter button to open filter pop-up.
> # Select an attribute and apply the condition.
> # Click on the apply button.
> # Now Click on Filter button again it won't show previously applied filter.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2018) UI: Attribute filter will not preserving state

2017-08-18 Thread Keval Bhatt (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keval Bhatt updated ATLAS-2018:
---
Attachment: ATLAS-2018.patch

> UI: Attribute filter will not preserving state
> --
>
> Key: ATLAS-2018
> URL: https://issues.apache.org/jira/browse/ATLAS-2018
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.8-incubating, 0.9-incubating
>
> Attachments: ATLAS-2018.patch
>
>
> Steps to reproduce.
> # Click on the filter button to open filter pop-up.
> # Select an attribute and apply the condition.
> # Click on the apply button.
> # Now Click on Filter button again it won't show previously applied filter.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Commented] (ATLAS-1993) UI : show list of Tables in detail page if entity type is hive_db

2017-08-18 Thread Keval Bhatt (JIRA)

[ 
https://issues.apache.org/jira/browse/ATLAS-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16132126#comment-16132126
 ] 

Keval Bhatt commented on ATLAS-1993:


Committed to master http://git-wip-us.apache.org/repos/asf/atlas/commit/b23dc858

> UI : show list of Tables in detail page if entity type is hive_db
> -
>
> Key: ATLAS-1993
> URL: https://issues.apache.org/jira/browse/ATLAS-1993
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1993.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-1993) UI : show list of Tables in detail page if entity type is hive_db

2017-08-18 Thread Keval Bhatt (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keval Bhatt updated ATLAS-1993:
---
Fix Version/s: 0.9-incubating

> UI : show list of Tables in detail page if entity type is hive_db
> -
>
> Key: ATLAS-1993
> URL: https://issues.apache.org/jira/browse/ATLAS-1993
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-1993.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2038) Integration Test cases for AtlasAuthentication and Authorization Filter

2017-08-18 Thread Nixon Rodrigues (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nixon Rodrigues updated ATLAS-2038:
---
Attachment: ATLAS-2038.2.patch

In [^ATLAS-2038.2.patch] removed base64 API which was deprecated,
[~ashutoshm], Thanks for review comment and please review the patch.


> Integration Test cases for AtlasAuthentication and Authorization Filter
> ---
>
> Key: ATLAS-2038
> URL: https://issues.apache.org/jira/browse/ATLAS-2038
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.8-incubating
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
> Fix For: 0.9-incubating, 0.8.1-incubating
>
> Attachments: ATLAS-2038.2.patch, ATLAS-2038.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2049) Document common standards for OMAS interfaces

2017-08-18 Thread Nigel Jones (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nigel Jones updated ATLAS-2049:
---
Attachment: ATLAS_2049_Document_common_standards_for_OMAS_interfaces3.patch

> Document common standards for OMAS interfaces
> -
>
> Key: ATLAS-2049
> URL: https://issues.apache.org/jira/browse/ATLAS-2049
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Nigel Jones
>Assignee: Nigel Jones
> Attachments: 
> ATLAS_2049_Document_common_standards_for_OMAS_interfaces1.patch, 
> ATLAS_2049_Document_common_standards_for_OMAS_interfaces21.patch, 
> ATLAS_2049_Document_common_standards_for_OMAS_interfaces3.patch, 
> ATLAS_2049_Document_common_standards_for_OMAS_interfaces.patch
>
>
> Document (and review) common standards for OMAS interfaces, so as to ensure 
> some consistency between the multiple OMASs being developed.
> As per phone discussion with some of team on 15 Aug will create this list in 
> a text-like format (perhaps twiki) and review using review board tool.
> Since this will then form documentation for ATlas (internal) developers it 
> may make sense to create as a permanent part of the twiki docs, though if so 
> we may wish to consider adding other related information there such as 
> architectural explanations of omrs, omas etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Updated] (ATLAS-2058) Add a description to every element that appears in TypeDefs

2017-08-18 Thread David Radley (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Radley updated ATLAS-2058:

Description: 
It would be very useful to have a desciption for every element that appears in 
the TypeDef. 

This will be useful as we can document the meaning of each of each of the top 
level defs. In the new top level types we are adding (e.g. in Jira 1836) we can 
define exactly the intent of each entity, relationship, classification, 
attribute and enum value. TypeDefs thjemselves already have descriptions.

We may need to think about restricting or escaping some characters that might 
interfere with the json. At the description will be a quoted string, we may be 
able to get away with supporting all characters apart from quotes.   

Ideally we would support markup and embedded images. Short term I propose we 
consider tolerating markup if it is easy to implement and look at embedded 
images longer term.  


  was:
It would be very useful to have a desciption for every element that appears in 
the TypeDef. 

This will be useful as we can document the meaning of each of each of the top 
level defs. In the new top level types we are adding (e.g. in Jira 1836) we can 
define exactly the intent of each entity, relationship, classification, 
attribute and enum value.

We may need to think about restricting or escaping some characters that might 
interfere with the json. At the description will be a quoted string, we may be 
able to get away with supporting all characters apart from quotes.   

Ideally we would support markup and embedded images. Short term I propose we 
consider tolerating markup if it is easy to implement and look at embedded 
images longer term.  



> Add a description to every element that appears in TypeDefs 
> 
>
> Key: ATLAS-2058
> URL: https://issues.apache.org/jira/browse/ATLAS-2058
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Radley
>Assignee: David Radley
>
> It would be very useful to have a desciption for every element that appears 
> in the TypeDef. 
> This will be useful as we can document the meaning of each of each of the top 
> level defs. In the new top level types we are adding (e.g. in Jira 1836) we 
> can define exactly the intent of each entity, relationship, classification, 
> attribute and enum value. TypeDefs thjemselves already have descriptions.
> We may need to think about restricting or escaping some characters that might 
> interfere with the json. At the description will be a quoted string, we may 
> be able to get away with supporting all characters apart from quotes.   
> Ideally we would support markup and embedded images. Short term I propose we 
> consider tolerating markup if it is easy to implement and look at embedded 
> images longer term.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


Re: [DISCUSS] Atlas models

2017-08-18 Thread David Radley
I made a mistake in the namings (thanks Mandy for pointing this out) :  
0100Area1-connectors should be  0100Area1-assets. I have corrected below

On 2017-08-18 10:30, "David Radley" wrote: 
> I am adding new models that will be part of Atlas by default. These models 
> are grouped as different areas of metadata. Rather than add over 100 files in 
> the models folder, I propose that we have subfolders of Area0-base, 
> 0100Area1-assets, 0200Area2-glossary etc and a 1000Hadoop folder for the 
> older models. Each folder will have a patches subfolder where the models can 
> be overridden.
> 
> I propose the load order will be to load in number order, based on the prefix 
> of the folders then numerically on the files within the folder. By convention 
> the folder prefix will match the file prefixes along the lines of my 
> suggested names.   
> 
> This structure sets us up nicely to be add in models to specify a standard we 
> need Atlas to be aware of - for example we could have a GDPR folder and files 
> to introduce classifications that match the GDPR standard. 
> 
> If this is what we want - I will look to add it as part of ATLAS-1836.
> 
>
> 


[DISCUSS] Atlas models

2017-08-18 Thread David Radley
I am adding new models that will be part of Atlas by default. These models are 
grouped as different areas of metadata. Rather than add over 100 files in the 
models folder, I propose that we have subfolders of Area0-base, 
0100Area1-connectors, 0200Area2-glossary etc and a 1000Hadoop folder for the 
older models. Each folder will have a patches subfolder where the models can be 
overridden.

I propose the load order will be to load in number order, based on the prefix 
of the folders then numerically on the files within the folder. By convention 
the folder prefix will match the file prefixes along the lines of my suggested 
names.   

This structure sets us up nicely to be add in models to specify a standard we 
need Atlas to be aware of - for example we could have a GDPR folder and files 
to introduce classifications that match the GDPR standard. 

If this is what we want - I will look to add it as part of ATLAS-1836.

   


[jira] [Updated] (ATLAS-2058) Add a description to every element that appears in TypeDefs

2017-08-18 Thread David Radley (JIRA)

 [ 
https://issues.apache.org/jira/browse/ATLAS-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Radley updated ATLAS-2058:

Description: 
It would be very useful to have a desciption for every element that appears in 
the TypeDef. 

This will be useful as we can document the meaning of each of each of the top 
level defs. In the new top level types we are adding (e.g. in Jira 1836) we can 
define exactly the intent of each entity, relationship, classification, 
attribute and enum value.

We may need to think about restricting or escaping some characters that might 
interfere with the json. At the description will be a quoted string, we may be 
able to get away with supporting all characters apart from quotes.   

Ideally we would support markup and embedded images. Short term I propose we 
consider tolerating markup if it is easy to implement and look at embedded 
images longer term.  


  was:
It would be very useful to have a desciption for every element that appears in 
the TypeDef. 

This will be useful as we can document the meaning of each of each of the top 
level defs. In the new top level types we are adding (e.g. in Jira 1836) we can 
define exactly the intent of each entity, relationship, classification, 
attribute and enum value.

We may need to think about restricting or escaping some characters that might 
interfere with the json. At the description will be a quoted string, we may be 
able to get away with supporting all characters apart from quotes.   



> Add a description to every element that appears in TypeDefs 
> 
>
> Key: ATLAS-2058
> URL: https://issues.apache.org/jira/browse/ATLAS-2058
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Radley
>Assignee: David Radley
>
> It would be very useful to have a desciption for every element that appears 
> in the TypeDef. 
> This will be useful as we can document the meaning of each of each of the top 
> level defs. In the new top level types we are adding (e.g. in Jira 1836) we 
> can define exactly the intent of each entity, relationship, classification, 
> attribute and enum value.
> We may need to think about restricting or escaping some characters that might 
> interfere with the json. At the description will be a quoted string, we may 
> be able to get away with supporting all characters apart from quotes.   
> Ideally we would support markup and embedded images. Short term I propose we 
> consider tolerating markup if it is easy to implement and look at embedded 
> images longer term.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (ATLAS-2058) Add a description to every element that appears in TypeDefs

2017-08-18 Thread David Radley (JIRA)
David Radley created ATLAS-2058:
---

 Summary: Add a description to every element that appears in 
TypeDefs 
 Key: ATLAS-2058
 URL: https://issues.apache.org/jira/browse/ATLAS-2058
 Project: Atlas
  Issue Type: Improvement
Reporter: David Radley
Assignee: David Radley


It would be very useful to have a desciption for every element that appears in 
the TypeDef. 

This will be useful as we can document the meaning of each of each of the top 
level defs. In the new top level types we are adding (e.g. in Jira 1836) we can 
define exactly the intent of each entity, relationship, classification, 
attribute and enum value.

We may need to think about restricting or escaping some characters that might 
interfere with the json. At the description will be a quoted string, we may be 
able to get away with supporting all characters apart from quotes.   




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)


[jira] [Created] (ATLAS-2057) Attributes filter does not show the attribute and value if the value of that attribute is null

2017-08-18 Thread Sharmadha Sainath (JIRA)
Sharmadha Sainath created ATLAS-2057:


 Summary: Attributes filter does not show the attribute and value 
if the value of that attribute is null
 Key: ATLAS-2057
 URL: https://issues.apache.org/jira/browse/ATLAS-2057
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath


1.Created a hive_table.
2. Few attributes like aliases , partitionKeys , viewOriginalText , 
viewExpandedText , description had null values.
3. Fired a basic query with following POST body :
{code}
{
"entityFilters":null
"tagFilters":null,
"attributes":["viewExpandedText","comment","retention","aliases"],
"query":null,
"excludeDeletedEntities":true,
"limit":25,
"typeName":"hive_table",
"classification":null   
}
{code}

Following is the response :
{code}
{
"queryType": "BASIC",
"searchParameters": {
"typeName": "hive_table",
"excludeDeletedEntities": true,
"limit": 25,
"offset": 0,
"entityFilters":null,
"attributes": [
"viewExpandedText",
"aliases",
"comment",
"retention"
]
},
"entities": [
{
"typeName": "hive_table",
"attributes": {
"owner": "hrt_qa",
"qualifiedName": "db_h189c6z0eu.table_12_h189c6z0eu@cl1",
"name": "table_12_h189c6z0eu",
"description": null,
"retention": 0
},
"guid": "c1a1362d-75f8-42a9-8ad8-3792ecc75018",
"status": "ACTIVE",
"displayText": "table_12_h189c6z0eu",
"classificationNames": []
}
]
}
{code}

In the "attributes" key value , only retention is seen because it has non-null 
value. Other null valued attributes are ignored. 

If response has 2 entities and the second hive_table entity has non-null values 
for aliases , partitionKeys , viewOriginalText , viewExpandedText , the 
attribute along with non-null value is fetched in the response. It can be 
confusing as why for one hive_table entity few attributes are not retrieved. 

It is fine from the UI since the attribute name is shown and the value is empty 
for null valued attributes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)