_link_ doesn't work as expected for joined resources in tables

[rsinger]

If your tablespec has something like:

{
"id" : "t_foo",
"from" : "barCollection",
"joins" : {
    "foo:bar" :  {
        "from" : "fooCollection",
        "fields" : [
           {
                "fieldName" : "fooLink",
                "predicates" : [""],
                "value" : "_link_"
           }]
    }
}
}

"fooLink" will be populated from barCollection._id.r

In searchDocument, it appears that it would correctly populate fooLink from fooCollection._id.r

[scaleupcto]

Should we also consider allowing

{
  "fieldName":"fooLink",
  "value":"_link_"
}

to be functionally equivalent to:

{
  "fieldName":"fooLink",
  "predicates":[""],
  "value":"_link_"
}

[rsinger]

I'm not sure I'm familiar enough with tripod to answer that.

The current behavior, as I understand it, is that "predicates" is always required. It seems like you're satisfying that requirement by supplying a "value". What happens if "value" is something other than "link"?

[rsinger]

That said, this conversation seems more appropriate for #15. This issue is really just to align table spec behavior with search spec behavior.

[scaleupcto]

Wherever fixed, predicates:[""] is just boulderdash to fix config validation. Even predicates:["_self_"] would be better. Infact, that would be really nice as you could mix it with other predicates: predicates:["_self_","resourcelists:createdBy"]

[scaleupcto]

Can this be closed?