Hi, I executed the 'timeline API' to the table 'A' several days ago with 'DOCUMENTATION' category and got the history of adding/modifying it (as the first figure shows). But today doing same work to 'A' got response with empty dictionary like the second figure. What's strange is that all tables from postrgres got the same result. Other tables from types except postgres such as hive showed the history well. Why those problems occur?

I would probably inspect the database to ensure that the historical aspects are still there inside metadata_aspect_v2 table

@better-orange-49102 You mean, entering mysql docker and connect datahub inside it? After connection, how to inspect whether historical aspects exist or not?

Records have urn as key. Check the version of the aspects to see if older versions (aka version=!0 records) exist or not

@better-orange-49102 I found the row which is impossible to get by api. The first figure is the screenshot captured before. and the second one shows urn, version (11), aspect (editableschemametadat) and timestamp. I'm convinced that they are the same since timestamp is equal (converting unix time stamp). In summary, the records are in metadata_aspect_v2 table but using api can't get it now.

@astonishing-answer-96712 appears that the timeline API glitched in this case

Hi @better-orange-49102, thanks for the heads up!

Are you using the default start & end timestamps? By default we only do a week lookback. Try it with startTimeMillis = 0 instead of -1

@orange-night-91387 Thanks! After changing the value of startime to 0, the result came out. One more question : how to set the endtime to 'current date'?

That's the default, 0 -> current time for end time millis