[jira] [Commented] (ATLAS-181) Integrate storm topology metadata into Atlas

[ https://issues.apache.org/jira/browse/ATLAS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15057715#comment-15057715 ] Hemanth Yamijala commented on ATLAS-181: We would be better off changing the doc for the storm.yaml

[jira] [Commented] (ATLAS-181) Integrate storm topology metadata into Atlas

[ https://issues.apache.org/jira/browse/ATLAS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15058008#comment-15058008 ] Hemanth Yamijala commented on ATLAS-181: More comments: * In the documentation, we must ask users

[jira] [Commented] (ATLAS-181) Integrate storm topology metadata into Atlas

[ https://issues.apache.org/jira/browse/ATLAS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15059290#comment-15059290 ] Hemanth Yamijala commented on ATLAS-181: bq. I guess this is yaml format. They can refer to storm

[jira] [Commented] (ATLAS-183) Add a Hook in Storm to post the topology metadata

[ https://issues.apache.org/jira/browse/ATLAS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15059287#comment-15059287 ] Hemanth Yamijala commented on ATLAS-183: bq. Please read the accompanying docs for clarity

[jira] [Commented] (ATLAS-183) Add a Hook in Storm to post the topology metadata

[ https://issues.apache.org/jira/browse/ATLAS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15059293#comment-15059293 ] Hemanth Yamijala commented on ATLAS-183: In the above comment, the atlas related deps can have

[jira] [Created] (ATLAS-387) Running quick_start without a valid atlas endpoint in configuration or argument prints a spurious success message.

Hemanth Yamijala created ATLAS-387: -- Summary: Running quick_start without a valid atlas endpoint in configuration or argument prints a spurious success message. Key: ATLAS-387 URL: https://issues.apache.org/jira

[jira] [Updated] (ATLAS-385) Support for Lineage for entities with SuperType as DataSet

[ https://issues.apache.org/jira/browse/ATLAS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-385: --- Attachment: sample_graph_api_output.txt feed_enhancements.txt I extended

[jira] [Updated] (ATLAS-374) Doc: Create a wiki for documenting fault tolerance and HA options for Atlas data

[ https://issues.apache.org/jira/browse/ATLAS-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-374: --- Attachment: ATLAS-374.patch Attached patch makes the proposed changes. * Moved architecture

[jira] [Updated] (ATLAS-346) Atlas server loses messages sent from Hive hook if restarted after unclean shutdown

[ https://issues.apache.org/jira/browse/ATLAS-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-346: --- Attachment: ATLAS-346.patch This patch upgrades the version of Jersey to the latest in 1.x

[jira] [Commented] (ATLAS-244) UI: Add Tag Tab

[ https://issues.apache.org/jira/browse/ATLAS-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052507#comment-15052507 ] Hemanth Yamijala commented on ATLAS-244: Tested the patch. * Created tags with more than one

[jira] [Commented] (ATLAS-346) Atlas server loses messages sent from Hive hook if restarted after unclean shutdown

[ https://issues.apache.org/jira/browse/ATLAS-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15052702#comment-15052702 ] Hemanth Yamijala commented on ATLAS-346: A couple of things to call out for review: * I have

[jira] [Updated] (ATLAS-385) Support for Lineage for entities with SuperType as DataSet

[ https://issues.apache.org/jira/browse/ATLAS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-385: --- Attachment: lineage.png Did another CTAS on table t4 and it shows the transforms from t2 to t4

[jira] [Updated] (ATLAS-374) Doc: Create a wiki for documenting fault tolerance and HA options for Atlas data

[ https://issues.apache.org/jira/browse/ATLAS-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-374: --- Attachment: ATLAS-374.patch The attached patch documents options for providing high

[jira] [Updated] (ATLAS-374) Doc: Create a wiki for documenting fault tolerance and HA options for Atlas data

[ https://issues.apache.org/jira/browse/ATLAS-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-374: --- Attachment: ATLAS-374.patch A few minor modifications to align the terminology with what we're

[jira] [Created] (ATLAS-383) hive-import seems broken in Atlas trunk and 0.6 release candidate.

Hemanth Yamijala created ATLAS-383: -- Summary: hive-import seems broken in Atlas trunk and 0.6 release candidate. Key: ATLAS-383 URL: https://issues.apache.org/jira/browse/ATLAS-383 Project: Atlas

[jira] [Updated] (ATLAS-383) hive-import seems broken in Atlas trunk and 0.6 release candidate.

[ https://issues.apache.org/jira/browse/ATLAS-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-383: --- Attachment: hive_import_rc_bug.txt Server side stack trace from application.log > hive-imp

Re: [VOTE] Release Apache Atlas version 0.6.0-incubating (Release Candidate 1)

Hi, I tried to validate the release. While I don't see the compile errors, I do see hive-import failing for me. This is occurring on trunk as well. This could be an environment issue, but I suspect some recent changes could be the cause as well. I filed

[jira] [Resolved] (ATLAS-239) UI: Tag screen should make it possible to specify parent tag

[ https://issues.apache.org/jira/browse/ATLAS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-239. Resolution: Fixed This is fixed as part of ATLAS-279. Verified that we can created tag

[jira] [Resolved] (ATLAS-268) Performance - UI : Search page, TRAIT service call to be called once

[ https://issues.apache.org/jira/browse/ATLAS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-268. Resolution: Fixed This is fixed as part of ATLAS-279. Verified that we make a types?type

[jira] [Created] (ATLAS-375) Improve the way we manage the display of 'Schema' information in the entity details view

Hemanth Yamijala created ATLAS-375: -- Summary: Improve the way we manage the display of 'Schema' information in the entity details view Key: ATLAS-375 URL: https://issues.apache.org/jira/browse/ATLAS-375

[jira] [Created] (ATLAS-376) UI: Use the Schema API of the backend to populate details for Schema tab

Hemanth Yamijala created ATLAS-376: -- Summary: UI: Use the Schema API of the backend to populate details for Schema tab Key: ATLAS-376 URL: https://issues.apache.org/jira/browse/ATLAS-376 Project

[jira] [Updated] (ATLAS-376) UI: Use the Schema API of the backend to populate details for Schema tab

[ https://issues.apache.org/jira/browse/ATLAS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-376: --- Attachment: schema_response.json Attaching the sample response for the schema API. > UI:

[jira] [Created] (ATLAS-377) API: Return all super types of an entity

Hemanth Yamijala created ATLAS-377: -- Summary: API: Return all super types of an entity Key: ATLAS-377 URL: https://issues.apache.org/jira/browse/ATLAS-377 Project: Atlas Issue Type: Sub

[jira] [Updated] (ATLAS-376) UI: Use the Schema API of the backend to populate details for Schema tab

[ https://issues.apache.org/jira/browse/ATLAS-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-376: --- Issue Type: Sub-task (was: Task) Parent: ATLAS-375 > UI: Use the Schema

[jira] [Created] (ATLAS-378) UI: Suppress the call to Schema API if entity is not a DataSet.

Hemanth Yamijala created ATLAS-378: -- Summary: UI: Suppress the call to Schema API if entity is not a DataSet. Key: ATLAS-378 URL: https://issues.apache.org/jira/browse/ATLAS-378 Project: Atlas

[jira] [Commented] (ATLAS-354) Kerberized cluster: quick_start.py fails to add sample data

[ https://issues.apache.org/jira/browse/ATLAS-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15046463#comment-15046463 ] Hemanth Yamijala commented on ATLAS-354: Lgtm. +1 > Kerberized cluster: quick_start.py fa

[jira] [Commented] (ATLAS-279) UI not displaying results for certain successful "select" search queries

[ https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15044960#comment-15044960 ] Hemanth Yamijala commented on ATLAS-279: Verified new patch and all issues reported above are fixed

[jira] [Commented] (ATLAS-345) UI: Should allow tag addition on any search result that returns a reference-able entity

[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15046343#comment-15046343 ] Hemanth Yamijala commented on ATLAS-345: Tested the above patch after applying ATLAS-279

[jira] [Assigned] (ATLAS-346) Atlas server loses messages sent from Hive hook if restarted after unclean shutdown

[ https://issues.apache.org/jira/browse/ATLAS-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala reassigned ATLAS-346: -- Assignee: Hemanth Yamijala > Atlas server loses messages sent from Hive h

[jira] [Created] (ATLAS-374) Doc: Create a wiki for documenting fault tolerance and HA options for Atlas data

Hemanth Yamijala created ATLAS-374: -- Summary: Doc: Create a wiki for documenting fault tolerance and HA options for Atlas data Key: ATLAS-374 URL: https://issues.apache.org/jira/browse/ATLAS-374

[jira] [Reopened] (ATLAS-268) Performance - UI : Search page, TRAIT service call to be called once

[ https://issues.apache.org/jira/browse/ATLAS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala reopened ATLAS-268: This is not yet fixed as ATLAS-279 is not completed. > Performance - UI : Search page, TR

[jira] [Commented] (ATLAS-279) UI not displaying results for certain successful "select" search queries

[ https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15043880#comment-15043880 ] Hemanth Yamijala commented on ATLAS-279: Hi, I took this patch for a run. Found couple of important

[jira] [Updated] (ATLAS-279) UI not displaying results for certain successful "select" search queries

[ https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-279: --- Attachment: tag_addition_missing_attr_name_bug.txt

[jira] [Updated] (ATLAS-279) UI not displaying results for certain successful "select" search queries

[ https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-279: --- Attachment: tag_association_missing_child_attrs.png > UI not displaying results for cert

[jira] [Reopened] (ATLAS-239) UI: Tag screen should make it possible to specify parent tag

[ https://issues.apache.org/jira/browse/ATLAS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala reopened ATLAS-239: Not yet closed, as ATLAS-279 is not committed. > UI: Tag screen should make it possi

[jira] [Reopened] (ATLAS-264) UI: As part of trait/tag creation, POST response(201 created) is enough to say the request is successful. Extra http GET call can be removed.

[ https://issues.apache.org/jira/browse/ATLAS-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala reopened ATLAS-264: Not yet done, as ATLAS-279 is not committed. > UI: As part of trait/tag creation, POST respo

[jira] [Updated] (ATLAS-337) Hive import fails upon re-run if Atlas Server was restarted after abnormal termination

[ https://issues.apache.org/jira/browse/ATLAS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-337: --- Assignee: Suma Shivaprasad > Hive import fails upon re-run if Atlas Server was restarted af

[jira] [Resolved] (ATLAS-337) Hive import fails upon re-run if Atlas Server was restarted after abnormal termination

[ https://issues.apache.org/jira/browse/ATLAS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-337. Resolution: Fixed Tested this on a cluster with Atlas trunk having ATLAS-352 that removes

[jira] [Commented] (ATLAS-345) UI: Should allow tag addition on any search result that returns a reference-able entity

[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037374#comment-15037374 ] Hemanth Yamijala commented on ATLAS-345: Anil, in the backend, we are going to try and ensure

[jira] [Updated] (ATLAS-345) UI: Should allow tag addition on any search result that returns a reference-able entity

[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-345: --- Attachment: hive_storagedesc_results.png > UI: Should allow tag addition on any search res

[jira] [Updated] (ATLAS-345) UI: Should allow tag addition on any search result that returns a reference-able entity

[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-345: --- Attachment: hive_storagedesc_results_json.txt This is the JSON that is returned for the query

[jira] [Commented] (ATLAS-345) UI: Should allow tag addition on any search result that returns a reference-able entity

[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15035356#comment-15035356 ] Hemanth Yamijala commented on ATLAS-345: Hi, I applied this patch and did a quick check. Tested

[jira] [Reopened] (ATLAS-345) UI: Should allow tag addition on any search result that returns a reference-able entity

[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala reopened ATLAS-345: Reopening this, and will mark it blocked by ATLAS-279 as described in earlier comments. >

[jira] [Created] (ATLAS-347) Atlas search APIs should allow pagination of results

Hemanth Yamijala created ATLAS-347: -- Summary: Atlas search APIs should allow pagination of results Key: ATLAS-347 URL: https://issues.apache.org/jira/browse/ATLAS-347 Project: Atlas Issue

[jira] [Created] (ATLAS-345) UI: Should allow tag addition on any search result that returns an entity

Hemanth Yamijala created ATLAS-345: -- Summary: UI: Should allow tag addition on any search result that returns an entity Key: ATLAS-345 URL: https://issues.apache.org/jira/browse/ATLAS-345 Project

Re: Problem in Adding Trait

Hi Rishabh, Thanks for reporting this and providing the correction. We will look into this and update it. Thanks Hemanth On Sat, Nov 28, 2015 at 12:32 AM, Rishabh Bhardwaj wrote: > Figured it out. > The api endpoint should be 'entities' instead of 'entity'. > > Docs here

[jira] [Commented] (ATLAS-339) UI: Improve the flow for associating tags to entities

[ https://issues.apache.org/jira/browse/ATLAS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033057#comment-15033057 ] Hemanth Yamijala commented on ATLAS-339: Here is a proposal for concrete changes that I feel

[jira] [Commented] (ATLAS-345) UI: Should allow tag addition on any search result that returns an entity

[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033069#comment-15033069 ] Hemanth Yamijala commented on ATLAS-345: Here's the JSON response for the query hive_column where

[jira] [Updated] (ATLAS-345) UI: Should allow tag addition on any search result that returns a reference-able entity

[ https://issues.apache.org/jira/browse/ATLAS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-345: --- Summary: UI: Should allow tag addition on any search result that returns a reference-able

[jira] [Created] (ATLAS-346) Atlas server loses messages sent from Hive hook if restarted after unclean shutdown

Hemanth Yamijala created ATLAS-346: -- Summary: Atlas server loses messages sent from Hive hook if restarted after unclean shutdown Key: ATLAS-346 URL: https://issues.apache.org/jira/browse/ATLAS-346

[jira] [Updated] (ATLAS-346) Atlas server loses messages sent from Hive hook if restarted after unclean shutdown

[ https://issues.apache.org/jira/browse/ATLAS-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-346: --- Attachment: hive_server2_import_bug_snip.txt Attached relevant portion of failure

[jira] [Commented] (ATLAS-343) Search not behaving correctly for specific DSL query of form where =''

[ https://issues.apache.org/jira/browse/ATLAS-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15031690#comment-15031690 ] Hemanth Yamijala commented on ATLAS-343: After bit of digging around, it appears this issue

[jira] [Created] (ATLAS-340) Doc: Hive configuration directory is incorrectly documented for Hive Bridge

Hemanth Yamijala created ATLAS-340: -- Summary: Doc: Hive configuration directory is incorrectly documented for Hive Bridge Key: ATLAS-340 URL: https://issues.apache.org/jira/browse/ATLAS-340 Project

[jira] [Updated] (ATLAS-343) Search not behaving correctly for specific DSL query of form where =''

[ https://issues.apache.org/jira/browse/ATLAS-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-343: --- Attachment: hive-dsl-failute.txt > Search not behaving correctly for specific DSL qu

[jira] [Created] (ATLAS-341) Doc: Fault tolerant configurations for Atlas backing stores

Hemanth Yamijala created ATLAS-341: -- Summary: Doc: Fault tolerant configurations for Atlas backing stores Key: ATLAS-341 URL: https://issues.apache.org/jira/browse/ATLAS-341 Project: Atlas

[jira] [Commented] (ATLAS-343) Search not behaving correctly for specific DSL query of form where =''

[ https://issues.apache.org/jira/browse/ATLAS-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15031359#comment-15031359 ] Hemanth Yamijala commented on ATLAS-343: Relevant portion of log attached. > Search not behav

[jira] [Commented] (ATLAS-343) Search not behaving correctly for specific DSL query of form where =''

[ https://issues.apache.org/jira/browse/ATLAS-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15031389#comment-15031389 ] Hemanth Yamijala commented on ATLAS-343: Some quick observations: * This is happening for every

[jira] [Created] (ATLAS-343) Search not behaving correctly for specific DSL query of form where =''

Hemanth Yamijala created ATLAS-343: -- Summary: Search not behaving correctly for specific DSL query of form where ='' Key: ATLAS-343 URL: https://issues.apache.org/jira/browse/ATLAS-343 Project

[jira] [Commented] (ATLAS-339) UI: Improve the flow for associating tags to entities

[ https://issues.apache.org/jira/browse/ATLAS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15029805#comment-15029805 ] Hemanth Yamijala commented on ATLAS-339: Couple of corrections to the previous comment

[jira] [Commented] (ATLAS-337) Hive import fails upon re-run if Atlas Server was restarted after abnormal termination

[ https://issues.apache.org/jira/browse/ATLAS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15029453#comment-15029453 ] Hemanth Yamijala commented on ATLAS-337: As per discussion with [~suma.shivaprasad], this will most

[jira] [Commented] (ATLAS-338) Notifications to Kafka from a new Hive client don't come if Atlas server is down

[ https://issues.apache.org/jira/browse/ATLAS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15029456#comment-15029456 ] Hemanth Yamijala commented on ATLAS-338: As per discussion with [~shwethags], this issue is likely

[jira] [Created] (ATLAS-337) Hive import fails upon re-run if Atlas Server was restarted after abnormal termination

Hemanth Yamijala created ATLAS-337: -- Summary: Hive import fails upon re-run if Atlas Server was restarted after abnormal termination Key: ATLAS-337 URL: https://issues.apache.org/jira/browse/ATLAS-337

[jira] [Created] (ATLAS-339) UI: Improve the flow for associating tags to entities

Hemanth Yamijala created ATLAS-339: -- Summary: UI: Improve the flow for associating tags to entities Key: ATLAS-339 URL: https://issues.apache.org/jira/browse/ATLAS-339 Project: Atlas Issue

[jira] [Commented] (ATLAS-337) Hive import fails upon re-run if Atlas Server was restarted after abnormal termination

[ https://issues.apache.org/jira/browse/ATLAS-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15029452#comment-15029452 ] Hemanth Yamijala commented on ATLAS-337: Exception stack trace: {code} 2015-11-25 19:22:44,322

[jira] [Created] (ATLAS-338) Notifications to Kafka from a new Hive client don't come if Atlas server is down

Hemanth Yamijala created ATLAS-338: -- Summary: Notifications to Kafka from a new Hive client don't come if Atlas server is down Key: ATLAS-338 URL: https://issues.apache.org/jira/browse/ATLAS-338

[jira] [Commented] (ATLAS-220) Gets on Enum attribute should return EnumValue

[ https://issues.apache.org/jira/browse/ATLAS-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15023784#comment-15023784 ] Hemanth Yamijala commented on ATLAS-220: I tried to do this, but couldn't. Can't explain fully

[jira] [Updated] (ATLAS-220) Gets on Enum attribute should return EnumValue

[ https://issues.apache.org/jira/browse/ATLAS-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-220: --- Attachment: ATLAS-220.patch Attached patch adds a test to reproduce the problem and has (I

[jira] [Commented] (ATLAS-220) Gets on Enum attribute should return EnumValue

[ https://issues.apache.org/jira/browse/ATLAS-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15018195#comment-15018195 ] Hemanth Yamijala commented on ATLAS-220: Interestingly, I don't seem to be able to see this through

[jira] [Commented] (ATLAS-274) No lineage is recorded for creating a table using LIKE

[ https://issues.apache.org/jira/browse/ATLAS-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15015466#comment-15015466 ] Hemanth Yamijala commented on ATLAS-274: I am able to replicate this behavior. However, thinking

[jira] [Assigned] (ATLAS-274) No lineage is recorded for creating a table using LIKE

[ https://issues.apache.org/jira/browse/ATLAS-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala reassigned ATLAS-274: -- Assignee: Hemanth Yamijala > No lineage is recorded for creating a table using L

Re: [jira] [Commented] (ATLAS-199) webapp build fails (grunt + tests)

Sonali, ALTAS-159 & ATLAS-199 are merged with the master branch. However, the status of ATLAS-199 is still open, so I assume some work is still pending on it (which might also be why you are still seeing the error). The only release of the project we’ve had is the 0.5 version, and for it I only

Re: [jira] [Commented] (ATLAS-199) webapp build fails (grunt + tests)

It appears you can download the binary bits that come off master from the nightly builds that are published here: https://builds.apache.org/job/apache-atlas-nightly/ - Can you check if this is accessible for you? Thanks Hemanth On Thu, Nov 19, 2015 at 10:18 AM, Hemanth Yamijala <yh

[jira] [Commented] (ATLAS-308) Rename tags to traits through out the application.

[ https://issues.apache.org/jira/browse/ATLAS-308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15008521#comment-15008521 ] Hemanth Yamijala commented on ATLAS-308: >From a product perspective, we have to see whether 't

[jira] [Commented] (ATLAS-311) UI: Local storage for traits - caching [not cleared on refresh] To be cleared on time lapse for 1hr.

[ https://issues.apache.org/jira/browse/ATLAS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15008523#comment-15008523 ] Hemanth Yamijala commented on ATLAS-311: We may need to discuss this a bit. What

[jira] [Updated] (ATLAS-297) KafkaNotificationTest.testSendReceiveMessage fails when atlas-server is running on the same machine

[ https://issues.apache.org/jira/browse/ATLAS-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-297: --- Attachment: ATLAS-297-1.patch Here is a very dumbed down version that addresses the original

[jira] [Commented] (ATLAS-297) KafkaNotificationTest.testSendReceiveMessage fails when atlas-server is running on the same machine

[ https://issues.apache.org/jira/browse/ATLAS-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15003832#comment-15003832 ] Hemanth Yamijala commented on ATLAS-297: I debugged the issue of the failing integration tests

[jira] [Commented] (ATLAS-301) Atlas Distribution module test is failing

[ https://issues.apache.org/jira/browse/ATLAS-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15003575#comment-15003575 ] Hemanth Yamijala commented on ATLAS-301: Seems to be because the actual code has a new classpath

[jira] [Updated] (ATLAS-297) KafkaNotificationTest.testSendReceiveMessage fails when atlas-server is running on the same machine

[ https://issues.apache.org/jira/browse/ATLAS-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-297: --- Attachment: ATLAS-297.patch The attached patch attempts to fix the issue using ephemeral ports

[jira] [Assigned] (ATLAS-297) KafkaNotificationTest.testSendReceiveMessage fails when atlas-server is running on the same machine

[ https://issues.apache.org/jira/browse/ATLAS-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala reassigned ATLAS-297: -- Assignee: Hemanth Yamijala > KafkaNotificationTest.testSendReceiveMessage fails w

[jira] [Created] (ATLAS-297) KafkaNotificationTest.testSendReceiveMessage fails when atlas-server is running on the same machine

Hemanth Yamijala created ATLAS-297: -- Summary: KafkaNotificationTest.testSendReceiveMessage fails when atlas-server is running on the same machine Key: ATLAS-297 URL: https://issues.apache.org/jira/browse/ATLAS

<    4   5   6   7   8   9