Mailing-List: contact dev-help@zest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zest.apache.org
Date: Thu, 9 Jul 2015 15:25:05 +0000 (UTC)
From: "Paul Merlin (JIRA)" <jira@apache.org>
To: dev@zest.apache.org
Message-ID: <JIRA.12838029.1434424796000.143603.1436455505284@Atlassian.JIRA>
In-Reply-To: <JIRA.12838029.1434424796000@Atlassian.JIRA>
References: <JIRA.12838029.1434424796000@Atlassian.JIRA>
 <JIRA.12838029.1434424796435@arcas>
Subject: [jira] [Updated] (ZEST-31) ElasticSearch Query dereferences
 Associations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ZEST-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Merlin updated ZEST-31:
----------------------------
    Affects Version/s: 2.0

> ElasticSearch Query dereferences Associations
> ---------------------------------------------
>
>                 Key: ZEST-31
>                 URL: https://issues.apache.org/jira/browse/ZEST-31
>             Project: Zest
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Niclas Hedhman
>
> I think there is a problem in the ElasticSearch Query system, when it comes to handling Associations. I haven't investigated yet, but it tried to dereference the EntityReference of an Association, which of course causes an EntityTypeNotFoundException, since originating Module is down in the Infra Layer.


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