Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Unable to query data between timestamp with cf-java-client

Open
#835 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
api, backend

Research direction

Start with the events().list flow and ListEventsRequest, then compare its timestamp handling with the REST /v2/events query shown in the issue. Add support for a bounded timestamp range and verify that requests can represent both the start and end dates shown in the example.

Written by the indexing model from the issue text.

Description

client enhancement triaged

Hi,

I am trying to query the /v1/events api using the java client, but there is no provision to query for a particular range with timestamp. Below is the code,

cloudFoundryClient.events()
  .list(ListEventsRequest.builder()
    .timestamp(startDate)
    .build())

Say if startDate is 2017-11-01, then java api gives the response from 2017-11-01 to current date (2017-11-21).

But the range is supported when I try to consume it via REST client.

/v2/events?order-by=timestamp&order-by=id&order-direction=asc&q=timestamp>=2017-11-01&q=timestamp<=2017-11-03

Could you please help on this ?

Thanks
Sundar

Dominant language
Java
Stars
334
Forks
319
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudfoundry/cf-java-client

All issues in cloudfoundry/cf-java-client

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.