[jira] [Updated] (ATLAS-806) Create default taxonomy at server startup

[ https://issues.apache.org/jira/browse/ATLAS-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-806: --- Summary: Create default taxonomy at server startup (was: Business Taxonomy related types

[jira] [Created] (ATLAS-914) CLONE - Business Taxonomy related types should be registered one time on server startup.

Hemanth Yamijala created ATLAS-914: -- Summary: CLONE - Business Taxonomy related types should be registered one time on server startup. Key: ATLAS-914 URL: https://issues.apache.org/jira/browse/ATLAS-914

Re: Review Request 48820: Create default taxonomy if required

", "default"); } catch (Exception e) { LOG... } ``` Basically, the check for taxonomy name null or empty can be avoided using the config.get call with a default value. - Hemanth Yamij

[jira] [Created] (ATLAS-913) Messages sent from hooks could be duplicated in case of partial failures

Hemanth Yamijala created ATLAS-913: -- Summary: Messages sent from hooks could be duplicated in case of partial failures Key: ATLAS-913 URL: https://issues.apache.org/jira/browse/ATLAS-913 Project

[jira] [Commented] (ATLAS-911) Get entity by unique attribute doesn't enforce type

[ https://issues.apache.org/jira/browse/ATLAS-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335453#comment-15335453 ] Hemanth Yamijala commented on ATLAS-911: Changes look ok to me. +1. Please commit if tests

[jira] [Assigned] (ATLAS-912) Update to use Kafka 0.10.0.0 (from 0.9.0.0)

[ https://issues.apache.org/jira/browse/ATLAS-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala reassigned ATLAS-912: -- Assignee: Hemanth Yamijala (was: Madhan Neethiraj) > Update to use Kafka 0.10.

Re: Review Request 48723: ATLAS-901 Log messages that cannot be sent to Kafka to a specific log configuration

- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/48723/#review137984 --- On June 16, 2016, 12:21 p.m., Hemanth Yamijala wrote: > > --

[jira] [Updated] (ATLAS-899) Fix Hive Hook documentation

[ https://issues.apache.org/jira/browse/ATLAS-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-899: --- Attachment: ATLAS-899-1.patch.txt Validated the changes. There were a few fields missing

Re: Review Request 48723: ATLAS-901 Log messages that cannot be sent to Kafka to a specific log configuration

ssages > logging only if the log file location is specified in the configuration - in > a property named like "atlas.hook.notification.failed.messages.filename" > > Hemanth Yamijala wrote: > I have made the log file name configurable. However, a slight change to > your proposal: I did retain the boo

Re: Review Request 48723: ATLAS-901 Log messages that cannot be sent to Kafka to a specific log configuration

t having just one configuration. I will leave the issue open to hear back from you. - Hemanth --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/48723/#review137927 ---

Re: Review Request 48723: ATLAS-901 Log messages that cannot be sent to Kafka to a specific log configuration

for the changes. Thanks, Hemanth Yamijala

[jira] [Updated] (ATLAS-901) Log messages that cannot be sent to Kafka to a specific log configuration

[ https://issues.apache.org/jira/browse/ATLAS-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-901: --- Attachment: ATLAS-901-1.patch Patch addressing review comments on review board from

[jira] [Updated] (ATLAS-762) Assertion in NegativeSSLAndKerberosTest.testUnsecuredClient needs to be hardened

[ https://issues.apache.org/jira/browse/ATLAS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-762: --- Fix Version/s: (was: 0.7-incubating) > Assert

[jira] [Commented] (ATLAS-901) Log messages that cannot be sent to Kafka to a specific log configuration

[ https://issues.apache.org/jira/browse/ATLAS-901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333191#comment-15333191 ] Hemanth Yamijala commented on ATLAS-901: [~madhan.neethiraj], Thanks for looking at the patch. I

[jira] [Commented] (ATLAS-904) Hive hook fails due to session state not being set

[ https://issues.apache.org/jira/browse/ATLAS-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15333127#comment-15333127 ] Hemanth Yamijala commented on ATLAS-904: [~suma.shivaprasad], I don't know the full details

Re: Review Request 48760: ATLAS-908: Force index creation up front

> On June 16, 2016, 12:21 a.m., Hemanth Yamijala wrote: > > I am unable to comment on JIRA because of issues with Apache JIRA instance. > > > > However, from a log of a recently launched one, I see this sequence: > > > > 2016-06-15 22:57:09,910 INFO - [main:]

Re: Review Request 48760: ATLAS-908: Force index creation up front

indexes are indeed created before the Type system is either restored or created for first time. Can you please explain why you think indexes are not created upfront, and which indexes are you referring to? - Hemanth Yamijala On June 15, 2016, 10:35 p.m., Jeff Hagelberg wrote

Re: Atlas and the various "types"

Ernie, All bridges are accepted and certified to the extent that there are tests run against them for ensuring expected behavior. In terms of functionality, the Hive bridge / hook is the most advanced covering a huge list of capabilities (added in the soon to be released 0.7 release). Sqoop,

[jira] [Commented] (ATLAS-762) Assertion in NegativeSSLAndKerberosTest.testUnsecuredClient needs to be hardened

[ https://issues.apache.org/jira/browse/ATLAS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15332202#comment-15332202 ] Hemanth Yamijala commented on ATLAS-762: [~nixonrodrigues] / [~mehul] / [~madhan.neethiraj], can

[jira] [Updated] (ATLAS-890) Log received messages in case of error

[ https://issues.apache.org/jira/browse/ATLAS-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-890: --- Attachment: ATLAS-890-1.patch There were some minor merge conflicts - I rebased the patch

[jira] [Commented] (ATLAS-796) Fulltext search 500 Error

[ https://issues.apache.org/jira/browse/ATLAS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15332091#comment-15332091 ] Hemanth Yamijala commented on ATLAS-796: [~ayubkhan], I moved this out of the 0.7 bucket. Please

[jira] [Updated] (ATLAS-796) Fulltext search 500 Error

[ https://issues.apache.org/jira/browse/ATLAS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-796: --- Fix Version/s: (was: 0.7-incubating) > Fulltext search 500 Er

Review Request 48723: ATLAS-901 Log messages that cannot be sent to Kafka to a specific log configuration

that the message is logged into the log file. Added some UTs for the changes. Thanks, Hemanth Yamijala

[jira] [Updated] (ATLAS-901) Log messages that cannot be sent to Kafka to a specific log configuration

[ https://issues.apache.org/jira/browse/ATLAS-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-901: --- Attachment: ATLAS-901.patch The attached patch attempts to save failed messages to a log file

[jira] [Commented] (ATLAS-859) Sqoop hook can also extend from AtlasHook

[ https://issues.apache.org/jira/browse/ATLAS-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329546#comment-15329546 ] Hemanth Yamijala commented on ATLAS-859: It does. Sorry - my comment is completely garbled

[jira] [Commented] (ATLAS-801) Atlas hooks would lose messages if Kafka is down for extended period of time

[ https://issues.apache.org/jira/browse/ATLAS-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329458#comment-15329458 ] Hemanth Yamijala commented on ATLAS-801: Filed ATLAS-901 to track this. > Atlas hooks would l

[jira] [Updated] (ATLAS-901) Log messages that cannot be sent to Kafka to a specific log configuration

[ https://issues.apache.org/jira/browse/ATLAS-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-901: --- Fix Version/s: 0.7-incubating > Log messages that cannot be sent to Kafka to a specific

[jira] [Assigned] (ATLAS-901) Log messages that cannot be sent to Kafka to a specific log configuration

[ https://issues.apache.org/jira/browse/ATLAS-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala reassigned ATLAS-901: -- Assignee: Hemanth Yamijala > Log messages that cannot be sent to Kafka to a speci

[jira] [Created] (ATLAS-901) Log messages that cannot be sent to Kafka to a specific log configuration

Hemanth Yamijala created ATLAS-901: -- Summary: Log messages that cannot be sent to Kafka to a specific log configuration Key: ATLAS-901 URL: https://issues.apache.org/jira/browse/ATLAS-901 Project

[jira] [Commented] (ATLAS-801) Atlas hooks would lose messages if Kafka is down for extended period of time

[ https://issues.apache.org/jira/browse/ATLAS-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329431#comment-15329431 ] Hemanth Yamijala commented on ATLAS-801: [~Daniel Cave], this is worth considering in a longer term

[jira] [Commented] (ATLAS-801) Atlas hooks would lose messages if Kafka is down for extended period of time

[ https://issues.apache.org/jira/browse/ATLAS-801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329424#comment-15329424 ] Hemanth Yamijala commented on ATLAS-801: Update on this issue: * ATLAS-515 is now committed

[jira] [Resolved] (ATLAS-859) Sqoop hook can also extend from AtlasHook

[ https://issues.apache.org/jira/browse/ATLAS-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-859. Resolution: Not A Bug [~shwethags] pointed out that the Sqoop hook class already extends

Re: ATLAS-542 Backward incompatible changes

Hi everyone, This is now committed to master. Please make note of the changes mentioned by Suma in the mail below. Let us know if there is any issue you run into. Thanks hemanth On 6/11/16, 12:53 AM, "Suma Shivaprasad" wrote: >Hi all, > >As part of changes

[jira] [Updated] (ATLAS-542) Make qualifiedName and name consistent across all Datasets and Process

[ https://issues.apache.org/jira/browse/ATLAS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-542: --- Labels: incompatibleChange (was: ) > Make qualifiedName and name consistent across

[jira] [Commented] (ATLAS-542) Make qualifiedName and name consistent across all Datasets and Process

[ https://issues.apache.org/jira/browse/ATLAS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329347#comment-15329347 ] Hemanth Yamijala commented on ATLAS-542: I just ran a few basic hive tests - via import and hook

[jira] [Commented] (ATLAS-666) PropertyUtil and XMLPropertiesUtil changes improve to performance

[ https://issues.apache.org/jira/browse/ATLAS-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329288#comment-15329288 ] Hemanth Yamijala commented on ATLAS-666: Improvement, will move to next release. > PropertyU

[jira] [Commented] (ATLAS-650) Use Apache logo on the webapp

[ https://issues.apache.org/jira/browse/ATLAS-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329283#comment-15329283 ] Hemanth Yamijala commented on ATLAS-650: Good improvement for next release. Unless its very easy

[jira] [Updated] (ATLAS-651) Add a atlas_status.py script

[ https://issues.apache.org/jira/browse/ATLAS-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-651: --- Fix Version/s: (was: 0.7-incubating) > Add a atlas_status.py scr

[jira] [Updated] (ATLAS-650) Use Apache logo on the webapp

[ https://issues.apache.org/jira/browse/ATLAS-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-650: --- Fix Version/s: (was: 0.7-incubating) > Use Apache logo on the web

[jira] [Commented] (ATLAS-576) Build with Maven 3.0.5 fails

[ https://issues.apache.org/jira/browse/ATLAS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329279#comment-15329279 ] Hemanth Yamijala commented on ATLAS-576: Have been OK with our versions of mvn so far. Will leave

[jira] [Updated] (ATLAS-504) Create components for assigning JIRA(s) ...

[ https://issues.apache.org/jira/browse/ATLAS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-504: --- Fix Version/s: (was: 0.7-incubating) > Create components for assigning JIR

[jira] [Updated] (ATLAS-576) Build with Maven 3.0.5 fails

[ https://issues.apache.org/jira/browse/ATLAS-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-576: --- Fix Version/s: (was: 0.7-incubating) > Build with Maven 3.0.5 fa

[jira] [Commented] (ATLAS-504) Create components for assigning JIRA(s) ...

[ https://issues.apache.org/jira/browse/ATLAS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329278#comment-15329278 ] Hemanth Yamijala commented on ATLAS-504: Improvement - will be good for next release. I strongly +1

[jira] [Resolved] (ATLAS-889) alter table touch is not handled

[ https://issues.apache.org/jira/browse/ATLAS-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-889. Resolution: Duplicate > alter table touch is not hand

[jira] [Commented] (ATLAS-829) When moved from embedded to standalone hbase, HBASE_CONF_DIR should point to the standalone instance of hbase, otherwise atlas fails to comeup

[ https://issues.apache.org/jira/browse/ATLAS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329268#comment-15329268 ] Hemanth Yamijala commented on ATLAS-829: [~ayubkhan], Embedded HBase is no longer the default

[jira] [Commented] (ATLAS-826) Add support for singleton traits

[ https://issues.apache.org/jira/browse/ATLAS-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329265#comment-15329265 ] Hemanth Yamijala commented on ATLAS-826: This is a new capability for Atlas. Removing from 0.7

[jira] [Updated] (ATLAS-829) When moved from embedded to standalone hbase, HBASE_CONF_DIR should point to the standalone instance of hbase, otherwise atlas fails to comeup

[ https://issues.apache.org/jira/browse/ATLAS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-829: --- Fix Version/s: (was: 0.7-incubating) > When moved from embedded to standalone hb

[jira] [Updated] (ATLAS-826) Add support for singleton traits

[ https://issues.apache.org/jira/browse/ATLAS-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-826: --- Fix Version/s: (was: 0.7-incubating) > Add support for singleton tra

[jira] [Commented] (ATLAS-822) Type updates - add supertypes

[ https://issues.apache.org/jira/browse/ATLAS-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329263#comment-15329263 ] Hemanth Yamijala commented on ATLAS-822: Not updating will probably be the fix for 0.7 (if at all

[jira] [Commented] (ATLAS-772) Ordering of columns is not maintained in schema query response, where as hive table entity response maintains the ordering

[ https://issues.apache.org/jira/browse/ATLAS-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329256#comment-15329256 ] Hemanth Yamijala commented on ATLAS-772: [~ayubkhan], I agree with [~madhan.neethiraj

[jira] [Commented] (ATLAS-815) Authentication error message

[ https://issues.apache.org/jira/browse/ATLAS-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329253#comment-15329253 ] Hemanth Yamijala commented on ATLAS-815: This seems related to ATLAS-767. > Authentication er

[jira] [Commented] (ATLAS-800) Embedded Solr5 does not start on Windows7

[ https://issues.apache.org/jira/browse/ATLAS-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329246#comment-15329246 ] Hemanth Yamijala commented on ATLAS-800: As Embedded Solr is not the default profile, I am removing

[jira] [Commented] (ATLAS-795) Business Catalog Move

[ https://issues.apache.org/jira/browse/ATLAS-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329243#comment-15329243 ] Hemanth Yamijala commented on ATLAS-795: [~bergenholtz], [~jspeidel], [~madhan.neethiraj

[jira] [Updated] (ATLAS-800) Embedded Solr5 does not start on Windows7

[ https://issues.apache.org/jira/browse/ATLAS-800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-800: --- Fix Version/s: (was: 0.7-incubating) > Embedded Solr5 does not start on Windo

[jira] [Commented] (ATLAS-768) Refactoring authorization code to be simpler

[ https://issues.apache.org/jira/browse/ATLAS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329239#comment-15329239 ] Hemanth Yamijala commented on ATLAS-768: Removing this from 0.7 bucket as it is an improvement area

[jira] [Updated] (ATLAS-768) Refactoring authorization code to be simpler

[ https://issues.apache.org/jira/browse/ATLAS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-768: --- Fix Version/s: (was: 0.7-incubating) > Refactoring authorization code to be simp

[jira] [Updated] (ATLAS-751) Add support for primary key constraint on class types

[ https://issues.apache.org/jira/browse/ATLAS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-751: --- Fix Version/s: (was: 0.7-incubating) > Add support for primary key constraint on cl

[jira] [Commented] (ATLAS-751) Add support for primary key constraint on class types

[ https://issues.apache.org/jira/browse/ATLAS-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329238#comment-15329238 ] Hemanth Yamijala commented on ATLAS-751: [~suma.shivaprasad], it appears there is more work

[jira] [Commented] (ATLAS-745) Set heapsize for embedded hbase

[ https://issues.apache.org/jira/browse/ATLAS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329235#comment-15329235 ] Hemanth Yamijala commented on ATLAS-745: Since embedded HBase is no longer the default profile, I

[jira] [Commented] (ATLAS-677) Atlas start fails the first time because of embedded hbase

[ https://issues.apache.org/jira/browse/ATLAS-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329230#comment-15329230 ] Hemanth Yamijala commented on ATLAS-677: Since embedded HBase is not the default profile, I am

[jira] [Commented] (ATLAS-741) atlas_stop fails if embedded hmaster that was started doesn't exist

[ https://issues.apache.org/jira/browse/ATLAS-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329231#comment-15329231 ] Hemanth Yamijala commented on ATLAS-741: Since embedded HBase is no longer the default profile, I

[jira] [Updated] (ATLAS-741) atlas_stop fails if embedded hmaster that was started doesn't exist

[ https://issues.apache.org/jira/browse/ATLAS-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-741: --- Fix Version/s: (was: 0.7-incubating) > atlas_stop fails if embedded hmas

[jira] [Updated] (ATLAS-677) Atlas start fails the first time because of embedded hbase

[ https://issues.apache.org/jira/browse/ATLAS-677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-677: --- Fix Version/s: (was: 0.7-incubating) > Atlas start fails the first time beca

[jira] [Commented] (ATLAS-740) UI: "References" DSL query response is not handled properly

[ https://issues.apache.org/jira/browse/ATLAS-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329228#comment-15329228 ] Hemanth Yamijala commented on ATLAS-740: [~ayubkhan], as discussed the Referenceable is a very

[jira] [Updated] (ATLAS-740) UI: "References" DSL query response is not handled properly

[ https://issues.apache.org/jira/browse/ATLAS-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-740: --- Fix Version/s: (was: 0.7-incubating) > UI: "References" DSL query response i

[jira] [Updated] (ATLAS-704) With Authentication and HA enabled, UI redirection asks for password from already authenticated user

[ https://issues.apache.org/jira/browse/ATLAS-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-704: --- Fix Version/s: 0.7-incubating > With Authentication and HA enabled, UI redirection a

[jira] [Assigned] (ATLAS-704) With Authentication and HA enabled, UI redirection asks for password from already authenticated user

[ https://issues.apache.org/jira/browse/ATLAS-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala reassigned ATLAS-704: -- Assignee: Hemanth Yamijala > With Authentication and HA enabled, UI redirection a

[jira] [Updated] (ATLAS-704) With Authentication and HA enabled, UI redirection asks for password from already authenticated user

[ https://issues.apache.org/jira/browse/ATLAS-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-704: --- Fix Version/s: (was: 0.7-incubating) > With Authentication and HA enabled, UI redirect

[jira] [Resolved] (ATLAS-701) atlas-admin-site.xml contains actual endpoints

[ https://issues.apache.org/jira/browse/ATLAS-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-701. Resolution: Duplicate This was addressed in ATLAS-869. Resolving as duplicate. > at

[jira] [Commented] (ATLAS-671) Include binary dist in release

[ https://issues.apache.org/jira/browse/ATLAS-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329219#comment-15329219 ] Hemanth Yamijala commented on ATLAS-671: [~j...@nanthrax.net] - did you have a chance to look

[jira] [Commented] (ATLAS-638) UI : Recognize and display HDFS Paths with a different notation

[ https://issues.apache.org/jira/browse/ATLAS-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329215#comment-15329215 ] Hemanth Yamijala commented on ATLAS-638: This looks like an improvement. Hence, moving out of 0.7

[jira] [Commented] (ATLAS-542) Make qualifiedName and name consistent across all Datasets and Process

[ https://issues.apache.org/jira/browse/ATLAS-542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329211#comment-15329211 ] Hemanth Yamijala commented on ATLAS-542: Looks good to me. Will run tests and commit. > M

[jira] [Commented] (ATLAS-614) Try to avoid duplication of initialization code in HA mode

[ https://issues.apache.org/jira/browse/ATLAS-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329097#comment-15329097 ] Hemanth Yamijala commented on ATLAS-614: This is really an improvement. Moving out of the 0.7

[jira] [Updated] (ATLAS-614) Try to avoid duplication of initialization code in HA mode

[ https://issues.apache.org/jira/browse/ATLAS-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-614: --- Fix Version/s: (was: 0.7-incubating) > Try to avoid duplication of initialization c

[jira] [Commented] (ATLAS-613) Allow configuration of host and port on which an Atlas instance should start

[ https://issues.apache.org/jira/browse/ATLAS-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329090#comment-15329090 ] Hemanth Yamijala commented on ATLAS-613: This is really an improvement. Moving out of 0.7 release

[jira] [Updated] (ATLAS-613) Allow configuration of host and port on which an Atlas instance should start

[ https://issues.apache.org/jira/browse/ATLAS-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-613: --- Fix Version/s: (was: 0.7-incubating) > Allow configuration of host and port on wh

[jira] [Resolved] (ATLAS-608) Hook modules depend on atlas-server-api

[ https://issues.apache.org/jira/browse/ATLAS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-608. Resolution: Fixed I checked the pom.xml of hive and falcon hooks and don't see

[jira] [Resolved] (ATLAS-596) UI : Bucket cols and sortCols within storage descriptor are not displayed correctly

[ https://issues.apache.org/jira/browse/ATLAS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-596. Resolution: Fixed Verified this is working in the new UI. > UI : Bucket cols and sortC

[jira] [Commented] (ATLAS-592) Queue for failed hook messages

[ https://issues.apache.org/jira/browse/ATLAS-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329060#comment-15329060 ] Hemanth Yamijala commented on ATLAS-592: [~shwethags], moved this out of 0.7 release. For now

[jira] [Updated] (ATLAS-592) Queue for failed hook messages

[ https://issues.apache.org/jira/browse/ATLAS-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-592: --- Fix Version/s: (was: 0.7-incubating) > Queue for failed hook messa

[jira] [Commented] (ATLAS-568) Parallelize Hive hook operations

[ https://issues.apache.org/jira/browse/ATLAS-568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329050#comment-15329050 ] Hemanth Yamijala commented on ATLAS-568: I believe this is going to be fairly complicated to do

[jira] [Updated] (ATLAS-568) Parallelize Hive hook operations

[ https://issues.apache.org/jira/browse/ATLAS-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-568: --- Fix Version/s: (was: 0.7-incubating) > Parallelize Hive hook operati

[jira] [Updated] (ATLAS-559) Atlas should allow JSONs to be submitted that don't have optional attributes.

[ https://issues.apache.org/jira/browse/ATLAS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-559: --- Issue Type: Improvement (was: Bug) > Atlas should allow JSONs to be submitted that don't h

[jira] [Commented] (ATLAS-559) Atlas should allow JSONs to be submitted that don't have optional attributes.

[ https://issues.apache.org/jira/browse/ATLAS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329043#comment-15329043 ] Hemanth Yamijala commented on ATLAS-559: This does not break existing functionality

[jira] [Updated] (ATLAS-559) Atlas should allow JSONs to be submitted that don't have optional attributes.

[ https://issues.apache.org/jira/browse/ATLAS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-559: --- Fix Version/s: (was: 0.7-incubating) > Atlas should allow JSONs to be submitted that do

[jira] [Resolved] (ATLAS-554) Remove Powered By

[ https://issues.apache.org/jira/browse/ATLAS-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-554. Resolution: Fixed Dashboardv2 is primary now. Closing as resolved. > Remove Powe

[jira] [Updated] (ATLAS-535) Support delete cascade efficiently

[ https://issues.apache.org/jira/browse/ATLAS-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-535: --- Fix Version/s: (was: 0.7-incubating) > Support delete cascade efficien

[jira] [Resolved] (ATLAS-506) Atlas UI: numBuckets shows up as invalid date

[ https://issues.apache.org/jira/browse/ATLAS-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-506. Resolution: Fixed This has been fixed as part of the move to the new UI. > Atlas

[jira] [Commented] (ATLAS-501) UI: Add link to document that explains the DSL syntax

[ https://issues.apache.org/jira/browse/ATLAS-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329027#comment-15329027 ] Hemanth Yamijala commented on ATLAS-501: New feature - so won't make it to the 0.7 release. >

[jira] [Updated] (ATLAS-501) UI: Add link to document that explains the DSL syntax

[ https://issues.apache.org/jira/browse/ATLAS-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-501: --- Fix Version/s: (was: 0.7-incubating) > UI: Add link to document that explains the

[jira] [Resolved] (ATLAS-490) Switch to SOLR out of box experience

[ https://issues.apache.org/jira/browse/ATLAS-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala resolved ATLAS-490. Resolution: Fixed This is now done as part of ATLAS-833. > Switch to SOLR out of

[jira] [Commented] (ATLAS-489) GUI refresh on state change

[ https://issues.apache.org/jira/browse/ATLAS-489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329005#comment-15329005 ] Hemanth Yamijala commented on ATLAS-489: Marked as improvement. Won't make the 0.7 release

[jira] [Updated] (ATLAS-489) GUI refresh on state change

[ https://issues.apache.org/jira/browse/ATLAS-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-489: --- Fix Version/s: (was: 0.7-incubating) > GUI refresh on state cha

[jira] [Updated] (ATLAS-472) UI : Pagination is failing when the search result has more numbers of pages

[ https://issues.apache.org/jira/browse/ATLAS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-472: --- Assignee: Keval Bhatt (was: Darshan Kumar) > UI : Pagination is failing when the sea

[jira] [Updated] (ATLAS-472) UI : Pagination is failing when the search result has more numbers of pages

[ https://issues.apache.org/jira/browse/ATLAS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-472: --- Fix Version/s: (was: 0.7-incubating) > UI : Pagination is failing when the search res

[jira] [Updated] (ATLAS-472) UI : Pagination is failing when the search result has more numbers of pages

[ https://issues.apache.org/jira/browse/ATLAS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-472: --- Fix Version/s: 0.7-incubating > UI : Pagination is failing when the search result has m

[jira] [Updated] (ATLAS-216) UI: showing invalid date and time values for hive table

[ https://issues.apache.org/jira/browse/ATLAS-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-216: --- Fix Version/s: (was: 0.7-incubating) > UI: showing invalid date and time values for h

[jira] [Commented] (ATLAS-216) UI: showing invalid date and time values for hive table

[ https://issues.apache.org/jira/browse/ATLAS-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15329003#comment-15329003 ] Hemanth Yamijala commented on ATLAS-216: I see create time is fine and also last access time

[jira] [Commented] (ATLAS-796) Fulltext search 500 Error

[ https://issues.apache.org/jira/browse/ATLAS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328998#comment-15328998 ] Hemanth Yamijala commented on ATLAS-796: [~ayubkhan], Firing the query with a quote around

[jira] [Commented] (ATLAS-891) UI changes to implement Update term

[ https://issues.apache.org/jira/browse/ATLAS-891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15328971#comment-15328971 ] Hemanth Yamijala commented on ATLAS-891: Tested this once more on top of the committed ATLAS-794

<    1   2   3   4   5   6   7   8   9   >