Yes, it indeed appears to be a regex issue. If I run:
partial_name=re.escape('[LTV] Dataset Test'),
It works as expected. I'm not sure how raw you want to leave the partial_name features. I could create a PR to fix this but would you want me to re.escape at the
list_datasets() level? Or go deeper and do it at
Hi @<1545216070686609408:profile|EnthusiasticCow4> ! Note that the
Datasets section is created only if you get the dataset with an alias? are you sure that
number_of_datasets_on_remote != 0 ?
If so, can you provide a short snippet that would help us reproduce? The code you posted looks fine to me, not sure what the problem could be.
I see. Thanks for the insight. That seems to be the case. I'm struggling a bit with datasets. For example, if I wanted to trace the genealogy of a dataset that's used by traditional tasks and pipelines. I'll try and write something up about the challenges around that when I get the chance. But your comment revealed another issue:
It appears that the partial name matching isn't going well. I'm unclear why this wouldn't be matching. In the attached photo you can see the input for
'[LTV] Dataset Test'
and you can see from the unfiltered search there are many datasets titled identically. Yet, with that search criteria I get 0 results. One would assume that a partial match would include perfect matches?
The plot thickens. It seems like there's something odd going on with the interaction between
[LTV] and additional text. If I just search
[LTV] it works, if I just search
Dataset Test it works, but if I put them together it breaks the search. Now that I think about it, there's other oddities that seem to happen in the web interface that might be explained by some bugs around using brackets in names.