3 ms·

> That said, we evaluated TileDB for genomics recently and found it lacking for our use case. Could you share what solution you landed on instead?

• aroch 6y ago
  Hail.is is what we landed on. There are some things we don't like with it too but weren't deal breakers
  • stavrospap 6y ago
    TileDB and Hail are rather complementary. We have customers that use TileDB to store and manage their variants, and Hail to perform GWAS (by exporting from TileDB to Hail format). We are currently designing a tighter integration with Hail. This expands on our vision for a universal data engine that integrates with pretty much everything out there and does not lock you in a single framework (e.g., Spark).
    • aroch 6y ago
      That was our feeling about the two products as well, the limitations w/ TileDB-vcf though sort of forced our hands. I was (and still am) of the opinion TileDB would be a good variant store since it does do so many of the things we want and does them well
  • johnc1231 6y ago
    Hail team member here. I'd be curious to hear what the things you don't like about hail are. Hopefully they're things that are already on our road map