micomahesh1982
micomahesh1982
technically, csv_file = StringIO("""int__v|Decimal__v|Float__v|Boolean__v|String__v|Null__v|Date__v|Timestamp__v 1|43.4|11.02|True|'456'|12|2021-03-02|2019-08-07 10:11:12 2|101.4|11.128|False|'456'||2020-09-09|2019-05-04 11:12:13 3|43.4|13.02|True|'456'||2022-03-14|2012-08-07 10:15:12 4|202.4|14.128|False|'456'||2020-03-15|2017-09-04 11:17:13 5|43.4|11.02|True|'456'||2021-03-02|2019-08-07 10:11:12 6|101.4|11.128|False|'456'||2020-09-09|2019-05-04 11:12:13 7|43.4|13.02|True|'456'||2022-03-14|2012-08-07 10:15:12 8|202.4|14.128|False|'456'||2020-03-15|2017-09-04 11:17:13 9|43.4|11.02|True|'456'||2021-03-02|2019-08-07 10:11:12 10|101.4|11.128|False|'456'||2020-09-09|2019-05-04 11:12:13 11|43.4|13.02|True|'456'||2022-03-14|2012-08-07 10:15:12 12|202.4|14.128|False|'456'||2020-03-15|2017-09-04 11:17:13 13|101.4|11.128|False|'456'||2020-09-09|2019-05-04 11:12:13...
pyarrow==5.0.0; python_full_version >= "3.6.2" and python_version < "3.10" and python_version >= "3.6" - This is the pyarrow version being used in our project
couple of things i do explain here so that you may have visibility and provide me the solution which fits in this, (1) We have a source file like (CSV...
@abhishekrb19 Thanks for the update however i have provided all the issues in the slack channel. (1) There is no active ingestion for this datasource. Just the custom datasource meaning...
Thank you for your email however I’m not sure how to dynamically delete the ALL granular segments. Thanks, Regards, Mahesha S Cell:8015127140 On Thu, Mar 7, 2024 at 6:59 PM...
I see one more thing here, I see most of the time 1 segment for ALL granules then I can hardcode the interval: -146136543-09-08T08:23:32. 096Z/146140482-04-24T15:36:27.903Z however one more scenario, If...
Thank you Abhishek. On Mon, Mar 11, 2024 at 5:17 AM Abhishek Radhakrishnan < ***@***.***> wrote: > @micomahesh1982 , you can enable > auto-kill, please see these docs - >...
Sure thank you so much Regards, Mahesha S Cell:8015127140 On Wed, Mar 27, 2024 at 5:34 PM Abhishek Radhakrishnan < ***@***.***> wrote: > Closing this issue as the behavior was...