GitHub user jihoonson opened a pull request:

    https://github.com/apache/tajo/pull/714

    TAJO-1803: Use in-memory derby as the default catalog for unit tests

    

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

    $ git pull https://github.com/jihoonson/tajo-2 TAJO-1803

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

    https://github.com/apache/tajo/pull/714.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 #714
    
----
commit 199f164101cbe1185dfcc9cae151bcfe4ab30b48
Author: Jihoon Son <[email protected]>
Date:   2015-08-23T13:28:04Z

    testing

commit a1c9a6b3761f8d834b7eda3c471cd473e977c081
Author: Jihoon Son <[email protected]>
Date:   2015-08-26T01:38:06Z

    Merge branch 'mem_derby' of https://github.com/jihoonson/tajo-2 into 
mem_derby

commit 6db115b00a01cf3cc93b54c3a4cd6a81e6a2decb
Author: Jihoon Son <[email protected]>
Date:   2015-08-26T10:15:55Z

    success

commit 7a2f4aba1c0d691d0737e897620c76109555d4a6
Author: Jihoon Son <[email protected]>
Date:   2015-08-26T12:41:10Z

    Merge branch 'mem_derby' of https://github.com/jihoonson/tajo-2 into 
TAJO-1803

commit f6d564889dcd0a79106f373945d6926ba843651d
Author: Jihoon Son <[email protected]>
Date:   2015-08-26T14:46:32Z

    Replace MemStore with DerbyStore

commit c29cd501837b28e437c1d93421e71f841b06e16c
Author: Jihoon Son <[email protected]>
Date:   2015-08-27T09:46:17Z

    Enable external catalog

commit c971249a3e5634cbd0168b61aacac208cdf697bf
Author: Jihoon Son <[email protected]>
Date:   2015-08-28T10:07:01Z

    TAJO-1803

commit 9da53d4719e32a73b60a376fcf755d15288c7628
Author: Jihoon Son <[email protected]>
Date:   2015-08-28T13:27:43Z

    Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/tajo into 
TAJO-1803

commit bd68897d98ca7c95fbcb9c3ad82a96ea88ef1357
Author: Jihoon Son <[email protected]>
Date:   2015-08-29T02:01:59Z

    TAJO-1803

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to