[ensembl-dev] VEP differences in REST interface (grch37 vs grch38)

[Andrew Parton]

Hi,

Thanks for bringing this issue to our attention. This is an issue that was introduced with a recent bug fix, that should now have been resolved. 

If you find any more issues, please let us know.

Kind Regards,
Andrew

> On 4 Jun 2019, at 15:47, Wolf Beat <Beat.Wolf at hefr.ch> wrote:
> 
> Hi,
> 
> 
> i'm having an issue where several variants are missing MAF information in the grch37 rest api since the last release (they had the information previously).
> 
> 
> One example would be:
> 
> 
> http://grch37.ensembl.org/Homo_sapiens/Variation/Population?db=core;r=2:179616271-179617271;v=rs58651353;vdb=variation;vf=75079740
> 
> 
> This variants shows a MAF in multiple databases on the website, yet, in the REST API it does not:
> 
> http://grch37.rest.ensembl.org/vep/hsapiens/id/rs58651353?distance=0&content-type=application/json
> 
> 
> Yet, when accessing the latest rest backend, the information is present:
> 
> 
> http://rest.ensembl.org/vep/hsapiens/id/rs58651353?distance=0&content-type=application/json
> 
> 
> Are there additional parameters i have to set for the grch37 backend or is this a bug? I can give examples of more variants with that issue (eg. rs659243)
> 
> 
> Kind regards
> 
> 
> Beat Wolf
> 
> _______________________________________________
> Dev mailing list    Dev at ensembl.org
> Posting guidelines and subscribe/unsubscribe info: https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org
> Ensembl Blog: http://www.ensembl.info/