Mailing-List: contact dev-help@asterixdb.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@asterixdb.incubator.apache.org
Subject: Re: Proposal for adding test name resolver for NC names and HDFS
 NameNode names
To: dev@asterixdb.incubator.apache.org
References: 
 <CAN_YF5yfwYqt0DtybU8tS_khjues=N6jN2sY5r79VbgHqPJfJg@mail.gmail.com>
From: Mike Carey <dtabass@gmail.com>
Message-ID: <56AC0AF9.9030904@gmail.com>
Date: Fri, 29 Jan 2016 16:59:37 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0)
 Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: 
 <CAN_YF5yfwYqt0DtybU8tS_khjues=N6jN2sY5r79VbgHqPJfJg@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------070703010305020208070303"

--------------070703010305020208070303
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

+1   :-)

On 1/29/16 12:37 PM, Ian Maxon wrote:
> Hi all,
> Murtadha, Till, Abdullah and I all were discussing the best way to resolve
> the issue with how to provide the location of the HDFS namenode to external
> indexing queries in test cases, without having to change the queries
> themselves.
>
> The proposed solution (as I understood it... :) ) is to basically come up
> with a new name resolver, akin to the DNSResolver and IdentityResolver in
> Hyracks, but will allow for arbitrary mappings of strings to IPs akin to a
> host file. This will be used both in the NC name resolution and the
> external indexing adapter configuration.
> By default this will be disabled, everything will still use DNSResolver by
> default in normal instances. However this resolver will be available and
> possible to enable (again, mainly for testing's sake) in the
> asterix-configuration.xml properties.
>
> Please feel free to comment! In the meantime, I will start implementing
> this so it can unblock the use of external indexing queries in
> ClusterExecutionIT.
>
> Thanks,
> - Ian
>


--------------070703010305020208070303--