Hi Dev, In the last year or so I have been more involved in AsterixDB. However, I'm 90% user and 10% developer (due to the nature of my work). I want to share some of my (and my colleagues) experience with ADM. However, I might be too obvious.
One of the challenges we face most of the time is Indexing non-ADM data. Most of the data are either in JSON or CSV format which mean all ADM richness are not usable. For instance in load, I usually create External (or Temporary) Dataset, query/transform and then insert it to my Internal Dataset, which takes more time compared with load, as a result of flush/merge operations. Another challenging case, The TwitterFeed example <https://ci.apache.org/projects/asterixdb/feeds/tutorial.html>, the *longitude* and *latitude* fields are not indexable and I need to ETL to another dataset to transform (lon,lat) to a point type*.* It would be awesome if we can bridge non-ADM to ADM types. -- *Regards,* Wail Alkowaileet
