You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@metamodel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/07/21 22:08:00 UTC

[jira] [Commented] (METAMODEL-1144) Join Performance

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

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

GitHub user tomatophantastico opened a pull request:

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

    Feature/faster join

    A simple nested loop join implementation to deal with METAMODEL-1144.
    
    This is an okay-ish solution:
    it maintains the results of the joins, but wont scale too well
    no join ordering or similar

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

    $ git pull https://github.com/tomatophantastico/metamodel feature/fasterJoin

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

    https://github.com/apache/metamodel/pull/148.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 #148
    
----
commit 65574d345bec251428868b24dc0f9322b3c93e14
Author: Jörg Unbehauen <jo...@unbehauen.net>
Date:   2017-07-20T15:01:02Z

    guava is now available in core

commit ee2b91671d8cb6b35046aabba8426724831b7205
Author: Jörg Unbehauen <jo...@unbehauen.net>
Date:   2016-05-03T10:34:03Z

    Simple nested loop join implementation

commit ef5ac06f17937365603e2be2eb1333c9d1407062
Author: Jörg Unbehauen <jo...@unbehauen.net>
Date:   2017-07-18T13:28:30Z

    Test cases for the join implementation

----


> Join Performance
> ----------------
>
>                 Key: METAMODEL-1144
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-1144
>             Project: Apache MetaModel
>          Issue Type: Improvement
>    Affects Versions: 5.0.0
>         Environment: Metamodel executed joins
>            Reporter: Joerg Unbehauen
>             Fix For: 5.0.0
>
>
> Whenever a join is executed by Metamodel in-memory, the execution method is rather inefficient and consumes a lot of memory and is slow.
> This is especially the case for CompositeDataContexts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)