Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

db2lucene and catalog2lucene produce different published dates #5435

Open
joelverhagen opened this issue Feb 12, 2018 · 0 comments
Open

db2lucene and catalog2lucene produce different published dates #5435

joelverhagen opened this issue Feb 12, 2018 · 0 comments

Comments

@joelverhagen
Copy link
Member

When db2lucene is run, all unlisted packages get a real published timestamp.

When catalog2lucene is run, an unlisted package gets a published date of 1900-01-01T00:00:00.0000000+00:00.

Throughout all of our endpoints, unlisted packages have published date of 1900. We should be consistent here and fix db2lucene.

joelverhagen added a commit to NuGet/NuGet.Services.Metadata that referenced this issue Nov 8, 2018
joelverhagen added a commit to NuGet/NuGet.Services.Metadata that referenced this issue Nov 8, 2018
joelverhagen added a commit to NuGet/NuGet.Services.Metadata that referenced this issue Nov 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants