Hadoop 无法从配置单元客户端找到由oozie配置单元操作创建的表，但可以在HDFS中找到它们

我正在尝试通过Oozie配置单元操作运行配置单元脚本，我刚刚在script.q中创建了一个配置单元表“test”，并且Oozie作业成功运行，我可以在hdfs path/user/hive/warehouse下找到Oozie作业创建的表。但我无法通过配置单元客户端中的“showtables”命令找到“test”表

我认为我的metastore配置有问题，但我就是想不出来。 有人能帮忙吗

oozie admin -oozie http://localhost:11000/oozie -status

系统模式：正常

oozie job -oozie http://localhost:11000/oozie -config C:\Hadoop\oozie-3.2.0-incubating\oozie-win-distro\examples\apps\hive\job.properties -run

作业ID:0000001-130910094106919-oozie-hado-W

这是我的oozie-site.xml

---

除非适用法律要求或书面同意，软件 根据许可证进行的分发是按“原样”进行分发的， 无任何明示或暗示的保证或条件。 请参阅许可证以了解管理权限和权限的特定语言 许可证下的限制。 -->

oozie.service.ActionService.executor.ext.classes
org.apache.oozie.action.email.EmailActionExecutor，
org.apache.oozie.action.hadoop.HiveActionExecutor，
org.apache.oozie.action.hadoop.ShellActionExecutor，
org.apache.oozie.action.hadoop.SqoopActionExecutor
oozie.service.SchemaService.wf.ext.schemas
shell-action-0.1.xsd、email-action-0.1.xsd、hive-action-0.2.xsd、sqoop-action-0.2.xsd、ssh-action-0.1.xsd
oozie.system.id
oozie-${user.name}
Oozie系统ID。
oozie.systemmode
正常的
启动时Oozie的系统模式。
oozie.service.AuthorizationService.security.enabled
假的
指定是否启用安全性（用户名/管理员角色）。
如果禁用，任何用户都可以管理Oozie系统和任何作业。
oozie.service.PurgeService.older.than
30
PurgeService将清除早于此值（以天为单位）的作业。
oozie.service.PurgeService.purge.interval
3600
清除服务将运行的间隔（秒）。
oozie.service.CallableQueueService.queue.size
10000
最大可调用队列大小
oozie.service.CallableQueueService.threads
10
用于执行可调用项的线程数
oozie.service.CallableQueueService.callable.concurrency
3.
给定可调用类型的最大并发性。
每个命令都是可调用类型（提交、启动、运行、发送信号、作业、作业、挂起、恢复等）。
每个操作类型都是可调用的类型（Map Reduce、Pig、SSH、FS、子工作流等）。
所有使用动作执行器（动作开始、动作结束、动作终止和动作检查）的命令都使用
将操作类型设置为可调用类型。
oozie.service.coord.normal.default.timeout
120
正常作业的协调器操作输入检查的默认超时（分钟）。
-1表示无限超时
oozie.db.schema.name
奥齐
Oozie数据库名称
oozie.service.JPAService.create.db.schema
真的
创建Oozie数据库。
如果设置为true，则会在数据库架构不存在时创建它。如果数据库模式存在，则为NOP。
如果设置为false，则不会创建DB架构。如果数据库模式不存在，则启动失败。
oozie.service.JPAService.jdbc.driver
org.apache.derby.jdbc.EmbeddedDriver
JDBC驱动程序类。
oozie.service.JPAService.jdbc.url
jdbc:derby:${oozie.data.dir}/${oozie.db.schema.name}-db；create=true
JDBCURL。
oozie.service.JPAService.jdbc.username
sa
数据库用户名。
oozie.service.JPAService.jdbc.password
pwd
数据库用户密码。
重要提示：如果密码为emtpy，请留下一个1空格字符串，则服务会修剪该值，
如果为空，则配置假定为空。
oozie.service.JPAService.pool.max.active.conn
10
最大连接数。
oozie.service.HadoopAccessorService.kerberos.enabled
假的
指示Oozie是否配置为使用Kerberos。
本地域
本地主机
Oozie和Hadoop使用的Kerberos领域。使用“local.realm”与Hadoop配置保持一致
oozie.service.HadoopAccessorService.keytab.file
${user.home}/oozie.keytab
Oozie用户密钥表文件的位置。
oozie.service.HadoopAccessorService.kerberos.principal
${user.name}/localhost@${local.realm}
Oozie服务的Kerberos主体。
oozie.service.HadoopAccessorService.jobTracker.whitelist
Oozie服务的白名单工作跟踪器。
oozie.service.HadoopAccessorService.nameNode.whitelist
Oozie服务的白名单工作跟踪器。
oozie.service.HadoopAccessorService.hadoop.configurations
*=hadoop conf
逗号分隔的AUTHORITY=HADOOP_CONF_DIR，其中AUTHORITY是主机：端口
Hadoop服务（JobTracker，HDFS）。通配符“*”配置无效
当权威没有完全匹配时使用。HADOOP_CONF_目录包含
相关的Hadoop*-site.xml文件。如果路径是相对的，则在内部查找
Oozie配置目录；虽然路径可以是绝对的（即指向点
到本地文件系统中的Hadoop客户端conf/目录。
oozie.service.WorkflowAppService.system.libpath
/user/${user.name}/share/lib
用于工作流应用程序的系统库路径。
如果作业属性已设置，则此路径将添加到工作流应用程序
将属性“oozie.use.system.libpath”设置为true。
使用.system.libpath.for.mapreduce.and.pig.jobs
假的
如果设置为true，则MapReduce和Pig作业的提交将包括
自动设置系统库路径，因此不需要用户
指定Pig JAR文件的位置.Inste
   http://www.apache.org/licenses/LICENSE-2.0

