[jira] [Commented] (ATLAS-61) Inconsistent metadata content
[
https://issues.apache.org/jira/browse/ATLAS-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14638198#comment-14638198
]
Shwetha G S commented on ATLAS-61:
--
ATLAS-46 is still not complete. Please wait for ATLAS-80
Inconsistent metadata content
-
Key: ATLAS-61
URL: https://issues.apache.org/jira/browse/ATLAS-61
Project: Atlas
Issue Type: Bug
Reporter: David Kaspar
Attachments: application.log
Steps to reproduce:
build Atlas binaries and install it to a fresh directory (aka in untar the
binary artifact to new/empty directory) and run:
{code}
apache-atlas-0.6-incubating-SNAPSHOT/bin/atlas_start.sh
sleep 30
curl http://127.0.0.1:21000/api/atlas/types
# it prints:
{results:[Process,Infrastructure,DataSet],count:3,requestId:1244107514@qtp-1475081618-0
- 4ced54d8-a726-4384-8e97-3f3d5535d307}
apache-atlas-0.6-incubating-SNAPSHOT/bin/atlas_stop.sh
apache-atlas-0.6-incubating-SNAPSHOT/bin/atlas_start.sh
sleep 30
curl http://127.0.0.1:21000/api/atlas/types
# it prints:
{results:[hive_function_type,hive_index,Process,hive_column,hive_serde,hive_function,hive_resourceuri,hive_table,hive_storagedesc,hive_principal_type,hive_process,hive_resource_type,hive_type,hive_object_type,Infrastructure,hive_order,hive_role,DataSet,hive_partition,hive_db],count:20,requestId:500065027@qtp-1586292005-0
- 22906b64-8c9e-4f1d-97b6-6eadf2a71bbf}
{code}
Note that I have not been load any types - I just started, stopped and then
started the atlas again and it printed inconsistent types.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (ATLAS-80) Support for variables in application properties
[ https://issues.apache.org/jira/browse/ATLAS-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shwetha G S reassigned ATLAS-80: Assignee: Shwetha G S Support for variables in application properties --- Key: ATLAS-80 URL: https://issues.apache.org/jira/browse/ATLAS-80 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Assignee: Shwetha G S We use commons-configuration for application properties and 1.x that we use doesn't support variables in properties. 2.x has support for variables, but is in beta and is not production ready. Meanwhile, we can support it using EL expression and substitute using system properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-78) [Olingo V2.0.4] Bug in Function Imports: nullable parameters not supported
[ https://issues.apache.org/jira/browse/ATLAS-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14637964#comment-14637964 ] Venkatesh Seetharam commented on ATLAS-78: -- This is Atlas and not Olingo project. Marking this as invalid. [Olingo V2.0.4] Bug in Function Imports: nullable parameters not supported -- Key: ATLAS-78 URL: https://issues.apache.org/jira/browse/ATLAS-78 Project: Atlas Issue Type: Bug Reporter: Andreas Pfenninger -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ATLAS-69) Add Falcon Bridge and Hook for Atlas
[ https://issues.apache.org/jira/browse/ATLAS-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatesh Seetharam updated ATLAS-69: - Summary: Add Falcon Bridge and Hook for Atlas (was: Falcon Plugin for Atlas) Add Falcon Bridge and Hook for Atlas Key: ATLAS-69 URL: https://issues.apache.org/jira/browse/ATLAS-69 Project: Atlas Issue Type: New Feature Reporter: Suma Shivaprasad Add a falcon plugin to consume falcon entities like cluster, feed, process into ATLAS. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-65) tableExists uses non-standard SQL keyword LIMIT
[ https://issues.apache.org/jira/browse/ATLAS-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatesh Seetharam resolved ATLAS-65. -- Resolution: Invalid tableExists uses non-standard SQL keyword LIMIT --- Key: ATLAS-65 URL: https://issues.apache.org/jira/browse/ATLAS-65 Project: Atlas Issue Type: Test Reporter: Robert Beauchemin Priority: Trivial This entry was created in error and cannot be deleted by me. Please delete it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ATLAS-57) Allow Kuromoji to load a custom dictionary from the file system instead of the classpath
[ https://issues.apache.org/jira/browse/ATLAS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatesh Seetharam resolved ATLAS-57. -- Resolution: Invalid Allow Kuromoji to load a custom dictionary from the file system instead of the classpath Key: ATLAS-57 URL: https://issues.apache.org/jira/browse/ATLAS-57 Project: Atlas Issue Type: Improvement Reporter: Hayden Muhl The JapaneseTokenizer currently loads its dictionary directly from the classpath. We create a custom dictionary with additional words, and in order to get the JapaneseTokenizer to pick up our custom dictionary, we have to repackage the WAR file (we currently use 4.10) to include our custom dictionary. Proposed changes: * Publish the Kuromoji tools as a JAR to Maven to make compiling a custom dictionary easier. * Move loading of the dictionary out to the JapaneseTokenizerFactory, and pass the dictionary into the JapaneseTokenizer constructor. * Add an argument to the JapaneseTokenizerFactory to load a dictionary off the file system. If this argument is not passed, then load the default dictionary from the classpath. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ATLAS-57) Allow Kuromoji to load a custom dictionary from the file system instead of the classpath
[ https://issues.apache.org/jira/browse/ATLAS-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14637896#comment-14637896 ] Venkatesh Seetharam commented on ATLAS-57: -- Not sure how this is related to Atlas, closing this as invalid. Allow Kuromoji to load a custom dictionary from the file system instead of the classpath Key: ATLAS-57 URL: https://issues.apache.org/jira/browse/ATLAS-57 Project: Atlas Issue Type: Improvement Reporter: Hayden Muhl The JapaneseTokenizer currently loads its dictionary directly from the classpath. We create a custom dictionary with additional words, and in order to get the JapaneseTokenizer to pick up our custom dictionary, we have to repackage the WAR file (we currently use 4.10) to include our custom dictionary. Proposed changes: * Publish the Kuromoji tools as a JAR to Maven to make compiling a custom dictionary easier. * Move loading of the dictionary out to the JapaneseTokenizerFactory, and pass the dictionary into the JapaneseTokenizer constructor. * Add an argument to the JapaneseTokenizerFactory to load a dictionary off the file system. If this argument is not passed, then load the default dictionary from the classpath. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
