ordingly and you must provide your checklist for your
> > vote**.
> >
> >
> > [ ] +1 approve
> >
> > [ ] +0 no opinion
> >
> > [ ] -1 disapprove with the reason
> >
> > Checklist:
> >
> > [ ] Download links are valid.
> >
> > [ ] Checksums and PGP signatures are valid.
> >
> > [ ] Source code artifacts have correct names matching the current
> release.
> >
> > For a detailed checklist please refer to:
> >
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
>
--
Adam Binford
artifacts here:
> https://repository.apache.org/content/groups/staging/org/apache/sedona/
> . I'll pay attention to this `--packages` use case in future releases.
>
> On Thu, Oct 12, 2023 at 8:08 PM Adam Binford wrote:
> >
> > Noticed on the now released 1.5.0, sedona-common depends on
>
addition, ASF's voting process is mainly focused on voting the
> > > source code. Binary is just a convenience release for users, no hard
> > > requirements on it.
> > >
> > > Please let me know if this makes sense to you. Or, if you have
> > > suggestions, please also advise.
> > >
> > > Thanks,
> > > Jia
> >
>
--
Adam Binford
; source code. Binary is just a convenience release for users, no hard
> requirements on it.
>
> Please let me know if this makes sense to you. Or, if you have
> suggestions, please also advise.
>
> Thanks,
> Jia
>
> On Tue, Oct 10, 2023 at 5:35 AM Adam Binford wrote:
> >
ps://mybinder.org/v2/gh/jiayuasu/sedona-tools/HEAD?labpath=binder%2Fverify-release.ipynb
> > >
> > > **Please vote accordingly and you must provide your checklist for your
> > vote**.
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > Checklist:
> > > [ ] Download links are valid.
> > > [ ] Checksums and PGP signatures are valid.
> > > [ ] Source code artifacts have correct names matching the current
> > release.
> > >
> > > For a detailed checklist please refer to:
> > >
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> > >
> > > Thanks,
> > > Jia
> >
>
--
Adam Binford
[
https://issues.apache.org/jira/browse/SEDONA-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714951#comment-17714951
]
Adam Binford commented on SEDONA-276:
-
[~umartin] Oh that's not how I took it! Yeah that's pretty
[
https://issues.apache.org/jira/browse/SEDONA-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714613#comment-17714613
]
Adam Binford commented on SEDONA-276:
-
[~umartin] I had everything use the same logging
[
https://issues.apache.org/jira/browse/SEDONA-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17713120#comment-17713120
]
Adam Binford commented on SEDONA-276:
-
I was looking at this as well. I think the log4j thing can
>
> [ ] -1 disapprove with the reason
>
> Checklist:
>
> [ ] Download links are valid.
>
> [ ] Checksums and PGP signatures are valid.
>
> [ ] Source code artifacts have correct names matching the current release.
>
> For a detailed checklist please refer to:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
>
> Thanks,
> Jia
>
--
Adam Binford
[
https://issues.apache.org/jira/browse/SEDONA-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17655634#comment-17655634
]
Adam Binford commented on SEDONA-231:
-
This is an interesting idea! Only comment I might add
Adam Binford created SEDONA-228:
---
Summary: Standardize logging dependencies
Key: SEDONA-228
URL: https://issues.apache.org/jira/browse/SEDONA-228
Project: Apache Sedona
Issue Type: Improvement
NSE (You have to manually check the LICENSE file)
> >
> > [ ] No unexpected binary files (You have to manually download binaries
> from
> > the link above)
> >
> > For a detailed checklist please refer to:
> >
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >
> >
> > [1] https://issues.apache.org/jira/browse/SEDONA-210
> > [2] https://issues.apache.org/jira/browse/SEDONA-211
> >
>
--
Adam Binford
eate JIRA tickets on their behalf once an issue or feature is
> confirmed.
>
> This will introduce extra complexity to the project management and might
> mess up the bug tracking at some point.
>
> Please let me know what you think.
>
> Thanks,
> Jia
>
--
Adam Binford
+1
I checked:
* Download links are valid
* Checksums and PGP signatures are valid
* DISCLAIMER and NOTICE are included
* Source code artifacts have correct names matching the current release
* The project can compile from the source code
On Mon, Nov 21, 2022 at 3:36 AM Jia Yu wrote:
> Hi
+1
I checked:
* Download links are valid
* Checksums and PGP signatures are valid
* DISCLAIMER and NOTICE are included
* Source code artifacts have correct names matching the current release
* The project can compile from the source code
Small note, the verify script on the website has a minor
ingly:
> > >
> > > [ ] +1 approve
> > >
> > > [ ] +0 no opinion
> > >
> > > [ ] -1 disapprove with the reason
> > >
> > > Checklist for reference (because of DISCLAIMER-WIP, other checklist
> items
> > > are not blockers):
> > >
> > > [ ] Download links are valid.
> > >
> > > [ ] Checksums and PGP signatures are valid.
> > >
> > > [ ] DISCLAIMER is included.
> > >
> > > [ ] Source code artifacts have correct names matching the current
> > release.
> > >
> > > For a detailed checklist please refer to:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> > >
> > >
> >
>
--
Adam Binford
Adam Binford created SEDONA-132:
---
Summary: Create common module for SQL functions
Key: SEDONA-132
URL: https://issues.apache.org/jira/browse/SEDONA-132
Project: Apache Sedona
Issue Type
I'll start with my support. I think it's fair to upgrade Spark versions to
get new features at this point.
Questions:
Since all the supported Spark versions are supported by a single artifact,
do you drop the -3.0 in the artifact ID? Or leave it in case it's needed in
the future?
Does Flink
Adam Binford created SEDONA-129:
---
Summary: Bump Spark version to 3.3.0
Key: SEDONA-129
URL: https://issues.apache.org/jira/browse/SEDONA-129
Project: Apache Sedona
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SEDONA-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17446503#comment-17446503
]
Adam Binford commented on SEDONA-4:
---
Yeah this would need a pretty big overhaul to properly fix for all
+1 (non-binding)
On Sun, Nov 14, 2021, 3:00 AM Jia Yu wrote:
> Hi all, This is a call for vote on Apache Sedona 1.1.1-incubating-rc1.
> Please refer to the changes listed at the bottom of this email. Release
> notes:
>
>
Adam Binford created SEDONA-73:
--
Summary: Support Scala 2.13
Key: SEDONA-73
URL: https://issues.apache.org/jira/browse/SEDONA-73
Project: Apache Sedona
Issue Type: Improvement
Adam Binford created SEDONA-67:
--
Summary: Support Spark 3.2
Key: SEDONA-67
URL: https://issues.apache.org/jira/browse/SEDONA-67
Project: Apache Sedona
Issue Type: Improvement
ala#L84-L109
>
> If we move the broadcast join detection as the first part of the detector
> and set other join detection to the "else". Will it fix the issue?
>
> if (broadcast XXX)
>
> else {
> all other join detection.
> }
>
> Thanks,
> Jia
>
>
with that is.
Adam
On Tue, Aug 3, 2021 at 7:46 AM Adam Binford wrote:
> I haven't encountered any issues with it but I can investigate with the
> full stacktrace. Also which version of Spark is this with?
>
> Adam
>
> On Tue, Aug 3, 2021 at 4:25 AM Jia Yu wrote:
>
>> Hi Pietro,
;> with 4 cores each.
> >>> No error is being print by driver but we are receiving the following
> >>> warning:
> >>> WARN org.apache.sedona.core.spatialOperator.JoinQuery: UseIndex is
> true,
> >>> but no index exists. Will build index on the fly.
> >>>
> >>> Actually we were able to run successfully the same spatial join when
> >>> only considering a very small sample of events.
> >>> Do you have any suggestion on how we can archive the same result on
> >>> higher volumes of data or if there is a way we can optimize the join?
> >>>
> >>> Attached you can find the pseudo-code we are running.
> >>>
> >>> Looking forward to hearing from you.
> >>>
> >>> Kind regards,
> >>> Pietro Greselin
> >>>
> >>
>
--
Adam Binford
>
> https://github.com/apache/incubator-sedona/blob/sedona-1.0.1-incubating-rc1/LICENSE
>
> 3. Please put instructions on how to build in the release, instructions can
> change over time so pointing to a URL may not be helpful when trying to
> build older versions.
>
> Build instruction has been added to svn/dist/dev
>
> https://dist.apache.org/repos/dist/dev/incubator/sedona/1.0.1-incubating-rc1/
>
--
Adam Binford
s relevant, I'm running with Scala 2.12.13 / Spark 3.0.2 and using
> the latest commit on the Sedona master branch.
>
>
>
> Best regards,
>
> Andrew Brooks
>
--
Adam Binford
Out of curiosity and knowing next to nothing about KNN, what is the return
value supposed to represent? The K nearest nearest geometries in spatialRDD
to any geometry in dataset point?
Adam
On Fri, Mar 26, 2021, 6:56 AM Alessandro Calvio
wrote:
> Hi,
> I’m a graduated in Computer Engineering
Adam Binford created SEDONA-26:
--
Summary: Add broadcast join support
Key: SEDONA-26
URL: https://issues.apache.org/jira/browse/SEDONA-26
Project: Apache Sedona
Issue Type: Improvement
pyter Notebook then in a .py file.
> >> On the official website I have found a quick start guide:
> >> https://sedona.apache.org/download/overview/
> >> and a Python Jupyter Notebook Examples guide:
> >> https://sedona.apache.org/tutorial/jupyter-notebook/
> >> However, it is still not clear, how to install and make it run.
> >> Unfortunately, I didn't find any useful step-by-step guide with the help
> >> of Google or YouTube and feel myself in an infinite loop of reading
> links
> >> after links that explain always different solutions.
> >> Thanks a lot in advance,
> >> Robert
> >> robertboz...@gmail.com
> >>
> >
>
--
Adam Binford
Hi all,
I've been playing around with Sedona a little bit, and first want to say
thanks to all the work that has gone into this! I was able to get a spatial
join working on several hundred billion points in under 30 minutes (time is
relatively based on resources obviously). I did have to use the
Adam Binford created SEDONA-19:
--
Summary: Global indexing does not work with SQL joins
Key: SEDONA-19
URL: https://issues.apache.org/jira/browse/SEDONA-19
Project: Apache Sedona
Issue Type: Bug
33 matches
Mail list logo
