This is the last error to fix. I don't quite understand the error and need help on this, @houqp

error: implementation of `graphql_parser::common::Text` is not general enough
   --> roapi/src/context.rs:124:68
    |
124 |       ) -> Result<Vec<arrow::record_batch::RecordBatch>, QueryError> {
    |  ____________________________________________________________________^
125 | |         self.cq.query_graphql(query).await
126 | |     }
    | |_____^ implementation of `graphql_parser::common::Text` is not general enough
    |
    = note: `graphql_parser::common::Text<'1>` would have to be implemented for the type `&'0 str`, for any two lifetimes `'0` and `'1`...
    = note: ...but `graphql_parser::common::Text<'2>` is actually implemented for the type `&'2 str`, for some specific lifetime `'2`

not obvious to me why this is happening yet, will have to take a closer look 🤔

Thanks, I also take a look and have no idea...

This is the last error to fix. I don't quite understand the error and need help on this, @houqp

error: implementation of `graphql_parser::common::Text` is not general enough
   --> roapi/src/context.rs:124:68
    |
124 |       ) -> Result<Vec<arrow::record_batch::RecordBatch>, QueryError> {
    |  ____________________________________________________________________^
125 | |         self.cq.query_graphql(query).await
126 | |     }
    | |_____^ implementation of `graphql_parser::common::Text` is not general enough
    |
    = note: `graphql_parser::common::Text<'1>` would have to be implemented for the type `&'0 str`, for any two lifetimes `'0` and `'1`...
    = note: ...but `graphql_parser::common::Text<'2>` is actually implemented for the type `&'2 str`, for some specific lifetime `'2`

I solved this by removing explicit lifetimes and changing the &str to String. Not sure if this is the recommended way, the rust experts can guide me here.

@jychen7 @houqp @rtyler I have a local branch where I have successfully upgraded roapi to the latest versions of datafusion, arrow and delta-rs, along with some other minor upgrades were required.

shall I raise a PR for it?

Sorry @jychen7 that I dropped the ball on this one ;(

@chitralverma please feel free to send a new MR

I am sorry that I don't have time to look into this recently, but I could try best to help review

feel free to raise a PR. I will close this one after that

Done !
#275