[ 
https://issues.apache.org/jira/browse/METAMODEL-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969248#comment-14969248
 ] 

ASF GitHub Bot commented on METAMODEL-197:
------------------------------------------

GitHub user LosD opened a pull request:

    https://github.com/apache/metamodel/pull/61

    Let ElasticSearchDataContext read changes

    This adds the ability for ElasticSearchDataContext to read  tables on
     updates, to assure that an outside change is registered. To
     keep the ability to specify own mappings, any static mappings will
     be left alone.
    
    Fixes METAMODEL-197

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/LosD/metamodel master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/metamodel/pull/61.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #61
    
----
commit a374b0affec8c9cfd8e6226de923331230029584
Author: Dennis Du Krøger <[email protected]>
Date:   2015-10-22T14:44:38Z

    Let ElasticSearchDataContext read new tables
    
    This adds the ability for ElasticSearchDataContext to read  tables on
     updates, to assure that an outside change is registered. To
     keep the ability to specify own mappings, any static mappings will
     be left alone.
    
    Fixes METAMODEL-197

----


> ElasticSearch datacontext does not reload tables (ES document types)
> --------------------------------------------------------------------
>
>                 Key: METAMODEL-197
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-197
>             Project: Apache MetaModel
>          Issue Type: Improvement
>    Affects Versions: 4.4.0
>         Environment: N/A
>            Reporter: Dennis Du Krøger
>            Priority: Minor
>
> The ElasticSearchDataContext only has the capability to find mappings at 
> startup, which means that it is not possible to create a type/table and then 
> refresh the context.
> It would be nice to have the ES context work like the other contexts. The 
> hard-ish part is not losing the capability of providing a list of tables in 
> the process.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to