Re: [Bigdata-developers] InlineURIFactory change

[Bryan T. <br...@sy...>]

It is going to me more efficient to have lookup by namespace in a map
rather than scanning a list, which is why I made this change. At the time
that I made it I was not thinking about the impact on the WDQS.  Can you
split up your handler into one handler per namespace or does that cause
problems?

Thanks,
Bryan

----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://blazegraph.com
http://blog.blazegraph.com

Blazegraph™ <http://www.blazegraph.com/> is our ultra high-performance
graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints
APIs.  Blazegraph is now available with GPU acceleration using our disruptive
technology to accelerate data-parallel graph analytics and graph query.

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

On Wed, Jan 6, 2016 at 6:37 PM, Stas Malyshev <sma...@wi...>
wrote:

> Hi!
>
> > Could you register the same handler multiple times, once for each
> namespace?
>
> No, because it indexes by handler.getNamespace() and this can return
> only one value:
>
>     protected void addHandler(final InlineURIHandler handler) {
>
>         //        this.handlers.add(handler);
>         handlersByNamespace.put(handler.getNamespace(), handler);
>     }
>
> --
> Stas Malyshev
> sma...@wi...
>