Edges are not found if filtered by correct label

[mrckzgl]

Consider this jruby example:

test_query = QueryBuilder.new("Work", params[:search_type], params[:search], search_additional).query
puts test_query
test_result = test_query.project('authors')
  .by(T.out_e().element_map())
  .to_list()
test_result.each{|v| puts v }

If executed against a very simple query, just filtering by search_nodetype property on a test dataset the result is:

[GraphStep(vertex,[]), HasStep([search_nodetype.textContains(Work)])]
{authors={id=1st1-2my0-1g5x-3ils, label=authors, IN={id=164080, label=vertex}, OUT={id=123048, label=vertex}}}
{authors={id=2bdb-3c6w-1g5x-23zs, label=authors, IN={id=98488, label=vertex}, OUT={id=155768, label=vertex}}}
{authors={id=1z4g-32ps-1g5x-3fg0, label=authors, IN={id=159984, label=vertex}, OUT={id=143488, label=vertex}}}
{authors={id=2v4u-3ca8-1gyd-2zhk, label=authors, IN={id=139304, label=vertex}, OUT={id=155888, label=vertex}}}
{authors={id=1ssx-2glk-1hqt-2wd4, label=authors, IN={id=135256, label=vertex}, OUT={id=114824, label=vertex}}}
{authors={id=29sb-2t7c-1ij9-32nc, label=authors, IN={id=143400, label=vertex}, OUT={id=131160, label=vertex}}}

So each found vertex has an out edge with label 'authors' which is found.
Now I only change the project query to filter for out edges with 'authors' as label like this:

test_result = test_query.project('authors')
  .by(T.out_e('authors').element_map())
  .to_list()

The result should be identical, but it is not:

[GraphStep(vertex,[]), HasStep([search_nodetype.textContains(Work)])]
{authors={id=1st1-2my0-1g5x-3ils, label=authors, IN={id=164080, label=vertex}, OUT={id=123048, label=vertex}}}
{authors={id=2bdb-3c6w-1g5x-23zs, label=authors, IN={id=98488, label=vertex}, OUT={id=155768, label=vertex}}}
{authors={id=1z4g-32ps-1g5x-3fg0, label=authors, IN={id=159984, label=vertex}, OUT={id=143488, label=vertex}}}
{authors=null}
{authors=null}
{authors=null}

Am I missing something or is this a bug in JanusGraph?

best

[mrckzgl]

Ok, we were experiencing this in JanusGraph 0.6.3. Now upgraded to 1.0.0 and for our test case above the problem seems not to happen anymore.