<!--
    Refer to the oozie-default.xml file for the complete list of
    Oozie configuration properties and their default values.
-->

<property>
    <name>oozie.service.ActionService.executor.ext.classes</name>
    <value>
        org.apache.oozie.action.email.EmailActionExecutor,
        org.apache.oozie.action.hadoop.HiveActionExecutor,
        org.apache.oozie.action.hadoop.ShellActionExecutor,
        org.apache.oozie.action.hadoop.SqoopActionExecutor
    </value>
</property>

<property>
    <name>oozie.service.SchemaService.wf.ext.schemas</name>
    <value>shell-action-0.1.xsd,email-action-0.1.xsd,hive-action-0.2.xsd,sqoop-action-0.2.xsd,ssh-action-0.1.xsd</value>
</property>

<property>
    <name>oozie.system.id</name>
    <value>oozie-${user.name}</value>
    <description>
        The Oozie system ID.
    </description>
</property>

<property>
    <name>oozie.systemmode</name>
    <value>NORMAL</value>
    <description>
        System mode for  Oozie at startup.
    </description>
</property>

<property>
    <name>oozie.service.AuthorizationService.security.enabled</name>
    <value>false</value>
    <description>
        Specifies whether security (user name/admin role) is enabled or not.
        If disabled any user can manage Oozie system and manage any job.
    </description>
</property>

<property>
    <name>oozie.service.PurgeService.older.than</name>
    <value>30</value>
    <description>
        Jobs older than this value, in days, will be purged by the PurgeService.
    </description>
</property>

<property>
    <name>oozie.service.PurgeService.purge.interval</name>
    <value>3600</value>
    <description>
        Interval at which the purge service will run, in seconds.
    </description>
</property>

<property>
    <name>oozie.service.CallableQueueService.queue.size</name>
    <value>10000</value>
    <description>Max callable queue size</description>
</property>

<property>
    <name>oozie.service.CallableQueueService.threads</name>
    <value>10</value>
    <description>Number of threads used for executing callables</description>
</property>

