EmilySChoy commented on issue #34689:
URL: https://github.com/apache/arrow/issues/34689#issuecomment-1482699593

   11.0.0.3 
   
   Hi @EmilySChoy, thanks for reporting this!
   > 
   > I'm afraid that's not quite enough information for us to be able to help 
easily. If the dataset is publicly available, can you show us all of the code 
you ran to access it? Also, which version of Arrow are you using? You can get 
that info by running `arrow::arrow_info()`.
   > 
   > It sounds like there is a segfault when you run the code, which causes R 
to abort. This makes it trickier to get error message out for reporting issues. 
One other possible thing to try is running the code from a session with the 
debugger attached, to get a more complete error message: 
https://arrow.apache.org/docs/r/articles/developers/debugging.html
   > 
   > Just to check; if you just run
   > 
   > ```
   > gps %>%  filter( dep_id %in% dd, # Only dep_ids from our list dd deployed 
== 1 # only data collected on the bird ) %>%  collect()
   > ```
   > 
   > does that work without any issues?
   
   
   Thank you @thisisnic 
   
   The data is on a private online AWS cloud for my lab. The arrow version I 
have is 11.0.0.3
   
   The code you have provided works without any issues. I get:
   FileSystemDataset (query)
   time: timestamp[us, tz=UTC]
   lon: double
   lat: double
   altitude_m: int32
   satellites: int32
   hdop: double
   inrange: bool
   site: string
   subsite: string
   species: string
   year: int32
   metal_band: int32
   dep_id: string
   deployed: int32
   
   * Filter: is_in(dep_id, {value_set=string:[
     "wewws_18May2019",
     "bsgwg_18May2019",
     "bowys_18May2019",
     "yogys_18May2019",
     "ysebg_18May2019",
     "ysrro_18May2019",
     "A26_rswbg_8May2022",
     "A35_bwwbs_7May2022",
     "A49_owrrs_7May2022",
     "A62_ysgeo_8May2022",
     "A61_esgbg_8May2022",
     "A70_eybbs_8May2022"
   ], skip_nulls=true})
   See $.data for the source Arrow object


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to