Thank for your reply.
The data is design data. This data is mix of ascii, binary and design views
(IPs, libraries, cadence design data etc..).
Currently its exactlly the way we use any other repository servers such as
svn, git. etc.. (checkin, checkout, add, tag etc...).
User stores the data on the repository server (creating a module, adding
data, checking, tagging and releasing... etc).

Rahul


On Fri, Jun 6, 2014 at 8:19 PM, Vinod Kumar Vavilapalli <
[email protected]> wrote:

> Can you give more details on the data that you are storing in "the release
> data management"? And also how on how it is accessed - read, and modified?
>
> +vinod
>
> On Jun 2, 2014, at 5:33 AM, rahul.soa <[email protected]> wrote:
>
> > Hello All,
> > I'm newbie to Hadoop and interested to know if hadoop can be useful in
> order to solve the problem I am seeing.
> >
> > We have big data (sometimes b/w 200 - 600 GB) to store in the release
> data management (repository server, currently we are using synchronicity
> designsync) which takes roughly about  3-7 hours to upload/checkin this
> data (and download from repository server).
> >
> > I would like to know if application of hadoop can be useful in order to
> reduce this big time. The time taken is bothering design engineers to
> upload and download which further lead to delay in deliveries.
> >
> > Please note I'm new to hadoop and checking the possibility of usage in
> this scenario.
> >
> > Best Regards,
> > Rahul
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Reply via email to