<property>
    <name>oozie.service.CallableQueueService.callable.concurrency</name>
    <value>3</value>
    <description>
        Maximum concurrency for a given callable type.
        Each command is a callable type (submit, start, run, signal, job, jobs, suspend,resume, etc).
        Each action type is a callable type (Map-Reduce, Pig, SSH, FS, sub-workflow, etc).
        All commands that use action executors (action-start, action-end, action-kill and action-check) use
        the action type as the callable type.
    </description>
</property>

<property>
    <name>oozie.service.coord.normal.default.timeout
    </name>
    <value>120</value>
    <description>Default timeout for a coordinator action input check (in minutes) for normal job.
        -1 means infinite timeout</description>
</property>

<property>
    <name>oozie.db.schema.name</name>
    <value>oozie</value>
    <description>
        Oozie DataBase Name
    </description>
</property>

<property>
    <name>oozie.service.JPAService.create.db.schema</name>
    <value>true</value>
    <description>
        Creates Oozie DB.

        If set to true, it creates the DB schema if it does not exist. If the DB schema exists is a NOP.
        If set to false, it does not create the DB schema. If the DB schema does not exist it fails start up.
    </description>
</property>

<property>
    <name>oozie.service.JPAService.jdbc.driver</name>
    <value>org.apache.derby.jdbc.EmbeddedDriver</value>
    <description>
        JDBC driver class.
    </description>
</property>

<property>
    <name>oozie.service.JPAService.jdbc.url</name>
    <value>jdbc:derby:${oozie.data.dir}/${oozie.db.schema.name}-db;create=true</value>
    <description>
        JDBC URL.
    </description>
</property>

<property>
    <name>oozie.service.JPAService.jdbc.username</name>
    <value>sa</value>
    <description>
        DB user name.
    </description>
</property>

<property>
    <name>oozie.service.JPAService.jdbc.password</name>
    <value>pwd</value>
    <description>
        DB user password.

        IMPORTANT: if password is emtpy leave a 1 space string, the service trims the value,
                   if empty Configuration assumes it is NULL.
    </description>
</property>

<property>
    <name>oozie.service.JPAService.pool.max.active.conn</name>
    <value>10</value>
    <description>
         Max number of connections.
    </description>
</property>

<property>
    <name>oozie.service.HadoopAccessorService.kerberos.enabled</name>
    <value>false</value>
    <description>
        Indicates if Oozie is configured to use Kerberos.
    </description>
</property>

<property>
    <name>local.realm</name>
    <value>LOCALHOST</value>
    <description>
        Kerberos Realm used by Oozie and Hadoop. Using 'local.realm' to be aligned with Hadoop configuration
    </description>
</property>

<property>
    <name>oozie.service.HadoopAccessorService.keytab.file</name>
    <value>${user.home}/oozie.keytab</value>
    <description>
        Location of the Oozie user keytab file.
    </description>
</property>

<property>
    <name>oozie.service.HadoopAccessorService.kerberos.principal</name>
    <value>${user.name}/localhost@${local.realm}</value>
    <description>
        Kerberos principal for Oozie service.
    </description>
</property>

<property>
    <name>oozie.service.HadoopAccessorService.jobTracker.whitelist</name>
    <value> </value>
    <description>
        Whitelisted job tracker for Oozie service.
    </description>
</property>

<property>
    <name>oozie.service.HadoopAccessorService.nameNode.whitelist</name>
    <value> </value>
    <description>
        Whitelisted job tracker for Oozie service.
    </description>
</property>

