Cool... Thanks for looking into this Ian :)
Abdullah. > On Jan 19, 2018, at 3:28 PM, Ian Maxon <[email protected]> wrote: > > It's a bug, basically the issue is that NCService prunes out the > appropraite [extension] sections as they are transmitted to the CC. > This isn't caught by tests because in AsterixHyracksIntegrationUtil, > the config isn't run through the wringer of being transmitted from the > CC to the NCService to the NC; the CC's is given as an arg. I'm fixing > it. > > On Thu, Jan 18, 2018 at 11:32 PM, abdullah alamoudi <[email protected]> > wrote: >> Hi Steven, >> This indicates that the BAD metadata extension was not configured correctly. >> And so, the additional metadata indexes couldn't be found. >> >> I realize I am stating the obvious but have you tried configuring them? The >> other question is how come BAD built fine when this broke? >> Was it lacking test cases that use this statement? >> >>> On Jan 18, 2018, at 7:16 PM, Steven Jacobs <[email protected]> wrote: >>> >>> Hi all, >>> Managix was recently removed from Asterix, and the assumption was that >>> extension clusters could use NCService. This is not actually the case. The >>> cluster seems to start, but queries give strange errors about metadata >>> being missing. I filed an issue for this, >>> >>> https://issues.apache.org/jira/plugins/servlet/mobile#issue/ASTERIXDB-2239 >>> >>> The solution is unclear to me. >>> Steven >>
