eagle query framework currently support @Prefix directly, no need additional change.
Sent from my iPhone > On Feb 5, 2016, at 12:58 PM, Liangfei.Su <[email protected]> wrote: > > One table for metadata is good idea. And I would suggest use a _type > field/tag to indicate the different type of metadata. > >> On Fri, Feb 5, 2016 at 9:09 AM, Hao Chen <[email protected]> wrote: >> >> I think it's better to use single table named "eagle_metadata" with >> different prefix for all metadata entities >> >>> On Feb 5, 2016, at 7:48 AM, Edward Zhang (JIRA) <[email protected]> wrote: >>> >>> Edward Zhang created EAGLE-150: >>> ---------------------------------- >>> >>> Summary: create eagle basic tables remotely >>> Key: EAGLE-150 >>> URL: https://issues.apache.org/jira/browse/EAGLE-150 >>> Project: Eagle >>> Issue Type: Improvement >>> Reporter: Edward Zhang >>> >>> >>> In development time, it is necessary to create basic table within IDE >> either by remote ssh or hbase client library. >>> The benefit is that developer does not need to login to sandbox and >> create table manually. >>> Better to automatically check all available table definitions and create >> them >>> The basic tables include the following list >>> tables.add("eagle_metric"); >>> tables.add("actiondetail"); >>> tables.add("alertdetail"); >>> tables.add("alertgroup"); >>> tables.add("alertmeta"); >>> tables.add("alertMetaEntity"); >>> >>> // for alert framework >>> tables.add("alertDataSource"); >>> tables.add("alertStream"); >>> tables.add("alertExecutor"); >>> tables.add("alertStreamSchema"); >>> tables.add("alertdef"); >>> >>> // for security >>> tables.add("hiveResourceSensitivity"); >>> tables.add("fileSensitivity"); >>> tables.add("ipzone"); >>> tables.add("mlmodel"); >>> tables.add("userprofile"); >>> >>> >>> >>> -- >>> This message was sent by Atlassian JIRA >>> (v6.3.4#6332) >>