<property>
    <name>oozie.service.HadoopAccessorService.hadoop.configurations</name>
    <value>*=hadoop-conf</value>
    <description>
        Comma separated AUTHORITY=HADOOP_CONF_DIR, where AUTHORITY is the HOST:PORT of
        the Hadoop service (JobTracker, HDFS). The wildcard '*' configuration is
        used when there is no exact match for an authority. The HADOOP_CONF_DIR contains
        the relevant Hadoop *-site.xml files. If the path is relative is looked within
        the Oozie configuration directory; though the path can be absolute (i.e. to point
        to Hadoop client conf/ directories in the local filesystem.
    </description>
</property>

<property>
    <name>oozie.service.WorkflowAppService.system.libpath</name>
    <value>/user/${user.name}/share/lib</value>
    <description>
        System library path to use for workflow applications.
        This path is added to workflow application if their job properties sets
        the property 'oozie.use.system.libpath' to true.
    </description>
</property>

<property>
    <name>use.system.libpath.for.mapreduce.and.pig.jobs</name>
    <value>false</value>
    <description>
        If set to true, submissions of MapReduce and Pig jobs will include
        automatically the system library path, thus not requiring users to
        specify where the Pig JAR files are. Instead, the ones from the system
        library path are used.
    </description>
</property>

<property>
    <name>oozie.authentication.type</name>
    <value>simple</value>
    <description>
        Defines authentication used for Oozie HTTP endpoint.
        Supported values are: simple | kerberos | #AUTHENTICATION_HANDLER_CLASSNAME#
    </description>
</property>

<property>
    <name>oozie.authentication.token.validity</name>
    <value>36000</value>
    <description>
        Indicates how long (in seconds) an authentication token is valid before it has
        to be renewed.
    </description>
</property>

<property>
    <name>oozie.authentication.signature.secret</name>
    <value>oozie</value>
    <description>
        The signature secret for signing the authentication tokens.
        If not set a random secret is generated at startup time.
        In order to authentiation to work correctly across multiple hosts
        the secret must be the same across al the hosts.
    </description>
</property>

<property>
  <name>oozie.authentication.cookie.domain</name>
  <value></value>
  <description>
    The domain to use for the HTTP cookie that stores the authentication token.
    In order to authentiation to work correctly across multiple hosts
    the domain must be correctly set.
  </description>
</property>

<property>
    <name>oozie.authentication.simple.anonymous.allowed</name>
    <value>true</value>
    <description>
        Indicates if anonymous requests are allowed.
        This setting is meaningful only when using 'simple' authentication.
    </description>
</property>

<property>
    <name>oozie.authentication.kerberos.principal</name>
    <value>HTTP/localhost@${local.realm}</value>
    <description>
        Indicates the Kerberos principal to be used for HTTP endpoint.
        The principal MUST start with 'HTTP/' as per Kerberos HTTP SPNEGO specification.
    </description>
</property>

<property>
    <name>oozie.authentication.kerberos.keytab</name>
    <value>${oozie.service.HadoopAccessorService.keytab.file}</value>
    <description>
        Location of the keytab file with the credentials for the principal.
        Referring to the same keytab file Oozie uses for its Kerberos credentials for Hadoop.
    </description>
</property>

<property>
    <name>oozie.authentication.kerberos.name.rules</name>
    <value>DEFAULT</value>
    <description>
        The kerberos names rules is to resolve kerberos principal names, refer to Hadoop's
        KerberosName for more details.
    </description>
</property>

<!-- Proxyuser Configuration -->

<!--

<property>
    <name>oozie.service.ProxyUserService.proxyuser.#USER#.hosts</name>
    <value>*</value>
    <description>
        List of hosts the '#USER#' user is allowed to perform 'doAs'
        operations.

        The '#USER#' must be replaced with the username o the user who is
        allowed to perform 'doAs' operations.

        The value can be the '*' wildcard or a list of hostnames.

        For multiple users copy this property and replace the user name
        in the property name.
    </description>
</property>

<property>
    <name>oozie.service.ProxyUserService.proxyuser.#USER#.groups</name>
    <value>*</value>
    <description>
        List of groups the '#USER#' user is allowed to impersonate users
        from to perform 'doAs' operations.

        The '#USER#' must be replaced with the username o the user who is
        allowed to perform 'doAs' operations.

        The value can be the '*' wildcard or a list of groups.

        For multiple users copy this property and replace the user name
        in the property name.
    </description>
</property>

-->