Ayub Khan created ATLAS-877:
---
Summary: CreateTime of an entity(for example hive table) changes
for every update
Key: ATLAS-877
URL: https://issues.apache.org/jira/browse/ATLAS-877
Project: Atlas
Ayub Khan created ATLAS-876:
---
Summary: No lineage for a re-created ctas table
Key: ATLAS-876
URL: https://issues.apache.org/jira/browse/ATLAS-876
Project: Atlas
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/ATLAS-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan resolved ATLAS-868.
-
Resolution: Invalid
> TestMetadata test failure results in build failure
>
Ayub Khan created ATLAS-868:
---
Summary: TestMetadata test failure results in build failure
Key: ATLAS-868
URL: https://issues.apache.org/jira/browse/ATLAS-868
Project: Atlas
Issue Type: Bug
[
https://issues.apache.org/jira/browse/ATLAS-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-850:
Summary: Atlas sends entity notifications to consumers(in this case Ranger)
even if there are no consumers
[
https://issues.apache.org/jira/browse/ATLAS-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-850:
Summary: Atlas sends entity notifications to consumers(in our case Ranger)
even if there are no consumers
Ayub Khan created ATLAS-850:
---
Summary: Atlas sends ATLAS_ENTITIES notifications to consumers
even if there are no consumers interested
Key: ATLAS-850
URL: https://issues.apache.org/jira/browse/ATLAS-850
[
https://issues.apache.org/jira/browse/ATLAS-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan resolved ATLAS-842.
-
Resolution: Invalid
> /api/atlas/v1/taxonomies api request fails with 403 error, policystore update
> is
Ayub Khan created ATLAS-842:
---
Summary: /api/atlas/v1/taxonomies api request fails with 403
error, policystore update is needed
Key: ATLAS-842
URL: https://issues.apache.org/jira/browse/ATLAS-842
Project:
Ayub Khan created ATLAS-839:
---
Summary: NEW UI: lineage is broken
Key: ATLAS-839
URL: https://issues.apache.org/jira/browse/ATLAS-839
Project: Atlas
Issue Type: Bug
Affects Versions:
[
https://issues.apache.org/jira/browse/ATLAS-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-838:
Description:
Create a hive table and make schema call on that table.
{noformat}
curl -v
Ayub Khan created ATLAS-838:
---
Summary: hive table schema api is broken.
Key: ATLAS-838
URL: https://issues.apache.org/jira/browse/ATLAS-838
Project: Atlas
Issue Type: Bug
Affects Versions:
[
https://issues.apache.org/jira/browse/ATLAS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-829:
Comment: was deleted
(was: [~madhan.neethiraj] Yes, I have manually updated HBASE_CONF_DIR when
moved from
[
https://issues.apache.org/jira/browse/ATLAS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15304084#comment-15304084
]
Ayub Khan commented on ATLAS-829:
-
[~madhan.neethiraj] Yes, I have manually updated HBASE_CONF_DIR when
Ayub Khan created ATLAS-829:
---
Summary: When moved from embedded to standalone hbase,
HBASE_CONF_DIR should point to the standalone instance of hbase, otherwise
atlas fails to comeup
Key: ATLAS-829
URL:
[
https://issues.apache.org/jira/browse/ATLAS-820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-820:
Assignee: Madhan Neethiraj (was: Ayub Khan)
> Kerberized env: Authentication failing
>
Ayub Khan created ATLAS-820:
---
Summary: Kerberized env: Authentication failing
Key: ATLAS-820
URL: https://issues.apache.org/jira/browse/ATLAS-820
Project: Atlas
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/ATLAS-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-804:
Affects Version/s: 0.7-incubating
> For hive_db, "locationUri" field is renamed to "location" but the hive
[
https://issues.apache.org/jira/browse/ATLAS-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-804:
Assignee: Suma Shivaprasad
> For hive_db, "locationUri" field is renamed to "location" but the hive data
>
Ayub Khan created ATLAS-804:
---
Summary: For hive_db, "locationUri" field is renamed to "location"
but the hive data model json is still showing as "locationUri"
Key: ATLAS-804
URL:
Ayub Khan created ATLAS-778:
---
Summary: ALTER TABLE TOUCH is not modelled
Key: ATLAS-778
URL: https://issues.apache.org/jira/browse/ATLAS-778
Project: Atlas
Issue Type: Bug
Affects Versions:
Ayub Khan created ATLAS-772:
---
Summary: Ordering of columns is not maintained in schema query
response, where as hive table entity response maintains the ordering
Key: ATLAS-772
URL:
Ayub Khan created ATLAS-761:
---
Summary: UI: is ignoring table parameters
Key: ATLAS-761
URL: https://issues.apache.org/jira/browse/ATLAS-761
Project: Atlas
Issue Type: Bug
Affects Versions:
Ayub Khan created ATLAS-760:
---
Summary: Missing table parameters(last_modified_by and
last_modified_time)
Key: ATLAS-760
URL: https://issues.apache.org/jira/browse/ATLAS-760
Project: Atlas
Issue
[
https://issues.apache.org/jira/browse/ATLAS-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-758:
Attachment: bug.log
> hdfs location of hive table is pointing to old location even after rename.
>
Ayub Khan created ATLAS-758:
---
Summary: hdfs location of hive table is pointing to old location
even after rename.
Key: ATLAS-758
URL: https://issues.apache.org/jira/browse/ATLAS-758
Project: Atlas
Ayub Khan created ATLAS-756:
---
Summary: UI: Hive lineage is not properly rendered when source
table has multiple edges
Key: ATLAS-756
URL: https://issues.apache.org/jira/browse/ATLAS-756
Project: Atlas
[
https://issues.apache.org/jira/browse/ATLAS-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-755:
Description:
Add hive table props: ALTER TABLE test_table set TBLPROPERTIES
Ayub Khan created ATLAS-755:
---
Summary: UI: User defined tableproperties are ignored/not
displayed.
Key: ATLAS-755
URL: https://issues.apache.org/jira/browse/ATLAS-755
Project: Atlas
Issue Type:
Ayub Khan created ATLAS-753:
---
Summary: UI: showing "viewOriginalText" field which is not part of
hive table metadata message and it will be always be null
Key: ATLAS-753
URL:
[
https://issues.apache.org/jira/browse/ATLAS-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-743:
Description: Modifying a deleted entity is still allowed. For example:
attaching a trait to a deleted entity
Ayub Khan created ATLAS-743:
---
Summary: Soft Delete: Modifying a deleted entity should not be
allowed.
Key: ATLAS-743
URL: https://issues.apache.org/jira/browse/ATLAS-743
Project: Atlas
Issue
Ayub Khan created ATLAS-740:
---
Summary: UI: "References" DSL query response is not handled
properly
Key: ATLAS-740
URL: https://issues.apache.org/jira/browse/ATLAS-740
Project: Atlas
Issue Type:
Ayub Khan created ATLAS-739:
---
Summary: UI: Search result for hive_process results in "query text
of hive process shown as href link"
Key: ATLAS-739
URL: https://issues.apache.org/jira/browse/ATLAS-739
[
https://issues.apache.org/jira/browse/ATLAS-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-735:
Description:
Steps to repro:
1. Through search tab, fire a valid dsl search query(eg: hive_table) and make
[
https://issues.apache.org/jira/browse/ATLAS-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-735:
Attachment: DSL-query.gif
Attaching a GIF file which captures all the details of reproducing the issue.
>
Ayub Khan created ATLAS-735:
---
Summary: UI showing incorrect results if two queries are
executed.(first query succeeds but second should fail)
Key: ATLAS-735
URL: https://issues.apache.org/jira/browse/ATLAS-735
Ayub Khan created ATLAS-734:
---
Summary: DSL queries are currently case sensitive, from customer's
perspective it is better to make them case insensitive
Key: ATLAS-734
URL:
Ayub Khan created ATLAS-733:
---
Summary: UI: "undefined" XHR request is made for every entity GET
page request.
Key: ATLAS-733
URL: https://issues.apache.org/jira/browse/ATLAS-733
Project: Atlas
[
https://issues.apache.org/jira/browse/ATLAS-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-713:
Description:
Atlas UI is still showing the deleted column of a hive table (Entity response
of hive table
[
https://issues.apache.org/jira/browse/ATLAS-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15257908#comment-15257908
]
Ayub Khan commented on ATLAS-713:
-
This is true in case of deleted hive tables as well.
Test:
1. Create
Ayub Khan created ATLAS-713:
---
Summary: Atlas UI is still showing the deleted column of a hive
table (Entity response of hive table does not have it). - with browser cache
disabled.
Key: ATLAS-713
URL:
Ayub Khan created ATLAS-710:
---
Summary: Soft deletes: GET response on a deleted hive tables
should have references to hive_db and hive_storagedesc
Key: ATLAS-710
URL: https://issues.apache.org/jira/browse/ATLAS-710
Ayub Khan created ATLAS-703:
---
Summary: No entity notification updates are sent for hive table
protection feature. Seems like table protection changes are not yet modelled.
Key: ATLAS-703
URL:
[
https://issues.apache.org/jira/browse/ATLAS-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-702:
Summary: "ALTER TABLE .. NOT STORED AS DIRECTORIES" metadata update is not
sent to Atlas. (was: "ALTER
Ayub Khan created ATLAS-702:
---
Summary: "ALTER TABLE .. NOT STORED AS DIRECTORIES" metadata
update is not triggered.
Key: ATLAS-702
URL: https://issues.apache.org/jira/browse/ATLAS-702
Project: Atlas
[
https://issues.apache.org/jira/browse/ATLAS-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238993#comment-15238993
]
Ayub Khan commented on ATLAS-663:
-
[~bergenholtz] and [~tbeerbower]
> As part of embedded hbase changes,
[
https://issues.apache.org/jira/browse/ATLAS-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-663:
Description:
As part of embedded hbase changes, 'zookeeper-data' and 'root' folder are
created under
Ayub Khan created ATLAS-663:
---
Summary: As part of embedded hbase changes, 'zookeeper-data' and
'root' folder are created under project root dir. These should be under
/data dir.
Key: ATLAS-663
URL:
[
https://issues.apache.org/jira/browse/ATLAS-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-583:
Summary: Rename table should retain traits/tags assigned to columns/storage
descriptors (was: Rename table
[
https://issues.apache.org/jira/browse/ATLAS-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15238687#comment-15238687
]
Ayub Khan commented on ATLAS-583:
-
Rename table should retain traits/tags assigned to storage descriptors
[
https://issues.apache.org/jira/browse/ATLAS-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-648:
Description:
Steps to repro:
create table src (x int, y int, s string);
create view view3 as select * from
Ayub Khan created ATLAS-648:
---
Summary: Alter view rename does not work across databases
Key: ATLAS-648
URL: https://issues.apache.org/jira/browse/ATLAS-648
Project: Atlas
Issue Type: Bug
[
https://issues.apache.org/jira/browse/ATLAS-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15227832#comment-15227832
]
Ayub Khan commented on ATLAS-639:
-
Also below continous error messages are observed in the log
{noformat}
[
https://issues.apache.org/jira/browse/ATLAS-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-639:
Description:
Exception in log for lineage request
Steps to repro:
create table j13 (col4 String);
Ayub Khan created ATLAS-639:
---
Summary: Exception for lineage request
Key: ATLAS-639
URL: https://issues.apache.org/jira/browse/ATLAS-639
Project: Atlas
Issue Type: Bug
Affects Versions: trunk
[
https://issues.apache.org/jira/browse/ATLAS-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-626:
Issue Type: Bug (was: Sub-task)
Parent: (was: ATLAS-492)
> Hive temporary table metadata is
[
https://issues.apache.org/jira/browse/ATLAS-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-626:
Issue Type: Sub-task (was: Bug)
Parent: ATLAS-492
> Hive temporary table metadata is captured in
[
https://issues.apache.org/jira/browse/ATLAS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15225910#comment-15225910
]
Ayub Khan commented on ATLAS-635:
-
[~suma.shivaprasad]
> Process showing old entity name where as actual
[
https://issues.apache.org/jira/browse/ATLAS-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15225908#comment-15225908
]
Ayub Khan commented on ATLAS-636:
-
[~suma.shivaprasad]
> Tags/Traits associated with partitionkeys should
Ayub Khan created ATLAS-636:
---
Summary: Tags/Traits associated with partitionkeys should be
retained after rename table.
Key: ATLAS-636
URL: https://issues.apache.org/jira/browse/ATLAS-636
Project: Atlas
[
https://issues.apache.org/jira/browse/ATLAS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15225769#comment-15225769
]
Ayub Khan commented on ATLAS-635:
-
Attached issue snapshot for reference.
> Process showing old entity
[
https://issues.apache.org/jira/browse/ATLAS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-635:
Attachment: screenshot-1.png
> Process showing old entity name where as actual entity is renamed.
>
Ayub Khan created ATLAS-635:
---
Summary: Process showing old entity name where as actual entity is
renamed.
Key: ATLAS-635
URL: https://issues.apache.org/jira/browse/ATLAS-635
Project: Atlas
Issue
Ayub Khan created ATLAS-634:
---
Summary: Atlas failed to start embedded kafka
Key: ATLAS-634
URL: https://issues.apache.org/jira/browse/ATLAS-634
Project: Atlas
Issue Type: Bug
Affects Versions:
[
https://issues.apache.org/jira/browse/ATLAS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15225733#comment-15225733
]
Ayub Khan commented on ATLAS-633:
-
This issue was observed when atlas was started in embedded mode on local
Ayub Khan created ATLAS-633:
---
Summary: "kafka.common.NoReplicaOnlineException" exception on
atlas startup
Key: ATLAS-633
URL: https://issues.apache.org/jira/browse/ATLAS-633
Project: Atlas
Issue
Ayub Khan created ATLAS-626:
---
Summary: Hive temporary table metadata is captured in atlas.
Key: ATLAS-626
URL: https://issues.apache.org/jira/browse/ATLAS-626
Project: Atlas
Issue Type: Bug
Ayub Khan created ATLAS-624:
---
Summary: UI: Clicking a tag hyperlink should always result in DSL
search. In some cases, results in full-text search.
Key: ATLAS-624
URL: https://issues.apache.org/jira/browse/ATLAS-624
[
https://issues.apache.org/jira/browse/ATLAS-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-623:
Attachment: Screen Shot 2016-04-04 at 11.25.51 AM.png
Attaching UI snapshot for reference.
> Atlas startup
[
https://issues.apache.org/jira/browse/ATLAS-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15223701#comment-15223701
]
Ayub Khan commented on ATLAS-623:
-
[~yhemanth]
> Atlas startup showing new tags(DataProducer and
Ayub Khan created ATLAS-623:
---
Summary: Atlas startup showing new tags(DataProducer and
DataConsumer) added by default
Key: ATLAS-623
URL: https://issues.apache.org/jira/browse/ATLAS-623
Project: Atlas
[
https://issues.apache.org/jira/browse/ATLAS-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15197770#comment-15197770
]
Ayub Khan commented on ATLAS-529:
-
[~suma.shivaprasad] What is the use-case for supporting dropDB with no
[
https://issues.apache.org/jira/browse/ATLAS-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-570:
Issue Type: Sub-task (was: Task)
Parent: ATLAS-510
> Ability to cascade failover in an multiple
Ayub Khan created ATLAS-570:
---
Summary: Ability to cascade failover in an multiple instance HA
cluster
Key: ATLAS-570
URL: https://issues.apache.org/jira/browse/ATLAS-570
Project: Atlas
Issue
[
https://issues.apache.org/jira/browse/ATLAS-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-536:
Attachment: ATLAS-536-v4.patch
> Falcon hook loads incorrect configuration when -Datlas.conf is not given
[
https://issues.apache.org/jira/browse/ATLAS-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-536:
Attachment: Adding_atlas_conf_path_to_falcon_server_opts-4.patch
Attaching a new patch with minor changes.
[
https://issues.apache.org/jira/browse/ATLAS-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15171888#comment-15171888
]
Ayub Khan edited comment on ATLAS-536 at 2/29/16 2:04 PM:
--
[~shwethags]
Thanks
[
https://issues.apache.org/jira/browse/ATLAS-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-536:
Attachment: Adding_atlas_conf_path_to_falcon_server_opts-3.patch
[~shwethags]
I have made the changes
[
https://issues.apache.org/jira/browse/ATLAS-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-536:
Attachment: Adding_atlas_conf_path_to_falcon_server_opts-2.patch
> Falcon hook loads incorrect configuration
[
https://issues.apache.org/jira/browse/ATLAS-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-536:
Attachment: Adding_atlas_conf_path_to_falcon_server_opts.patch
> Falcon hook loads incorrect configuration
[
https://issues.apache.org/jira/browse/ATLAS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-537:
Attachment: logs.tar.gz
> Falcon hook failing when tried to submit a process which creates a hive table.
>
[
https://issues.apache.org/jira/browse/ATLAS-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15168713#comment-15168713
]
Ayub Khan commented on ATLAS-537:
-
Attached the application logs for falcon and atlas.
Along with that,
Ayub Khan created ATLAS-536:
---
Summary: Falcon hook loads incorrect configuration when
-Datlas.conf is not given when falcon server startup. this needs to be
documented.
Key: ATLAS-536
URL:
Ayub Khan created ATLAS-477:
---
Summary: Entity update API: Inconsistent error message for data
validation
Key: ATLAS-477
URL: https://issues.apache.org/jira/browse/ATLAS-477
Project: Atlas
Issue
[
https://issues.apache.org/jira/browse/ATLAS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-434:
Assignee: Anilsg
> Add tags does not support non-English characters
>
Ayub Khan created ATLAS-396:
---
Summary: Creating an entity with non-existing type results in
"Unable to deserialize json" error
Key: ATLAS-396
URL: https://issues.apache.org/jira/browse/ATLAS-396
Project:
[
https://issues.apache.org/jira/browse/ATLAS-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-396:
Labels: regression (was: )
> Creating an entity with non-existing type results in "Unable to deserialize
>
Ayub Khan created ATLAS-400:
---
Summary: Entity update using PUT method is broken
Key: ATLAS-400
URL: https://issues.apache.org/jira/browse/ATLAS-400
Project: Atlas
Issue Type: Bug
Affects
Ayub Khan created ATLAS-398:
---
Summary: Delete trait that exists but not linked to entity results
in "400 Bad request". It should result "404 not found"
Key: ATLAS-398
URL:
Ayub Khan created ATLAS-397:
---
Summary: BigDecimal handling is broken, atlas returns double for a
bigdecimal.
Key: ATLAS-397
URL: https://issues.apache.org/jira/browse/ATLAS-397
Project: Atlas
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15037326#comment-15037326
]
Ayub Khan edited comment on ATLAS-279 at 12/3/15 6:29 AM:
--
[~Anilg]
UI not
Ayub Khan created ATLAS-354:
---
Summary: Kerberized cluster: quick_start.py fails to add sample
data
Key: ATLAS-354
URL: https://issues.apache.org/jira/browse/ATLAS-354
Project: Atlas
Issue Type:
Ayub Khan created ATLAS-355:
---
Summary: Kerberized cluster: client.properties does not have
correct values for the properties
Key: ATLAS-355
URL: https://issues.apache.org/jira/browse/ATLAS-355
Project:
Ayub Khan created ATLAS-351:
---
Summary: Solr as indexing backend is not picked up by titan when
storage backend is set to hbase
Key: ATLAS-351
URL: https://issues.apache.org/jira/browse/ATLAS-351
Project:
Ayub Khan created ATLAS-350:
---
Summary: Document jaas config details for atlas
Key: ATLAS-350
URL: https://issues.apache.org/jira/browse/ATLAS-350
Project: Atlas
Issue Type: Bug
Affects
[
https://issues.apache.org/jira/browse/ATLAS-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayub Khan updated ATLAS-351:
Assignee: Erik Bergenholtz
> Solr as indexing backend is not picked up by titan when storage backend is
>
[
https://issues.apache.org/jira/browse/ATLAS-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15033164#comment-15033164
]
Ayub Khan commented on ATLAS-344:
-
+1
> Document HBase permissions for secure cluster
>
Ayub Khan created ATLAS-335:
---
Summary: Kerberized cluster: Atlas fails to come up with hbase as
backend
Key: ATLAS-335
URL: https://issues.apache.org/jira/browse/ATLAS-335
Project: Atlas
Issue
[
https://issues.apache.org/jira/browse/ATLAS-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15022029#comment-15022029
]
Ayub Khan edited comment on ATLAS-279 at 11/23/15 12:32 PM:
[~Anilg] Looks good
201 - 300 of 381 matches
Mail list logo
