weaviate / weaviate-graphql-prototype

weaviate-graphql-prototype
1 stars 2 forks source link

add the option to fuzzy search in network by only ontology value #32

Open laura-ham opened 5 years ago

laura-ham commented 5 years ago

In the current design, at least the class and property name should be defined to search for property values (Network Fetch search). This issue proposes to give the option to do a fuzzy search by only providing a property value.

The ontology value should be in the contextionary to find Things/Actions in the whole network. (otherwise too search intensive)

bobvanluijt commented 5 years ago

@laura-ham not sure what the current status is on this one. Can you please share?

laura-ham commented 5 years ago

@laura-ham not sure what the current status is on this one. Can you please share?

@bobvanluijt opened this issue following yesterday's call about the Playground, haven't designed nor implemented this yet.

laura-ham commented 5 years ago
{
  Network{
    Fetch{
      Fuzzy(value:"Amsterdam", certainty:0.9){ // value is always a string, because needs to be in contextionary
        beacon
        certainty
      }
    }
  }
}

Designed as part of Fetch. In the current Fetch design there is only the possibility to return the beacon and certainty. Then the ontology information can be found by doing the introspect function.

@bobvanluijt shall we keep it like this or do we want to give ontology information (classname, property name) as well as a result of Fetch?

bobvanluijt commented 5 years ago

Hi @laura-ham,

I would argue for only working with the beacon and allowing to request more information about the beacon. This because a beacon means something differently per Weaviate instance.