Re: Superset production setup

2019-05-21 Thread Abhishek Sharma
Hi Mathew,

I wrote the article,
<https://medium.com/@abhioncbr/apache-superset-in-the-production-environment-92e914102cc5>
a couple of weeks back. Let me know if it is helpful for you.

Thanks
Abhishek Sharma

On Mon, May 20, 2019 at 2:35 PM John Bodley 
wrote:

> Hi Matthew,
>
> In answer to your questions (from Airbnb's perspective):
>
>1. Regarding a production environment it's probably highly dependent on
>your use case. At a minimum I would suggest having at least 3
> web-servers
>(we use Gunicorn <https://gunicorn.org/>) and 3 Celery workers for
>redundancy. We use Datadog for monitoring/alerting which has helped us
>track load and scale accordingly. We use Kubernetes for deployment which
>includes some elasticity, though currently we're running 3 web-servers
> and
>5+ Celery workers. The later may be overkill though we're trying to
> debug
>an ongoing QueuePool issue.
>2. We use AWS to house Redis, Superset, Celery, etc. which all run from
>the same region
><
> https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html
> >
>.
>3. Our servers run on 4 cores with 10 GB of memory. Note we haven't
>optimized this configuration.
>4. We have low thousands of weekly active users for Superset and SQL
>Lab.
>
> -John
>
>
>
>
> On Mon, May 20, 2019 at 12:24 AM Matthew Mutee  wrote:
>
> > Hi dev,
> >
> > We have been testing superset for the last couple of months and now want
> to
> > set it up in production. Could you please share what sort of resourcing
> > considerations you have made for  your superset installation.
> >
> > I am interested in:
> >
> >1. Number of servers used for load balancing.
> >2. Placement of  applications; redis, superset, celelery, nginx etc.
> >3. Actual resources in the servers; memory, cores etc
> >4. The average users accessing superset per day.
> >
> > Thanks :-)
> >
> > Regards,
> > Matthew M.
> >
>


Re: [VOTE] Release Superset 0.33.0 based on Superset 0.33.0rc1

2019-05-20 Thread Abhishek Sharma
+1 binding.

Newly built docker image

working fine.

Thanks
Abhishek

On Mon, May 20, 2019 at 2:03 PM Alan Gates  wrote:

> Max, when I check the signature (gpg --verify ) it tells me:
> gpg: Signature made Sat May 18 15:36:55 2019 PDT
> gpg:using RSA key 8CA186C4568E92301E5F2491A3B3BE2CCC1BB7E4
> gpg: Can't check signature: No public key
>
> I imported the KEYS file referenced in your message, but it doesn't appear
> to contain that key.  I think you need to either generate a new signature
> with the key in the file and upload that .asc file to the dist site (no
> need to rerole the release itself) or place the key you used into the KEYS
> file.
>
> Alan.
>
> On Sat, May 18, 2019 at 4:01 PM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > Dear all,
> >
> > The source release 0.33.0 RC1 for Apache Superset is baked and available
> > at:
> > https://dist.apache.org/repos/dist/dev/incubator/superset/, public
> > keys are available
> > at https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
> >
> > We're now attempting to use 0.33 as the base for the first release as
> > opposed to 0.32 in previous attempts. Many license-related issues had
> been
> > solved by the process shipping visualizations as plugins, and that
> > migration wasn't completed on 0.32. This is the third ASF release
> candidate
> > of Superset *We're still ironing out our release process, so please bear
> > with us and help if you can*.
> >
> > As I went along, I documented the process in [yet-to-be-merged]
> > RELEASING/README.md in the repo, latest edits here
> > https://github.com/apache/incubator-superset/pull/7539 . As part of
> > `RELEASING/`, we ship docker files to help package and test releases.
> >
> > For context the `0.33` release branch was cut at SHA 51068f007, that was
> > merged on master on Apr 17th. From that common ancestor, the following
> list
> > of commit was added as cherry-picks. The SHAs in the list bellow
> reference
> > the cherries on the release branch, PR number are available to get more
> > details.
> >
> > 7591a709 (tag: 0.33.0rc1, apache/release--0.33) 0.33.0rc1
> > b7ffdb8b Improve instructions
> > 4bbd68c6 Change babytux to open image in birth dashboard
> > eaa679e8 remove unused LICENSE entries
> > 42d50f9d Add Roboto font to LICENSE, remove glyphicons files
> > 5ae2836b Address COPYRIGHT + LICENSE issues
> > ea807f20 [WiP] Improvements related to ASF release process
> > c57ef5dc 0.31.0rc1.dev1
> > 51068f00 Adding permission for can_only_access_owned_queries (#7234)
> >
>


Re: [ANNOUNCE] Please welcome new Superset committer

2019-05-07 Thread Abhishek Sharma
Congrats Ville!

On Tue, May 7, 2019 at 7:13 PM Jeff Feng 
wrote:

> Nice, congrats Ville!
>
> On Tue, May 7, 2019 at 2:22 PM Andrew Musselman <
> andrew.mussel...@gmail.com>
> wrote:
>
> > Nice work Ville!
> >
> > On Tue, May 7, 2019 at 1:07 PM Charles Givre  wrote:
> >
> > > Congrats Ville!
> > >
> > > Sent from my iPhone
> > >
> > > > On May 7, 2019, at 15:49, Maxime Beauchemin <
> > maximebeauche...@gmail.com>
> > > wrote:
> > > >
> > > > All,
> > > >
> > > > I'm pleased to announce that the Superset PMC has voted in Ville
> > Brofeldt
> > > > to be
> > > > a committer. Ville has been actively involved in the project for some
> > > time
> > > > now, contributing patches and participating on Github.
> > > > Implementing optimizations to the core of Apache Superset to make it
> > > scale.
> > > > Please join in me congratulating Ville for becoming a Superset
> > committer.
> > > >
> > > > Welcome Ville!
> > > >
> > > > Cheers,
> > > >
> > > > Max, on behalf of the Superset PMC
> > >
> >
>
>
> --
>
> *Jeff Feng*
> Product Lead
> m: (949)-610-5108
> twitter: @jtfeng
>


Article on running a Superset as Docker container.

2019-04-23 Thread Abhishek Sharma
Hi All,

A couple of days back, I published a blog on how to run Apache Superset as
a Docker container.
Sharing it with you guys, if you guys want to refer. Link of article


Thanks
Abhishek


Re: [VOTE] Hosting questions / answers on StackOverFlow

2019-04-23 Thread Abhishek Sharma
+1

On Tue, Apr 23, 2019 at 8:49 PM Kan Ouivirach 
wrote:

> +1
>
> On Wed, Apr 24, 2019 at 7:47 AM Michelle Thomas
>  wrote:
>
> > +1
> >
> > On Tue, Apr 23, 2019 at 5:42 PM Krist Wongsuphasawat <
> > krist.wo...@gmail.com>
> > wrote:
> >
> > > Hi Superset Community,
> > >
> > > Per the previous thread "[DISCUSS] Best place for questions / answers",
> > > there is a proposal to
> > >
> > >- Host Superset Q (questions such as "How do I do something in
> > >Superset?") on StackOverFlow instead of github issues.
> > >- New questions on other channels (github/slack/etc.) will not be
> > >answered and the authors will be notified to ask on StackOverFlow
> > > instead.
> > >- Only keep bug reports, feature requests and project maintenance
> > issues
> > >on github. Old FAQs can be copied over to StackOverFlow. (Will need
> > >volunteers for this.)
> > >
> > > I would like to call for a VOTE to migrate to StackOverFlow.
> > > Please +1 if you support this decision, 0 for no comment or -1 if you
> > > disagree.
> > >
> > > This poll will end on Friday April 26th, 11:59pm Pacific time.
> > >
> > > Best regards,
> > >
> > > Krist
> > >
> > > --
> > >
> > > *Krist Wongsuphasawat*
> > > http://kristw.yellowpigz.com
> > >
> >
>


Re: Please add me to Hudi slack community

2019-04-22 Thread Abhishek Sharma
Apology, wrong email address.

On Mon, Apr 22, 2019 at 7:14 PM Abhishek Sharma 
wrote:

> Hi,
>
> Please add me to the Apache Hudi slack community. Email id is 
> *abhioncbr.apa...@gmail.com
> *
>
> Thanks
> Abhishek
>


Latest release of Superset has no flower dependency.

2019-04-22 Thread Abhishek Sharma
Hi,

Thanks for releasing a new version of Superset.
While using the latest version of Superset, I realized flower dependency is
not there. It is a good package for monitoring Celery. Is it dropped
purposely?

Also, please add me as a contributor for Superset Jira. My Jira id is
*abhioncbr*

Thanks
Abhishek


Please add me to Hudi slack community

2019-04-22 Thread Abhishek Sharma
Hi,

Please add me to the Apache Hudi slack community. Email id is
*abhioncbr.apa...@gmail.com
*

Thanks
Abhishek


Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2

2019-04-22 Thread Abhishek Sharma
Thanks, Max.

+1 Binding

On Mon, Apr 22, 2019 at 2:15 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Ok right, I just pushed the tag.
>
> On Mon, Apr 22, 2019 at 10:29 AM Abhishek Sharma <
> abhioncbr.apa...@gmail.com>
> wrote:
>
> > There is no git tag for release 0.32.0rc2 version
> > https://github.com/apache/incubator-superset/releases
> > Please check.
> >
> > Thanks
> > Abhishek
> >
> > On Sat, Apr 20, 2019 at 12:34 PM Jeff Feng  >
> > wrote:
> >
> > > +1 Binding
> > >
> > > On Sat, Apr 20, 2019 at 8:49 AM Maxime Beauchemin <
> > > maximebeauche...@gmail.com> wrote:
> > >
> > > > Done, thanks for the tip!
> > > >
> > > > On Sat, Apr 20, 2019 at 2:38 AM Bolke de Bruin 
> > > wrote:
> > > >
> > > > > +1, non-binding
> > > > >
> > > > > @max I suggest removing the older artifacts, it tends to confuse
> the
> > > > > incubator ppl
> > > > >
> > > > > Verstuurd vanaf mijn iPad
> > > > >
> > > > > > Op 20 apr. 2019 om 00:36 heeft Alan Gates 
> > het
> > > > > volgende geschreven:
> > > > > >
> > > > > > +1.  Checked LICENSE, NOTICE, and DISCLAIMER files, signature and
> > > hash.
> > > > > > Checked to make sure there were no binary files in the
> > distribution.
> > > > > >
> > > > > > Alan.
> > > > > >
> > > > > > On Fri, Apr 19, 2019 at 3:25 PM Maxime Beauchemin <
> > > > > > maximebeauche...@gmail.com> wrote:
> > > > > >
> > > > > >> Dear all,
> > > > > >>
> > > > > >> The source release 0.32.0 RC2 for Apache Superset is baked and
> > > > available
> > > > > >> at:
> > > > > >> https://dist.apache.org/repos/dist/dev/incubator/superset/,
> > public
> > > > > >> keys are available
> > > > > >> at
> > > https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
> > > > > >>
> > > > > >> This is the second ASF release candidate of Superset (!)* We're
> > > still
> > > > > >> ironing out our release process, so please bear with us and help
> > if
> > > > you
> > > > > >> can*
> > > > > >> .
> > > > > >>
> > > > > >> As I went along, I documented the process in RELEASING.md in the
> > > repo,
> > > > > >> latest edits here
> > > > > https://github.com/apache/incubator-superset/pull/7329
> > > > > >>
> > > > > >> For context (and similarly to 0.31) the `0.32` release branch
> was
> > > cut
> > > > at
> > > > > >> SHA 1fece0d2f, that was merged on master on Jan 22nd. From that
> > > common
> > > > > >> ancestor, the following list of commit was added as
> cherry-picks.
> > > The
> > > > > SHAs
> > > > > >> in the list bellow reference the cherries on the release branch,
> > PR
> > > > > number
> > > > > >> are available to get more details.
> > > > > >>
> > > > > >> New commits since 0.32.0rc1 *in bold:*
> > > > > >>
> > > > > >> *8fb4ba0d (HEAD -> release--0.32, tag: 0.32.0rc2) 0.32.0rc2*
> > > > > >> *3e6f6848 Add disclaimer and remove counter (#6738)*
> > > > > >> c7b32ac8 (tag: 0.32.0rc1, apache/release--0.32) 0.32.0rc1
> > > > > >> b89cdbdc RELEASING.md from master
> > > > > >> 0e23f2e6 Add sign.sh
> > > > > >> 21804346 [load_examples] download data at runtime (#7314)
> > > > > >> b32d5900 Remove LICENSE entry around dataset (#7318)
> > > > > >> b3aa5633 (release--0.31) 0.31rc23
> > > > > >> 24a595f4 bugfix: improve 'Time Table' (#6959)
> > > > > >> c70abbed 0.31rc22
> > > > > >> dd8c2db9 [filter_box] allow empty filters list (#7220) (#7244)
> > > > > >> 2ab07a08 Fix race condition when fetching results in SQL Lab
> > (#7198)
> > > > > >> (#7242)
> > > > > >> a9d54894 0.31.0rc21
> > > > > >> 

Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2

2019-04-22 Thread Abhishek Sharma
There is no git tag for release 0.32.0rc2 version
https://github.com/apache/incubator-superset/releases
Please check.

Thanks
Abhishek

On Sat, Apr 20, 2019 at 12:34 PM Jeff Feng 
wrote:

> +1 Binding
>
> On Sat, Apr 20, 2019 at 8:49 AM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > Done, thanks for the tip!
> >
> > On Sat, Apr 20, 2019 at 2:38 AM Bolke de Bruin 
> wrote:
> >
> > > +1, non-binding
> > >
> > > @max I suggest removing the older artifacts, it tends to confuse the
> > > incubator ppl
> > >
> > > Verstuurd vanaf mijn iPad
> > >
> > > > Op 20 apr. 2019 om 00:36 heeft Alan Gates  het
> > > volgende geschreven:
> > > >
> > > > +1.  Checked LICENSE, NOTICE, and DISCLAIMER files, signature and
> hash.
> > > > Checked to make sure there were no binary files in the distribution.
> > > >
> > > > Alan.
> > > >
> > > > On Fri, Apr 19, 2019 at 3:25 PM Maxime Beauchemin <
> > > > maximebeauche...@gmail.com> wrote:
> > > >
> > > >> Dear all,
> > > >>
> > > >> The source release 0.32.0 RC2 for Apache Superset is baked and
> > available
> > > >> at:
> > > >> https://dist.apache.org/repos/dist/dev/incubator/superset/, public
> > > >> keys are available
> > > >> at
> https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
> > > >>
> > > >> This is the second ASF release candidate of Superset (!)* We're
> still
> > > >> ironing out our release process, so please bear with us and help if
> > you
> > > >> can*
> > > >> .
> > > >>
> > > >> As I went along, I documented the process in RELEASING.md in the
> repo,
> > > >> latest edits here
> > > https://github.com/apache/incubator-superset/pull/7329
> > > >>
> > > >> For context (and similarly to 0.31) the `0.32` release branch was
> cut
> > at
> > > >> SHA 1fece0d2f, that was merged on master on Jan 22nd. From that
> common
> > > >> ancestor, the following list of commit was added as cherry-picks.
> The
> > > SHAs
> > > >> in the list bellow reference the cherries on the release branch, PR
> > > number
> > > >> are available to get more details.
> > > >>
> > > >> New commits since 0.32.0rc1 *in bold:*
> > > >>
> > > >> *8fb4ba0d (HEAD -> release--0.32, tag: 0.32.0rc2) 0.32.0rc2*
> > > >> *3e6f6848 Add disclaimer and remove counter (#6738)*
> > > >> c7b32ac8 (tag: 0.32.0rc1, apache/release--0.32) 0.32.0rc1
> > > >> b89cdbdc RELEASING.md from master
> > > >> 0e23f2e6 Add sign.sh
> > > >> 21804346 [load_examples] download data at runtime (#7314)
> > > >> b32d5900 Remove LICENSE entry around dataset (#7318)
> > > >> b3aa5633 (release--0.31) 0.31rc23
> > > >> 24a595f4 bugfix: improve 'Time Table' (#6959)
> > > >> c70abbed 0.31rc22
> > > >> dd8c2db9 [filter_box] allow empty filters list (#7220) (#7244)
> > > >> 2ab07a08 Fix race condition when fetching results in SQL Lab (#7198)
> > > >> (#7242)
> > > >> a9d54894 0.31.0rc21
> > > >> b959fcd2 fix PRODUCT-67916 Click OK button cannot close error
> message
> > > modal
> > > >> (#7179)
> > > >> 2da9613f Update __init__.py (#7166)
> > > >> 538da2e3 0.31.0.rc20
> > > >> 7ce35d2a [migration] Fixing issue with fb13d49b72f9 downgrade
> (#7145)
> > > >> 947f02ff [migration] Fixing issue with c82ee8a39623 downgrade
> (#7144)
> > > >> daf2b8e5 Bump python lib croniter to an existing version (#7132)
> > > >> eb4c1355 Use metric name instead of metric in filter box (#7106)
> > > >> 2ff721ae handle null column_name in sqla and druid models
> > > >> e83a07d3 [forms] Fix handling of NULLs
> > > >> 76d26f37 0.31.0.rc19
> > > >> fe78b4ec Fix filter_box migration PR #6523 (#7066)
> > > >> c43d0fd3 [sqlparse] Fixing table name extraction for ill-defined
> query
> > > >> (#7029)
> > > >> b64a452a [sql lab] improve table name detection in free form SQL
> > (#6793)
> > > >> 2357c4aa Adding custom control overrides (#6956)
> > > >> 9dd7e84a [sql-parse] Fixing LIMIT exceptions (#6963)
> > > >> 5d8dd142 [csv-upload] Fixing message encoding (#6971)
> > > >> f454dedd [main] Disable resetting main DB attributes (#6845)
> > > >> e967b268 [sqla] Fixing order-by for non-inner-joins (#6862)
> > > >> a5d9a4e0 Adding template_params to datasource editor for sqla tables
> > > >> (#6869)
> > > >> 6b895413 [datasource] Ensuring consistent behavior of datasource
> > > >> editing/saving. (#7037)
> > > >> 8ef2789f Adding warning message for sqllab save query (#7028)
> > > >> 0ebdb564 fix inaccurate data calculation with adata rolling and
> > > >> contribution (#7035)
> > > >> b3af6a26 [fix] explore chart from dashboard missed slice title
> (#7046)
> > > >> c54b067c [db-engine-spec] Aligning Hive/Presto partition logic
> (#7007)
> > > >> bd65942e Changing time table viz to pass formatTime a date (#7020)
> > > >> 50accda9 [fix] Cursor jumping when editing chart and dashboard
> titles
> > > >> (#7038)
> > > >> 5ace5769 0.31.0rc17
> > > >> 927a5846 [WIP] fix user specified JSON metadata not updating
> dashboard
> > > on
> > > >> refresh (#7027)
> > > >> fafb824d 0.31.0rc16
> > > >> 7b72985e [fix] /superset/slice/id url is too long (#6989)

Re: Latest release of Superset(0.31.0rc18) is failing for dependency croniter==0.3.26

2019-04-15 Thread abhishek sharma
Thanks. WIll do that.

On Mon, Apr 15, 2019 at 7:52 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Yes, we can do that in rc19.
>
> It's been fixed on `master` but wasn't on the release branch.
>
> Ideally you'd "-1" on the release thread I think.
>
> Max
>
> On Mon, Apr 15, 2019 at 2:52 PM abhishek sharma <
> abhioncbr.apa...@gmail.com>
> wrote:
>
> > Hi Dave,
> >
> > Thanks for the update.
> >
> > **Is there a possibility that Superset released version code will be
> making
> > the change in requirements.txt?
> >
> > Thanks
> >
> >
> > On Mon, Apr 15, 2019 at 4:33 PM David Smith 
> > wrote:
> >
> > > The developer of that project accidentally deleted that version. If you
> > > update the dependency to 0.3.29 it should unblock you.
> > >
> > > On Mon, Apr 15, 2019 at 1:28 PM abhishek sharma <
> > > abhioncbr.apa...@gmail.com>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > I am trying to build the Docker image of Superset for the latest
> > release
> > > > i.e. *0.31.0rc18 *and it is failing for the dependency
> > croniter==0.3.26.
> > > > Checked the croniter project release history
> > > > <https://pypi.org/project/croniter/#history>
> > > > and there is no such version.
> > > >
> > > > Please help me, Is I am missing something?
> > > >
> > > > Thanks
> > > > Abhishek
> > > > <https://pypi.org/project/croniter/#history>
> > > >
> > >
> >
>


Re: [VOTE] Release Superset 0.31.0 based on Superset 0.31.0 RC18

2019-04-15 Thread abhishek sharma
-1 (since, depenedency croniter==0.3.26 is failing.)

Thanks.

On Mon, Apr 15, 2019 at 3:54 PM Alan Gates  wrote:

> Per https://www.apache.org/legal/resolved.html#cc-by the CC BY 4.0 license
> can only be used on things included in binary form.  It appears that it is
> data from the diva-gis.org that is being included under this license,
> which
> I would think meets the requirement.  But I don't know how to verify that
> only data files from that source are being included.  Is there a list
> somewhere of the files included from that source?
>
> Other than that, things look good.  License, notice, and disclaimer files
> all look good.  All the .py and .sh files have the appropriate Apache
> License header, I didn't find any binaries.
>
> Alan.
>
> On Mon, Apr 15, 2019 at 10:47 AM John Bodley  .invalid>
> wrote:
>
> > +1
> >
> > On Sun, Apr 14, 2019 at 9:18 AM Krist Wongsuphasawat <
> > krist.wo...@gmail.com>
> > wrote:
> >
> > > +1 exciting!
> > >
> > > Best regards,
> > >
> > > Krist
> > >
> > > --
> > >
> > > Krist Wongsuphasawat
> > > http://kristw.yellowpigz.com
> > > On Apr 14, 2019, 06:24 -0700, Jeff Feng  >,
> > > wrote:
> > > > +1 Binding
> > > >
> > > > On Sun, Apr 14, 2019 at 6:20 AM Bolke de Bruin 
> > > wrote:
> > > >
> > > > > +1, non-binding
> > > > >
> > > > > I checked:
> > > > >
> > > > > * SHA512
> > > > > * Signature of the release, can use some improvement but the key
> > > checks out
> > > > > here (https://people.apache.org/keys/committer/):
> > > > >
> > > > > gpg: Signature made Tue Mar 19 07:35:24 2019 CET
> > > > > gpg: using RSA key BB990B01715969F648C7A65472DC479A3011B01B
> > > > > gpg: Good signature from "Maxime Beauchemin <
> > > maximebeauche...@gmail.com>"
> > > > > [unknown]
> > > > > gpg: WARNING: This key is not certified with a trusted signature!
> > > > > gpg: There is no indication that the signature belongs to the
> > > > > owner.
> > > > > Primary key fingerprint: BB99 0B01 7159 69F6 48C7 A654 72DC 479A
> 3011
> > > B01B
> > > > >
> > > > > * NOTICE present
> > > > > * LICENSE present
> > > > > * DISCLAIMER present
> > > > > * INSTALL.txt present (did not check build)
> > > > > * ran apache-rat
> > > > >
> > > > > Good luck at the incubator!
> > > > >
> > > > > (O and the vote is open for a minimum of 48h I believe :-) ).
> > > > >
> > > > > B.
> > > > >
> > > > >
> > > > >
> > > > > On 14 April 2019 at 00:24:11, Jeff Feng
> (jeff.f...@airbnb.com.invalid
> > )
> > > > > wrote:
> > > > >
> > > > > ++ this is very exciting. Thank you Max!
> > > > >
> > > > > On Sat, Apr 13, 2019 at 3:19 PM Bolke de Bruin 
> > > wrote:
> > > > >
> > > > > > Great stuff Max! Good to see this happening!
> > > > > >
> > > > > > - Maybe good to note that only the vote of committers counts as a
> > > binding
> > > > > > vote and that it's good practice to make that clear when voting?
> > > > > >
> > > > > > I'll verify the release tomorrow.
> > > > > >
> > > > > > B.
> > > > > >
> > > > > > Sent from my iPhone
> > > > > >
> > > > > > > On 13 Apr 2019, at 23:56, Maxime Beauchemin <
> > > > > maximebeauche...@gmail.com>
> > > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > Dear all,
> > > > > > >
> > > > > > > The source release 0.31.0 RC18 for Apache Superset is baked and
> > > > > available
> > > > > > > at:
> > > > > > > https://dist.apache.org/repos/dist/dev/incubator/superset/,
> > public
> > > > > > > keys are available
> > > > > > > at
> > > https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
> > > > > > >
> > > > > > > This is the first ASF release candidate of Superset (!)* We're
> > > still
> > > > > > > ironing out our release process, so please bear with us and
> help
> > > if you
> > > > > > can*.
> > > > > > > Note that we understand that starting at "RC18" is confusing,
> but
> > > > > > > constitute an outlier as we handoff from the old process to the
> > new
> > > > > one.
> > > > > > > From this point onwards, we intend on using a linear sequence
> > that
> > > maps
> > > > > > > one-to-one with Apache-submitted release candidates. The term
> > > release
> > > > > > > candidate and label RC should be exclusive to the proper
> > > > > Apache-compliant
> > > > > > > release process moving forward.
> > > > > > >
> > > > > > > Also note that I decided to use the label `0.31.0rc18` (pypi
> > > compliant)
> > > > > > > instead of a semver compliant `0.31.0-rc.18` which Pypi and
> > > Python's
> > > > > > > PEP-440 won't allow. This being a Python project, we use
> Python's
> > > > > > standards.
> > > > > > >
> > > > > > > As I went along, I documented the process in RELEASING.md in
> the
> > > repo,
> > > > > > > latest edits here
> > > > > > > https://github.com/apache/incubator-superset/pull/7296/files
> > > > > > >
> > > > > > > For context, the `0.31` release branch was cut at SHA
> 1fece0d2f,
> > > that
> > > > > was
> > > > > > > merged on master on Jan 22nd. From that common ancestor, the
> > > following
> > > > > > list
> > > > > > > of commit was 

Re: Latest release of Superset(0.31.0rc18) is failing for dependency croniter==0.3.26

2019-04-15 Thread abhishek sharma
Hi Dave,

Thanks for the update.

**Is there a possibility that Superset released version code will be making
the change in requirements.txt?

Thanks


On Mon, Apr 15, 2019 at 4:33 PM David Smith  wrote:

> The developer of that project accidentally deleted that version. If you
> update the dependency to 0.3.29 it should unblock you.
>
> On Mon, Apr 15, 2019 at 1:28 PM abhishek sharma <
> abhioncbr.apa...@gmail.com>
> wrote:
>
> > Hi,
> >
> > I am trying to build the Docker image of Superset for the latest release
> > i.e. *0.31.0rc18 *and it is failing for the dependency croniter==0.3.26.
> > Checked the croniter project release history
> > <https://pypi.org/project/croniter/#history>
> > and there is no such version.
> >
> > Please help me, Is I am missing something?
> >
> > Thanks
> > Abhishek
> > <https://pypi.org/project/croniter/#history>
> >
>


Latest release of Superset(0.31.0rc18) is failing for dependency croniter==0.3.26

2019-04-15 Thread abhishek sharma
Hi,

I am trying to build the Docker image of Superset for the latest release
i.e. *0.31.0rc18 *and it is failing for the dependency croniter==0.3.26.
Checked the croniter project release history

and there is no such version.

Please help me, Is I am missing something?

Thanks
Abhishek



Apache-Superset Setup in Production Environment

2018-12-21 Thread abhishek sharma
Hi,
A couple of days back, I just wrote the article about how to deploy Superset in 
the production environment. I am sharing the article link for your reference 
and open for suggestions/feedback over the setup architecture. 

Apache Superset in the production environment – Abhishek Sharma – Medium 


| 
| 
| 
|  |  |

 |

 |
| 
|  | 
Apache Superset in the production environment – Abhishek Sharma – Medium

Abhishek Sharma

Visualizing data helps in building a much deeper understanding of the data and 
fastens analytics around the data...
 |

 |

 |



Happy to hear more on this front from all of you.
ThanksAbhishek Sharma